{"push_id":3063156111,"size":1,"distinct_size":1,"ref":"refs/heads/awsorder","head":"90024150346abdda5e4373439001abfcf6a4f601","before":"fda8b3cd4065b84249ed311472f5ac713199c258","commits":[{"sha":"90024150346abdda5e4373439001abfcf6a4f601","author":{"name":"Masha Schneider","email":"9a19271f701eeb7a4e6dffa6a484ec27a6e51a66@cockroachlabs.com"},"message":"roachprod: fix order of regions when using create with AWS\n\nThe allRegions() function returns a list of all valid regions. Before\nit would read a mapping of regions to AMIs into a hashmap\nand would use that to generate a list. This resulted in callers getting\nregions in different orders between calls. For a function like Create\nwhich uses the first region from this list for a non geo distributed\ncluster, it means that the cluster would get started in a random region\nunless explicitly specified.\n\nNow we're going to read the AMI list in order so we can ensure\na consistent ordering between calls.\n\nRelease note: None","distinct":true,"url":"https://api.github.com/repos/m-schneider/cockroach/commits/90024150346abdda5e4373439001abfcf6a4f601"}]}
{"actor":{"display_login":"m-schneider"}}