357 karma · joined January 1, 2013
There are pros and cons to this approach but the point is not to exactly replicate DNS.
Imagine if you could just put iron ore in a warehouse and make a 25% return every year, we'd have no steel!
In fact, even the fact that the comment is now wrong tells you that the change was ill-considered and needs to be revisited.
There are even videos of her on YouTube speaking, reading braille, and communicating through hand-spelling.
Let's take the most basic example: auto-generated ids. Many resources in AWS, GCS, etc have auto generated ids (just use tags you say, but many don't have tags or tags are used as part of some other system). Now, when terraform creates that resource you have to modify the config to contain the id. But if you have any sense terraform runs as part of a CI system that lets others review your code before merging, deploy to staging, etc.
So now does the terraform process need to make an automatic git push? What if there's a conflict? Does it make a PR that has to be manually merged? All of this is much more complicated than just having one JSON file in S3.
I have actually managed resources with Ansible where you have this problem and it's worse. And this is just _one_ thing.
Is Terraform's state story perfect? No. There are definitely annoyances, and one thing I'd love to see is a way to declaratively handle imports, renames, etc. when you need to, but it's better than the alternative.
class F150(@delegate private val underlying: Car) { ... }
class F150(private val underlying: Car) : Car by Underlying { ... }
// etcLots of predators are far more dangerous to people than wolves but wolves provoke a visceral reaction because they've been demonized in a way bears, etc haven't.
If they wanted to penalize slow sites they could have… penalized slow sites. There are numerous metrics (paint time, etc) that they can track for that.