Define and provision cloud infrastructure using programming languages like TypeScript, Python, Java, C#, and Go with Terraform.
Terraform CDK (CDKTF) is an open-source tool that allows developers to define and provision cloud infrastructure using programming languages like TypeScript, Python, Java, C#, and Go instead of HashiCorp Configuration Language (HCL). It solves the problem of infrastructure management by enabling developers to leverage familiar programming constructs and existing toolchains while accessing the full Terraform ecosystem.
Cloud engineers, DevOps practitioners, and developers who prefer using programming languages over declarative configuration languages for infrastructure management and want to integrate infrastructure code with their application development workflows.
Developers choose Terraform CDK because it eliminates the need to learn HCL, allows reuse of programming skills, and integrates infrastructure code with existing development tools for testing and dependency management, all while maintaining compatibility with Terraform's extensive provider ecosystem.
Define infrastructure resources using programming constructs and provision them using HashiCorp Terraform
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Supports TypeScript, Python, Java, C#, and Go, allowing developers to use familiar programming languages for infrastructure code, as highlighted in the key features.
Provides access to all Terraform providers and modules without learning HCL, enabling leverage of Terraform's extensive resources while using programming paradigms.
Integrates with existing tools for testing, dependency management, and IDE support, promoting consistency in development workflows as stated in the philosophy.
Offers 'cdktf synth --hcl' to generate Terraform configuration files, easing migration to standard HCL, though it may require manual adjustments per the README.
The project sunsets on December 10, 2025, with no further updates, fixes, or compatibility improvements, risking long-term infrastructure management as per the sunset notice.
Migrating away requires generating HCL files that may need manual review and adjustments, adding overhead and potential for errors in transition.
Post-EOL, it won't support new Terraform versions or providers, leaving users stranded with outdated tools in evolving cloud environments.
Continued use depends on community forks, which may lack the resources, stability, or documentation of official HashiCorp maintenance.