open-constructs/cdk-terrain

Stance Yarn classic (1.x) is archived and no longer maintained upstream. The cdktn CLI still drives Yarn classic projects (yarn add, yarn list --json), but prints a deprecation warning. Please move Yarn classic projects to npm or pnpm; cdktn init --template=typescript-pnpm scaffolds a pnpm project. Yarn Berry (2+) is not officially supported. Some commands happen to work (see below), others fail with a clear error pointing here. We will not add Berry support unless there is demand. The supported route to a Yarn Berry cdktn project is projen (see below). Projen-based initialisation is a proposed long-term direction for this project (see discussion on #79). If you need native Yarn Berry support in cdktn init and cdktn provider *, give this issue a 👍 (please do not add "+1" comments). The vote count is what decides whether Berry support gets prioritised. A vote is for the suggested Yarn Berry configuration we would consider supporting, so the CLI surface stays small: packageManager:

Expected Behavior cdktn synth --hcl should produce a cdk.tf that is valid HCL. Literal " characters inside a string attribute value should be escaped as \", while resolved ${...} interpolations are left intact. Expected contents of cdktf.out/stacks/repro/cdk.tf: resource "aws_sqs_queue" "queue" { name = "repro-queue" redrive_policy = "{\"deadLetterTargetArn\":\"${aws_sqs_queue.dlq.arn}\",\"maxReceiveCount\":3}" } terraform validate and tflint should both exit cleanly. Emitting jsonencode({ ... }) instead would also be acceptable and arguably more idiomatic, but plain escaping is the minimal correct behaviour and matches what the JSON output path already achieves. Actual Behavior The embedded quotes are copied through unescaped, and the file cannot be parsed. Actual contents of cdktf.out/stacks/repro/cdk.tf: resource "aws_sqs_queue" "queue" { name = "repro-queue" redrive_policy = "{" deadLetterTargetArn ":" $ { aws_sqs_queue.dlq.arn } "," maxReceiveCount ":3}

Summary packages/@cdktn/hcl2cdk/test/convertProject.test.ts cannot run on any supported Terraform, because its fixture pulls a registry module that uses a language experiment removed in Terraform 1.3. Detail The fixture's cluster.tf declares: module "k3s" { source = "camptocamp/k3s/docker" version = "0.11.0" ... } getTerraformPlan runs a real terraform init, which fails: Error: Experiment has concluded on .terraform/modules/k3s/versions.tf line 24, in terraform: 24: module_variable_optional_attrs, Experiment "module_variable_optional_attrs" is no longer available. The final feature corresponding to this experiment differs from the experimental form and is available in the Terraform language from Terraform v1.3.0 onwards. A version bump does not fix it. Every published version of that module still uses the experiment — verified by terraform init against 0.11.0, 0.11.1, 1.0.0 and 1.0.1; all fail the same way. Why the suite has been skipped since 2022 The skip commit is

Description A blank or whitespace-only range in targetVersions is accepted as valid and then treated as if that product were not declared. This lets synth-time feature checks silently skip a targeted product. This was discovered while reviewing the ValidateFeatureTargetSupport migrations in #453, #454, #455, and #456. It is a shared validation issue rather than a defect specific to any one of those PRs, so it should be fixed separately. Reproduction Configure an app with an empty Terraform range: { "targetVersions": { "terraform": "" } } Then use a feature whose Terraform availability is validated through ValidateFeatureTargetSupport, such as an import block requiring Terraform >=1.5.0. The app synthesizes without the expected compatibility error. Whitespace-only values such as " " and "\t" behave the same way. Cause The shared target-version validation accepts these values because npm semver normalizes blank and whitespace-only strings to the wildcard range "*": semver.validRa

Expected Behavior pnpm test inside examples/typescript/azure-service-bus-queue-trigger starts Jest. Its jest.config.js sets: setupFilesAfterEnv: ["<rootDir>/setup.js"], and 21 of the 22 TypeScript examples ship a tracked setup.js at their root for exactly this purpose. The cdktn init template ships one too (packages/@cdktn/cli-core/templates/typescript/setup.js). Actual Behavior Jest aborts during config validation because the file does not exist: $ cd examples/typescript/azure-service-bus-queue-trigger && pnpm test $ jest ● Validation Error: Module <rootDir>/setup.js in the setupFilesAfterEnv option was not found. <rootDir> is: /path/to/cdk-terrain/examples/typescript/azure-service-bus-queue-trigger Configuration Documentation: https://jestjs.io/docs/configuration [ELIFECYCLE] Test failed. See above for more details. This example is the only one of the 22 missing setup.js: $ git ls-files 'examples/typescript/**/setup.js' | grep -v node_modules | wc -l 21 $ for d i