News for hackers. Stuff that matters.

A comment on Terraform should have remained stateless. Parent comment

Re:Terraform should have remained stateless by shepherdjerred on Saturday May 28, 2022 @01:06AM (#31537762)
I'm most familiar with AWS, but I assume Azure and GCP have similar features.

Use some tag unique to the project and tag all resources on creation. When deleting resources delete everything not in your stack that has the tag. You can find these resources using the provider's tagging APIs, e.g. https://aws.amazon.com/blogs/aws/new-aws-resource-tagging-ap...

[ Parent | on HN ]
Re:Terraform should have remained stateless by NovemberWhiskey on Saturday May 28, 2022 @01:32AM (#31537865)
That probably does help; I still feel like you're going to end up sacrificing a lot of the drift-detection capabilities as well though - like unless you know a priori what the default values of every optional parameter are, how do you know whether the values in your resources are "correct"?
[ Parent | on HN ]
Re:Terraform should have remained stateless by InvertedRhodium on Saturday May 28, 2022 @03:12AM (#31538265)
There are quite a few AWS resources that don't support tags.
[ Parent | on HN ]