{"push_id":639801707,"size":1,"distinct_size":1,"ref":"refs/heads/upstream-cluster-id-check","head":"ae6cc8d6b8ee70283161883150b58e3f25098fbb","before":"1f6bd119e83d95a76439928e5447f5d0ee8f8fbc","commits":[{"sha":"ae6cc8d6b8ee70283161883150b58e3f25098fbb","author":{"email":"7899e0c33011a90f0ae59315a11037005d1c3cc2@metaswitch.com","name":"Shaun Crampton"},"message":"Raise exception if cluster ID changes between reading and watching.\n\nThis catches the case where the cluster is rebuilt from a backup\nor replaced unexpectedly.  Without this change, we'd potentially\nwatch on an etcd index that was only valid on the old cluster.\n\n* On read, record the cluster ID of the server.\n* On watch, check the cluster ID hasn't changed.","distinct":true,"url":"https://api.github.com/repos/Metaswitch/python-etcd/commits/ae6cc8d6b8ee70283161883150b58e3f25098fbb"}]}