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.

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

feat: support OpenTofu #1132

Open
scottrigby opened this issue Nov 16, 2023 · 7 comments
Open

feat: support OpenTofu #1132

scottrigby opened this issue Nov 16, 2023 · 7 comments

Comments

@scottrigby
Copy link

scottrigby commented Nov 16, 2023

Follow-up to question in #1016

This issue is more clearly scoped to track actual support for OpenTofu in weaveworks/tf-controller. Thanks @LappleApple for the heads up.

Problem/opportunity

Many people have been impacted by HashiCorp's decision to change Terraform's licensing. As a result, the OpenTofu (formerly Open TF) fork of Terraform was created to remain open source, community-driven, and managed by the Linux Foundation.

Given OpenTofu's broad appeal, and the strong value that weaveworks/tf-controller already brings to GitOps for Terraform, it would be even more valuable if this controller also supported OpenTofu.

Suggested approach

@matheuscscp – and anyone else interested – let's use this issue as an entry point for collaboration toward OpenTofu Support.

Given that the tf-controller maintainers are busy with Terraform for now, OpenTofu support in this controller should be community-driven. As Chanwit said in #1016 (comment):

We've been busy tackling all things Terraform, and it's certainly kept our hands full.
Regarding OpenTofu, your offer to contribute is much appreciated. Please feel free to get involved.

@shanduur
Copy link

shanduur commented Jan 10, 2024

Hi @paulcarlton-ww , @scottrigby ! I have seen some initial work in the tf-runner-images, are you still thinking about working on this issue?

@nab-gha
Copy link

nab-gha commented Jan 10, 2024

I have reopened the PR, I closed because the Weaveworks project manager for TF controller asked me to, but recent developments at Weaveworks have removed this impediment.

@uya116
Copy link

uya116 commented Jan 20, 2024

Thank you @paulcarlton-ww , @shanduur , @scottrigby !
Does this mean that if we wait, we will be able to use OpenTofu with the TF controller without having to build our own runner image?

@uya116
Copy link

uya116 commented Jan 23, 2024

I have understood the situation.
#1166

@chanwit
Copy link
Collaborator

chanwit commented Feb 27, 2024

This project is now rebooted and landed to the new home, which is 100% community driven.
We're now prioritizing OpenTofu support so any contributions are welcome!

@kvendingoldo
Copy link

At this moment if you need to have a support of Terraform as well as OpenTofu (and Terragrunt :) ) in one tool you can use https://github.com/tofuutils/tenv which my team wrote some months ago. A lot of users switched to that tool to unify version management in the world of Terraform.

You're welcome to open any issues or contribute to tenv.

@ilithanos
Copy link
Collaborator

At this moment if you need to have a support of Terraform as well as OpenTofu (and Terragrunt :) ) in one tool you can use https://github.com/tofuutils/tenv which my team wrote some months ago. A lot of users switched to that tool to unify version management in the world of Terraform.

You're welcome to open any issues or contribute to tenv.

I have to ask you to stop spamming your project in our tickets, it's not that it's a bad project, bit it literally has nothing to do with the tickets you try to advertise for it in.

It will not work in combination with the way tofu controller handles terraform, and there are other solutions now to use openTofu with the tofu-controller.

I know you are just trying to get attention to your project and get more contributers and users. But this is the wrong way to go about it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants