5 min read
|
Saved February 14, 2026
|
Copied!
Do you care about this?
CDK for Terraform (CDKTF) has been deprecated, leaving users to find alternatives. This article outlines options for migration, focusing on Pulumi as a viable path forward, detailing the conversion and import process for transitioning projects.
If you do, here's more
CDK for Terraform (CDKTF) has been officially deprecated as of December 10, leaving users without support or updates. Teams that relied on CDKTF now face the challenge of finding a suitable replacement. The article outlines three primary alternatives: reverting to HashiCorp Configuration Language (HCL), migrating to AWS CDK, or transitioning to Pulumi.
Reverting to HCL is possible, but itβs not ideal for most teams since many chose CDKTF to avoid using HCL. Migrating to AWS CDK is another option, especially for teams committed to AWS. However, this approach demands a complete rewrite of code due to different APIs and resource models, complicating the migration process. The article emphasizes that this option may not be practical for many teams given the extensive work required.
Pulumi emerges as a strong alternative, allowing teams to use familiar programming languages like TypeScript, Python, and Go. It retains a similar structure to CDKTF, with general-purpose languages and the ability to manage infrastructure as code. Migrating to Pulumi involves three steps: converting CDKTF code to a Pulumi program, importing existing state, and refactoring the code to align with the new Pulumi stack. The article provides detailed commands for each step, highlighting how Pulumi simplifies the migration process while maintaining compatibility with existing Terraform resources.
Questions about this article
No questions yet.