{"push_id":1232861838,"size":1,"distinct_size":1,"ref":"refs/heads/bugfix/etcd-machines","head":"749c9150efc7c1dd6248d42dc23e6a60063df3c7","before":"579d4360220fae3b888dfbb7d67ec2833113ec7d","commits":[{"sha":"749c9150efc7c1dd6248d42dc23e6a60063df3c7","author":{"name":"Alexander Kukushkin","email":"7909656d7b76398bede3de15fdc4ac0ea30dc29a@zalando.de"},"message":"Update etcd topology only after original request succeed\n\nThere is no point to try to update topology until original request is\nnot performed. Also for us it is more important to execute original\nrequest rather then keep topology of etcd cluster in sync.\n\nIn addition to that implement the same retry-timeout logic in the\n`machines` property which already is used in `api_execute` method.","distinct":true,"url":"https://api.github.com/repos/zalando/patroni/commits/749c9150efc7c1dd6248d42dc23e6a60063df3c7"}]}
{"actor":{"display_login":"CyberDem0n"}}