The future of Terraform CDK

Post by chuckadams » Wed, Dec 10, 2025, 8:03 PM UTC

yearolinuxdsktp wrote: post #12

That’s a real shame. It seems like Pulumi is the only alternative for internal DSLs for IaaC? I always found HCL to be quite terrible, slowly becoming less painful, but not really refactoring-friendly. Terraform CDK had promise as a blessed infrastructure-as-actual-code solution from the official maintainer of Terraform, so easier to sell internally rather than something from a new vendor like Pulumi. I feel sorry fo…

Post by Hamuko » Wed, Dec 10, 2025, 8:07 PM UTC

smithcoin wrote: post #3

vbernat wrote: post #2

It's odd to always say "Hashicorp, an IBM company". Looks like they want to assign blame. I did try Pulumi a while back, but the compatibility with Terraform modules was not great, so I've switched to CDKTF, which can handle unmodified modules. Dunno if I'll switch back to Pulumi or just use OpenTofu directly.

We use OpenTofu it’s pretty seamless

Post by firesteelrain » Wed, Dec 10, 2025, 8:11 PM UTC

vbernat wrote: post #2

It's odd to always say "Hashicorp, an IBM company". Looks like they want to assign blame. I did try Pulumi a while back, but the compatibility with Terraform modules was not great, so I've switched to CDKTF, which can handle unmodified modules. Dunno if I'll switch back to Pulumi or just use OpenTofu directly.

Post by crimsonnoodle58 » Wed, Dec 10, 2025, 8:14 PM UTC

Post by ryandvm » Wed, Dec 10, 2025, 8:15 PM UTC

tapoxi wrote: post #13

GardenLetter27 wrote: post #6

Damn, what are the best alternatives here? For pure AWS I guess CDK directly is okay, but locks you in.

I went with CDK, I'm locked into AWS already and it means my major dependency for IaC is my cloud vendor and not a third party. If I really need to migrate off of AWS at some point I'll throw an LLM at it.