{"push_id":660774927,"size":2,"distinct_size":1,"ref":"refs/heads/master","head":"b6a9a258114ebc73ca60ca587d93f9c0586f8088","before":"f32ca77c7362c20241ce25f1e7e317757187746d","commits":[{"sha":"700bba2131e1694906e4204d950ca3d894ebffc3","author":{"email":"2adf8750ebf867c309e7a7aa7261810f76a10b79@gmail.com","name":"Dan Carley"},"message":"aws: Move all \"private\" records to \"public\" zone\n\nThe one existing private zone (referred to by zone ID) needed to be\nassociated with each new independent VPC. Terraform isn't able to do this\nbecause it doesn't manage that existing private zone and doing it by hand\nwould be too cumbersome. This was documented in the story but not the\nREADME.\n\nThis meant that machines were unable to resolve the addresses of internal\nELBs and failed to configure Nginx, in the example of the following Ansible\ninventory item:\n\n    [hipache]\n    xx.xx.xx.xx internal_ip=dcarley-hipache-int.tsuru.paas.alphagov.co.uk\n\nWe could fix this by letting Terraform create and manage a separate private\nzone for each independent environment. Since these don't have to be\ndelegated like public zones do.\n\nHowever we're not using the split-horizon feature of private zones (our\nrecords are namespaced to be \"internal\" and don't overlap with the public\nrecords) and I'm not concerned about us exposing private IP addresses.\n\nThe current private zone will have to be deleted manually.","distinct":false,"url":"https://api.github.com/repos/alphagov/tsuru-terraform/commits/700bba2131e1694906e4204d950ca3d894ebffc3"},{"sha":"b6a9a258114ebc73ca60ca587d93f9c0586f8088","author":{"email":"54669547a225ff20cba8b75a4adca540eef25858@uncommonsense-uk.com","name":"ActionJack"},"message":"Merge pull request #46 from alphagov/remove_private_zone\n\n[#93688938] aws: Move all \"private\" records to \"public\" zone","distinct":true,"url":"https://api.github.com/repos/alphagov/tsuru-terraform/commits/b6a9a258114ebc73ca60ca587d93f9c0586f8088"}]}