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.
import { Construct } from "constructs";import { TerraformOutput, TerraformStack, TerraformVariable } from "cdktf";import { Pet } from "@cdktf/provider-random/lib/pet";import { RandomProvider } from "@cdktf/provider-random/lib/provider"; export class HCLInteropStack extends TerraformStack { constructor(scope: Construct, name: string) { super(scope, name); new RandomProvider(this, "default", {}); const petNameLength = new TerraformVariable(this, "petNameLength", { type: "number", default: 2, description: "Pet name length", }); const myPet = new Pet(this, "example", { length: petNameLength.value, }); new TerraformOutput(this, "name", { value: myPet.id, }); }}
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.
terraform { required_providers { docker = { source = "hashicorp/random" version = "~> 3.1" } }} module "pet" { source = "./mods/pet" petNameLength = "1"} output "name" { value = module.pet.name}
HCL to CDKTF
HCL can be used with Terraform CDK in two ways. Converting HCL code directly to a CDKTF language, and using Terraform modules directly within CDKTF projects.
In order to convert HCL to a CDKTF language, the
cdktf convert
command can be used. It automatically translates HCL into a preferred CDKTF language. This is useful when working with an existing codebase that needs to be converted to CDKTF.While CDKTF has the ability to import HCL modules through
cdktf get
when referenced within thecdktf.json
file, Terraform modules can also be referenced without generating language specific bindings. The modules documentation shows how to use existing Terraform modules in CDK for Terraform projects.