3 ms·
Are you saying it should? I think whether that's desirable or not is a matter of preference. The nice thing about Terraform is that you don't have to go all in
by rbongers 4y ago
Are you saying it should?
I think whether that's desirable or not is a matter of preference. The nice thing about Terraform is that you don't have to go all in. I don't really want to have to tell it to ignore every resource that I want to manually manage, and I don't want it wasting the extra API calls on trying to find every resource that's not in my configuration every time I want to deploy.
Now, if they provided a separate tool for detecting manually created resources, that would be awesome, but it wouldn't fit into the typical flow of showing drift regularly just before deploying in my opinion. That's more about detecting whether you're about to overwrite something that was manually done, or if you're about to make changes assuming your infrastructure is as you last left it. I don't need to take inventory of every single resource I have every time before deploying.
- raffraffraff 4y agoNot suggesting it "should", I was just pointing out that it's not a complete drift detection tool.
- jen20 4y agoThat was a deliberate choice made. Terraform development has a cardinal rule: do not touch objects you did not create. It could do drift detection for existence rather easily if that was relaxed, but the rule follows the principle of least surprise.