3 ms·
I know why the state file exist, sorry; I really meant: The purpose of making the state file mandatory. In particular, it makes first-time setup incredibly oner
by lobster_johnson 10y ago
I know why the state file exist, sorry; I really meant: The purpose of making the state file mandatory. In particular, it makes first-time setup incredibly onerous. You almost _never_ start with a clean slate.
It's great that you're working on fixing that, but it looks like it will be some time before it's quite there, given the seemingly slow pace of development.
It's nice that Terraform can support untaggable resources, but I don't understand why that's the general case and not a special case. I can't remember an AWS resource that isn't nameable or taggable.
- leg100 10y ago>> I can't remember an AWS resource that isn't nameable or taggable. ElasticIP is one among many. For a complete list: http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/Using_Tags.html#tag-restrictions http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/Using_Tag...