3 ms·
No you’re not the only one. The problem with Terraform “Scripting” is in a lot of cases it takes a loooong time to find out your “runtime” errors. These are typ
by 0x445442 5y ago
No you’re not the only one. The problem with Terraform “Scripting” is in a lot of cases it takes a loooong time to find out your “runtime” errors. These are typically fat fingered strings. I think something like AWS CDK, where you find these errors at compile, time is a better approach.
- w1nt3rmut3 5y agoThis already exists. https://github.com/hashicorp/terraform-cdk/ https://github.com/hashicorp/terraform-cdk/
- 0x445442 5y agoI wasn't aware of this and I'm glad to see they're doing it. But my guess is this is a relatively recent offering in response to the AWS version and the issues I was mentioning.
- seniorThrowaway 5y agoterraform really needs to be run in CI/CD pipe. Even without the backend initialized you can run terraform validate which will find things like undeclared variables and messed up count and foreach references.
- isbvhodnvemrwvn 5y agoBut it won't find resource IDs being passed instead of ARNs, and a whole lot of other things.