[Ramnath0521]

Closes: #562

Summary

HCL synth copied backslashes in string values through unchanged, so a Windows path rendered as "C:\Users\me\project\terraform.tfstate". Terraform and OpenTofu reject that at init (The \U escape sequence must be followed by eight hexadecimal digits). The default LocalBackend path is path.join(process.cwd(), ...), so every HCL synth on Windows with the default backend produced a cdk.tf that cannot initialise. A value ending in a backslash left the string unterminated.

Change

In packages/cdktn/src/hcl/render.ts, escapeQuotes now escapes both \ and ", so Terraform reads the value back as written (the same result as JSON.stringify). The old (?<!\\) lookbehind is gone: once backslashes are escaped, a backslash before a quote no longer means the quote is already escaped.

A string that contains ${...} used to skip escaping entirely, and locals and outputs also wrote such strings without any escaping. Both now go through the same function, which keeps each ${...} interpolation as written and escapes only the text around it. The scanner follows nested braces and quoted strings inside the interpolation, so ${lookup({a = "}"}, "a")} is not cut short, and leaves $${ alone.

Tests

Seven tests in test/json-to-hcl.test.ts: a Windows path, a trailing backslash, a quote after a backslash, backslashes around an interpolation, a quoted string inside an interpolation, a brace inside a quoted string inside an interpolation, and the default LocalBackend path on Windows. Six fail on main and pass with the change; the one with a quoted string inside an interpolation passes either way and pins that handling. All 47 tests in json-to-hcl.test.ts pass, snapshots included (40/40).

I ran the whole cdktn package on Windows 11. 13 tests fail in 4 suites, with and without this change: no terraform binary on PATH (matchers.test.ts) and no built lib directory (the asset-* suites). Prettier and eslint are clean on both files. I did not run terraform init on the output; the tests compare the generated HCL text.

Notes

• A string that already contained a deliberate HCL escape (for example \n meant as a newline) is now written as a literal backslash and n. That follows the behaviour proposed in the issue, and a multi-line string still goes into a heredoc, which does not interpret escapes.
• fix(lib): escape quotes in HCL string expressions #501 and fix(lib): escape object keys in expressions and HCL maps #569 touch the same area (quotes in HCL string expressions, escaping of keys). This change only covers backslashes and quotes in string values.

🤖 Generated with Claude Code