{"push_id":631239553,"size":2,"distinct_size":2,"ref":"refs/heads/master","head":"ec4b7e7948159b78fe2149c8224f4fd9d688d2e7","before":"52f694add3b54525c9068529f3ec36beecadb16c","commits":[{"sha":"f9cb8d810537e2a757fde1d1a8d1f39a526e5bd5","author":{"email":"bd21dacf50ae0c2a81d439ae755251c53052fe92@cisco.com","name":"Ed Warnicke"},"message":"Fix so that operational store correctly removes controller entries\n\nBefore, if a controller entry was removed on ovsdb, we didn't\nremove it from the operational store.\n\nThis is an artifact of using *merge* rather than *put*.\nUsing merge is *still* a good idea for us, but what was happening\nwas basically this.\n\nSay we got a report in the operational store of\n\n[controller1, controller2]\n\nwhich we dutifully merged.\n\nThen we got a report of\n[controller2]\n\nwhen that is *merged*... the controller1 entry is left dangling,\nbecause its a *merge*.  To compensate, we have to be *very*\nspecific about wanting to remove controller1.\n\nThis is accomplished by factoring out an OvsdbControllerUpdateCommand\nand OvsdbControllerRemoveCommand.\n\nChange-Id: I2e38e0e175cef5f848f28501cfaeecc1cb162151\nSigned-off-by: Ed Warnicke <eaw@cisco.com>","distinct":true,"url":"https://api.github.com/repos/opendaylight/ovsdb/commits/f9cb8d810537e2a757fde1d1a8d1f39a526e5bd5"},{"sha":"ec4b7e7948159b78fe2149c8224f4fd9d688d2e7","author":{"email":"0bd82f91a319b8977788d8264eb020ecd4ace960@redhat.com","name":"Sam Hague"},"message":"Merge \"Fix so that operational store correctly removes controller entries\"","distinct":true,"url":"https://api.github.com/repos/opendaylight/ovsdb/commits/ec4b7e7948159b78fe2149c8224f4fd9d688d2e7"}]}