Interesting read. Seems to be focusing on the neck of the woods the author is exposed to. Terraform isn’t about cloud apis only. Terraform allows me managing k

Interesting read. Seems to be focusing on the neck of the woods the author is exposed to. Terraform isn’t about cloud apis only. Terraform allows me managing keycloack realms, ssh keys, cloud resources, postgres databases, git repos, imap accounts, and so on. The state is there to be treated as the source of truth. It gives an answer to „do I have what I want to have”. With that state, it is possible to cross reference various resource types without having to load the curent state on every run. I’m surprised that the author did not see that as a performance issue. Imagine that you have to load all route53 state, all buckets, ec2 instances, iam roles, … on every execution, and imagine you have 200+ machines… That’s what we used to do with puppet and chef, no? Turned out that always fetching the view of the world from an api is pretty expensive and quickly exhausts api rate limits. It’s a pretty weak article without any effort to suggest how could it work without a state.