CLI: HCL synth generates incorrect remote configuration with workspaces

[Hi-Fi]

Expected Behavior

Terraform can be initialized with CDKTF synthesized stack in HCL format. Remote configuration would look like:

terraform {
  backend "remote" {
    organization = "test-organization"
    workspaces {
      name = "test-stack"
    }
    hostname = "test.artifactory.local"
  }
}

Actual Behavior

CDKTF synthesized incorrect remove configuration

terraform {
  backend "remote" {
    organization = "test-organization"
    workspaces = {
      name = "test-stack"
    }
    hostname = "test.artifactory.local"
  }
}

When manually removing that = after workspaces, init works fine.

Steps to Reproduce

1. Initialize empty CDKTF project
2. Add following remote backend to it
3. Synthesize stack to HCL (cdktf synth --hcl)
4. Go to output directory of stack and run terraform init

Versions

language: typescript cdktf-cli: 0.20.8 node: v20.13.1 cdktf: 0.20.8 constructs: 10.3.0 jsii: null terraform: 1.9.4 arch: arm64 os: darwin 23.6.0

Providers

No response

Gist

No response

Possible Solutions

Probably some specific handling needed for that part. Didn't had any other places with similar issues. Datasource to remote works different way and it requires that = sign.

Workarounds

Don't use HCL (not working for me as HCL is needed for Sonarqube analysis)

Anything Else?

No response

References

No response

Help Wanted

• [ ] I'm interested in contributing a fix myself

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

[mutahhir]

Another alternative is to use the cloud block. (Docs), which is recommended by terraform anyway over the remote backend. From my understanding, that doesn't have this problem.

The remote backend is a bug nonetheless. We will be fixing it in a future release.

[Hi-Fi]

We use Artifactory as state backend, I understood that Cloud backend is reserved for HCP Terraform (ex-Terraform Cloud) (and it's Enterprise version) and remote is for that