Why IBM Dropped Terraform CDK Support and What It Means for IaC

IBM’s HashiCorp announced that Terraform Cloud Development Kit (CDKTF) will no longer be maintained. The source code is archived at https://github.com/hashicorp/terraform-cdk and will receive no further updates.

Background

Terraform was released by HashiCorp in 2014 as an infrastructure‑as‑code (IaC) tool. Core commands include terraform init, terraform plan, and terraform apply. In 2023 the project changed its license to a Business Source License, prompting the community fork OpenTofu, which later joined the CNCF.

IBM’s decision

IBM stated that CDKTF did not achieve sufficient product‑market fit and that future investment will focus on Terraform core and its ecosystem. Existing CDKTF projects are encouraged to migrate to native HashiCorp Configuration Language (HCL), which remains MPL‑licensed.

To convert a CDKTF project to HCL, run: cdktf synth -- hcl AWS users may consider the AWS CDK as an alternative.

Technical scope of CDKTF

CDKTF allowed infrastructure definitions in general‑purpose languages such as TypeScript, Python, C#, and Go, generating Terraform JSON configuration files that are then applied with the standard Terraform CLI. This approach mirrors Pulumi’s multi‑language model.

Community observations

Weekly downloads of the TypeScript CDKTF package exceed 140,000, indicating active usage.

Some experts argue that abandoning native language APIs reduces flexibility for developers who need programming constructs beyond HCL’s declarative model.

Implications for IaC

HCL is a domain‑specific, declarative language; it lacks loops, conditionals, and other advanced constructs found in general‑purpose languages, which can make complex configurations harder to maintain. CDKTF’s removal pushes users toward either pure HCL or alternative tools such as Pulumi, OpenTofu, System Initiative, or Platform Engineering Labs’ Formae.