Terraform should have remained stateless

Re:Terraform should have remained stateless by ntoskrnl on Saturday May 28, 2022 @06:45AM (#31539225)

How would TF work without state and without tags?

Let's say your TF config declares a database Foo. Your AWS account has databases Foo and Bar. How does TF know whether it's responsible for database Bar and whether to delete it?

[ Parent | on HN ]

Re:Terraform should have remained stateless by Aeolun on Saturday May 28, 2022 @07:03AM (#31539330)

Resource is tagged with “terraform stack x created this”?

[ Parent | on HN ]

Re:Terraform should have remained stateless by cassianoleal on Saturday May 28, 2022 @07:18AM (#31539405)

Interesting. Disregarding for a moment that not all cloud resources supporting tags on all cloud providers (and let's not get started with all the non-cloud stuff Terraform is capable to manage), how does tf know that `stack x` is the thing that's currently running?

[ Parent | on HN ]

Re:Terraform should have remained stateless by gtirloni on Saturday May 28, 2022 @08:22AM (#31539762)

By the time the tag has enough information to be useful, you are storing a TF state file in a tag. Anyway, I don't think people complaining about a s3 bucket for tf state actually has experience creating tools like tf.

[ Parent | on HN ]

Re:Terraform should have remained stateless by ntoskrnl on Saturday May 28, 2022 @08:20AM (#31539753)

The parent said he thinks tags aren't the right approach. I wanted to know what he proposes instead.

[ Parent | on HN ]