HCL Interoperability
Terraform requires infrastructure configuration files written in either HashiCorp Configuration Language (HCL) or JSON syntax. CDK for Terraform (CDKTF) works by translating configurations defined in an imperative programming language to JSON configuration files for Terraform.
Starting from version 0.20, CDKTF can also generate Terraform HCL as output by setting the --hcl
flag when running cdktf synth
.
CDKTF may not be the right choice for every team and project within your organization. For example, some teams may already be very familiar with Terraform and have created HCL modules, providers, etc. To provide flexibility, CDKTF applications are interoperable with Terraform projects written in HCL. Specifically:
- CDKTF applications can use all existing Terraform providers and HCL modules.
- CDKTF can generate modules that HCL Terraform projects can use in their configurations.
This page shows how you can interoperate HCL and CDK for Terraform configuration.
CDKTF to HCL
The following example is a CDKTF application that uses the hashicorp/random
provider to generate a random name.
To use this as a Terraform module, run cdktf synth
and copy the resulting cdktf.out/stacks/random-pet-module/cdk.tf.json
file out to the module directory in your HCL project.
By default, cdktf synth
generates Terraform JSON, but starting from version 0.20, CDKTF can also generate Terraform HCL output by passing the --hcl
flag to cdktf synth
.
After you transfer the cdk.tf.json
(or cdk.tf
) file, you can reference the pet name module as you would any other HCL Terraform module.
HCL to CDKTF
Use the cdktf convert
command to automatically translate existing HCL into a preferred CDKTF language. The modules documentation shows how to use existing Terraform modules in CDK for Terraform projects.