CDK compatibility commitment

Will OpenTofu be kept compatible with Terraform's CDK or have it own? I mean: it's nice it currently is compatible, but what will happen with CDK if OpenTofu will break Terraform compatibility at some point in the future?

Originally posted by @baterja in #601 (comment)

Editing the original issue: this issue is about OpenTofu's support for CDKTF. Please upvote this issue if you would like to see work on this to be done and also comment with the action you would like to see taken.

[luckydev]

Thanks a lot for creating a dedicated issue for this. It will be too helpful if we keep CDKTF produced JSON and Opentofu comptaible with each other.

That is we must be able to do a Synth() from go/python and generate a .json config and one should be able to apply the same via tofu apply.

Rationale: Outside CDKTF + OpenTofu combo, there is no other open-source-foundation-backed project that can let us code infrastructure in python/go. afaik.

Linking a recent discussion on Reddit: https://www.reddit.com/r/Terraform/comments/1gugfxe/is_cdktf_becoming_abandonware/

If you are interested in this feature, please make sure to upvote the original issue so the dev team can see how popular this would be.

[tmccombs]

Maybe it would be worth forking CDKTF and putting it under the opentofu organization?

[marcinwyszynski]

Before committing to maintaining something it would be good to understand why it hasn't been successful so far.

[cam72cam]

Here's the last discussion of this issue in the Technical Steering Committee a few months ago: https://github.com/opentofu/opentofu/blob/main/TSC_SUMMARY.md#cdk-tf-compatibility-commitment

We are open to reviewing code to fix compatibility issues between OpenTofu and the existing CDK codebase, or a potential community fork.