Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

CDK compatibility commitment #1335

Open
ghost opened this issue Mar 1, 2024 · 5 comments
Open

CDK compatibility commitment #1335

ghost opened this issue Mar 1, 2024 · 5 comments
Labels
enhancement New feature or request pending-decision This issue has not been accepted for implementation nor rejected. It's still open to discussion.

Comments

@ghost
Copy link

ghost commented Mar 1, 2024 •
edited by abstractionfactory
Loading

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.
@ghost ghost changed the title 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? CDK compatibility Mar 1, 2024
@ghost ghost mentioned this issue Mar 1, 2024
Closed
@ghost ghost changed the title CDK compatibility CDK compatibility commitment Mar 1, 2024
@ghost ghost added documentation Improvements or additions to documentation pending-decision This issue has not been accepted for implementation nor rejected. It's still open to discussion. labels Mar 1, 2024
@cam72cam cam72cam added the pending-steering-committee-decision Issue will be submitted to the steering committee to make a decision. label Jun 20, 2024
@luckydev
Copy link

luckydev commented Jun 23, 2024 •
edited
Loading

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.

@abstractionfactory
Copy link
Contributor

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.

@abstractionfactory abstractionfactory added enhancement New feature or request and removed documentation Improvements or additions to documentation pending-steering-committee-decision Issue will be submitted to the steering committee to make a decision. labels Nov 25, 2024
@github-actions github-actions bot mentioned this issue Nov 25, 2024
Open
@tmccombs
Copy link

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

@marcinwyszynski
Copy link
Contributor

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

@cam72cam
Copy link
Member

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request pending-decision This issue has not been accepted for implementation nor rejected. It's still open to discussion.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@luckydev @marcinwyszynski @cam72cam @tmccombs @abstractionfactory