github hashicorp/terraform-cdk v0.19.0

latest releases: v0.21.0-pre.137, v0.20.10, v0.21.0-pre.136...
13 months ago

Breaking changes

Minimum required Node.js version updated to 18.12

Since the long-term support for Node.js 16 ended on 2023-09-11, we updated our minimum compatible Node.js version to 18.12.

Potential provider naming collision with instance function moveTo on TerraformResource

We have added support for resource refactoring and renaming with the addition of the instance function moveTo on TerraformResource. We forsee the potential for naming collision with providers using moveTo as an attribute. In instances where provider bindings fail to compile due to the collision, regenerate your provider bindings and replace the provider related usage of moveTo to moveToAttribute in your configuration if applicable.

Java: codeMakerOutput needs to be set to a company identifier

We did not honor the codeMakerOutput setting in the cdktf.json previously, this is fixed now.
To have no changes in the generated code you can set codeMakerOutput: "imports".
If you like, you can now set it to your company name, e.g. codeMakerOutput: "com.hashicorp" so that the provider is generated under the com.hashicorp.aws namespace for example. Omitting the codeMakerOutput will lead to the default value .gen being used and results in an error.

feat

  • feat(lib): add resource move functionality #3152
  • feat: add import capabilities to cdktf #2972
  • feat!: update minimum required Node.js version to 18.12 (LTS) #3181

fix

  • fix(provider-generator): java akamai provider generation #3185
  • fix: use codemaker output in java #3000

chore

  • chore(examples): change debian image version in gcp example #3186
  • chore: upgrade node-pty dependency to add support for Node.js 20 #3182
  • chore(deps): pin trusted workflows based on HashiCorp TSCCR #3180

Don't miss a new terraform-cdk release

NewReleases is sending notifications on new releases.