{"push_id":608521331,"size":1,"distinct_size":1,"ref":"refs/heads/vpc_missing","head":"9545f26fa01c67d2339cb80163a9a0392c7e1e2a","before":"134ca191226339b422451b0b2635d362e65c17e0","commits":[{"sha":"9545f26fa01c67d2339cb80163a9a0392c7e1e2a","author":{"email":"591df529998a3f13802047f4a3da1cc13316b823@paperg.com","name":"Phil Frost"},"message":"Correct AWS VPC or route table read functions\n\nIf the state file contained a VPC or a route table which no longer\nexists, Terraform would fail to create the correct plan, which is to\nrecreate them.\n\nIn the case of VPCs, this was due to incorrect error handling. The AWS\nSDK returns a aws.APIError, not a *aws.APIError on error.  When the VPC\nno longer exists, upon attempting to refresh state Terraform would\nsimply exit with an error.\n\nFor route tables, the provider would recognize that the route table no\nlonger existed, but would not make the appropriate call to update the\nstate as such. Thus there'd be no crash, but also no plan to re-create\nthe route table.","distinct":true,"url":"https://api.github.com/repos/bitglue/terraform/commits/9545f26fa01c67d2339cb80163a9a0392c7e1e2a"}]}