4 ms·
I noticed that this GCP article about Terraform best practices linked to a similar tool: cloud-nuke (https://github.com/gruntwork-io/cloud-nuke https://github.c
by tpmx 4y ago
I noticed that this GCP article about Terraform best practices linked to a similar tool: cloud-nuke (https://github.com/gruntwork-io/cloud-nuke https://github.com/gruntwork-io/cloud-nuke)
https://cloud.google.com/docs/terraform/best-practices-for-terraform https://cloud.google.com/docs/terraform/best-practices-for-t...
> After you run the terraform destroy command, also run additional clean-up procedures to remove any resources that Terraform failed to destroy. Do this by deleting any projects used for test execution or by using a tool like cloud-nuke.
> Warning: Don't use such tools in a production environment.
It seems like this tool only supports AWS though, at least nowadays.
I kind of feel bad for the GCP people here. Damned if you do (link to an external project, which might change), damned if you don't.
Besides this thing, I really enjoyed reading this article though! AWS is missing this kind of content.
- thematrixturtle 4y agoIn GCP, the tool is not necessary, because you can simply delete the containing project to "nuke" any resources attached to it.
- deleted 4y ago[deleted]
- tpmx 4y agoThere is a 30 day "marked for deletion period" after you do this. The resources related to the project aren't immediately nuked. https://cloud.google.com/resource-manager/docs/creating-managing-projects#shutting_down_projects https://cloud.google.com/resource-manager/docs/creating-mana...
- thematrixturtle 4y agoDeleting a project does immediately turn off (stop billing) the vast majority of associated resources, including VMs. The main exception is storage, but that cost is typically fairly marginal.
- tpmx 4y agoOh, ok. That seems fair and makes sense. (I wish that had been documented.)