{"push_id":705629628,"size":2,"distinct_size":2,"ref":"refs/heads/force_destroy","head":"b21ac2cbd29d1052cbb8bd704538979904cb86ee","before":"599935de4b159b2a5ced5ffabe320061ddb2fa61","commits":[{"sha":"a574a80e2a4fd8b8bade3eb0951d37402156eebc","author":{"email":"ef3de85a3d97dbcab5d7819afea3ade14024d455@gmail.com","name":"Colin Saliceti"},"message":"force_destroy parameter for GCE and AWS buckets\n\nAvoid the following error:\nError deleting S3 Bucket: BucketNotEmpty: The bucket you tried to delete is not empty\n\tstatus code: 409, request id: []\n\nAllows deleting the content of S3 and GCE buckets on a terraform destroy action.\nThis is really useful when using test environments. It is potentially dangerous as the bucket resource may be implicitly destroyed and recreated during a simple apply.\nIt can be specified via the force_destroy variable, which is false by default.","distinct":true,"url":"https://api.github.com/repos/alphagov/tsuru-terraform/commits/a574a80e2a4fd8b8bade3eb0951d37402156eebc"},{"sha":"b21ac2cbd29d1052cbb8bd704538979904cb86ee","author":{"email":"cfdafbac99d2e35c247a9a77807e3052ab164d38@gmail.com","name":"Hector Rivas Gandara"},"message":"Update README to explain apply limiting target\n\nTo change the force_deploy setting in the buckets you need to run apply again\nlimiting the target to the buckets. It is better to set the variable\nduring the initial provisioning.\n\nThis commit explains how set this variable in the initial provision and\nhow to change the setting if it was not set previously.","distinct":true,"url":"https://api.github.com/repos/alphagov/tsuru-terraform/commits/b21ac2cbd29d1052cbb8bd704538979904cb86ee"}]}