Skip to content

Commit

Permalink
chore: update upgrade guide
Browse files Browse the repository at this point in the history
  • Loading branch information
DanielMSchmidt committed Oct 16, 2023
1 parent aab4b80 commit e207a50
Showing 1 changed file with 10 additions and 0 deletions.
10 changes: 10 additions & 0 deletions website/docs/cdktf/release/upgrade-guide-v0-19.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -8,6 +8,16 @@ description: >-

0.19 brings new workflows to import existing resources from cloud providers and refactor exisiting resources in your CDKTF project.

### 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.

0 comments on commit e207a50

Please sign in to comment.