{"push_id":728425755,"size":2,"distinct_size":2,"ref":"refs/heads/devR2.5","head":"962719908ac10050e782ce20e1bc0fac2e91f322","before":"e23a1260347132e1bf71f550a8fb460755c1274e","commits":[{"sha":"ad8c6ed94f118938305d73c8afba24643604e8ea","author":{"email":"6c6b10459f882b6cf22810865e8b9f08251d0036@juniper.net","name":"Yun Li"},"message":"PR 1099996 [Confidential] - [CLoS Setup] Device gets wrongly mapped when we delete and leaf and add a different new leaf\n\nfix:\nIn case of ztpStage is true and this is a leaf and deployStatus changes to provision:\nThe device is going to be removed and the management ip will eventually expire and go back to DHCP pool.\nWe need to reset managementIp field for this device to None because soon another leaf will probably get the\nsame management ip address from DHCP. We want avoid the getDevices REST API returns\n2 devices having the same management ip.\nNote we don't do this when ztpStaged is false because all the management ip are pre-allocated\nin that case and will never change.\n\nPR: 1099996\nReviewed by: yunli","distinct":true,"url":"https://api.github.com/repos/moloyc/OpenClos/commits/ad8c6ed94f118938305d73c8afba24643604e8ea"},{"sha":"962719908ac10050e782ce20e1bc0fac2e91f322","author":{"email":"6c6b10459f882b6cf22810865e8b9f08251d0036@juniper.net","name":"Yun Li"},"message":"Merge pull request #182 from yunli2004/devR2.5\n\nPR 1099996 [Confidential] - [CLoS Setup] Device gets wrongly mapped w…","distinct":true,"url":"https://api.github.com/repos/moloyc/OpenClos/commits/962719908ac10050e782ce20e1bc0fac2e91f322"}]}