4 ms·
it took 5 years to get that useful for_each for modules though so I'd imagine some people waited long enough that they moved on to better tools.
by stevehawk 5y ago
it took 5 years to get that useful for_each for modules though
so I'd imagine some people waited long enough that they moved on to better tools.
- acdha 5y agoWhat better tools do you have in mind? Most of the people I know in the space have been moving _to_ Terraform, although CDK has improved enough over CF to be appealing for people who are all in on Amazon.
- thayne 5y ago"better" is subjective. But Pulumi fixes a lot of the pain points of terraform for me.
- staticassertion 5y agoPulumi has been such a breath of fresh air. It is the only tool that actually feels like it encompasses "infrastructure as code".
- MehdiHK 5y agoTerraform CDK is a thing too, if you want to go beyond AWS.
- asenchi 5y agofor_each is an anti-pattern for reliable Terraform IMO. Not sure it was worth the wait and there isn't much out there that can compare with the simplicity of Terraform.
- devonbleak 5y agoWAY more reliable than count which would do screwy things like rename a bunch of stuff and delete the last item if you removed an item from the middle of a list. Complex architectures and reusable module encapsulation require a bit more complexity than HCL1 was capable of describing IMO (and apparently the O of most of the Internet). That doesn't necessarily make it less reliable. Could I describe my infrastructure "reliably" just using raw resources with no loops? Sure but that sounds like a nightmare to both build and maintain.