December 10, 2025
Press F to synth
Terraform CDK has been phased out
HashiCorp axes Terraform CDK; devs cry “rug pull” and debate lock‑in
TLDR: Terraform CDK goes read‑only on Dec 10, 2025, as HashiCorp pivots back to standard Terraform files. Comments explode over blame, vendor lock‑in, and losing “real code” workflows, with folks split between forking, moving to Pulumi or AWS CDK, or bracing for a painful migration.
HashiCorp (now under IBM) just told DevOps to pack their bags: Terraform CDK will be sunset on Dec 10, 2025, archived, and left read‑only. The official line is “no product‑market fit,” and they’re steering folks back to Terraform’s own config files (HCL) with a lifeboat command: cdktf synth --hcl. The community? Absolutely buzzing. One top comment side‑eyes the repeated “HashiCorp, an IBM Company” phrasing, saying it feels like blame‑shifting. Another calls it a straight‑up rug pull—because when a tool like this dies, it can hit your entire infrastructure at once.
The big drama: code vs config. Fans of “infrastructure as actual code” (writing real programming languages to manage servers) say HCL—Terraform’s config language—is clunky and hard to refactor. Pulumi (a rival that uses real code) gets name‑checked as the last major option, but not everyone loves it. AWS’s CDK is suggested for Amazon‑only setups, but many are nervous about vendor lock‑in. Others eye OpenTofu, the community fork of Terraform, hoping it’ll fill the gap.
Memes rolled in fast: “404: product‑market‑fit not found,” and “Press F to synth.” Some vow to fork CDKTF; others are grabbing the emergency exit via synth --hcl. However you slice it, this is a spicy moment for infra nerds. Official info lives here: Terraform CDK
Key Points
- •Terraform CDK (CDKTF) will be sunset and archived on December 10, 2025, with no further maintenance or development.
- •HashiCorp cites lack of product‑market fit and a focus on Terraform core and its ecosystem as reasons for the decision.
- •The CDKTF repository will become read‑only on GitHub, and documentation will mark it as deprecated; no compatibility updates will follow.
- •CDKTF remains under the MPL license, and HashiCorp encourages community forks for independent continuation.
- •Users can migrate by generating HCL via “cdktf synth --hcl” and managing with Terraform CLI; AWS CDK users may choose to migrate to AWS CDK instead.