Changed package self-references to github.com/opentofu/tofu-exec

[Magnitus-]

Changed project self-references to be accurate given the change in name and organizations.

If nobody else is actively working on this project. I'll proceed to change terraform for tofu in the codebase and make other changes that are sensible to make it work with Opentofu.

As things are, unless there is another similar project in the works, we'll be dependent on this project to migrate to Opentofu.

[Lucasjuv]

@eranelbaz @cam72cam Can we get this going?

[cam72cam]

Just messaged the core team to discuss the path forward on this, apologies for letting this sit for a while!

[Magnitus-]

Just messaged the core team to discuss the path forward on this, apologies for letting this sit for a while!

Glad to hear it.

It's not a huge rush on our side (atm, older versions of terraform work for us), but as mentioned, we'll need something like this in order to transition to opentofu (we have a large number of pipelines we run on-prem and everything runs automatically in the background with an in-house tool).

Not sure how squeezed you are in terms of programmer resources and the degree of direct involvement opentofu maintainers want to have with this issue (we don't want to step on anybody's toes), but given that this is something we'll need, we're more than happy to work on this if it is helpful.

[Yantrio]

Hi, First off I want to say thank you for this contribution, however for now we're going to hold off merging this PR as we feel a bit unsure about if we want to maintain this package for public usage or not.

It will take some resources to maintain this package and we are trying to determine if we have the resources to manage this.

Thank you for your patience and understanding on this one.

In the meantime I do believe that terraform-exec can work with tofu. I have heard anecdotally that people have it running, but I am not aware of how to do this.

[Magnitus-]

I understand. Thanks for clarifying the current situation.

In that case, we'll tackle it independently on our end. I don't foresee it being a quickie so I'll schedule it with the team after I'm back from parental leave.

Let us know in the interim if you come up with an official gameplan to interact with opentofu programmatically.

[salyh]

I also suggest to update the code example in the README with the correct import statements

[RoseSecurity]

Is there any way I can support the management of this? I have downstream tooling that relies on tfexec and I would like to make it compatible with tofu exec as well

[Magnitus-]

Is there any way I can support the management of this? I have downstream tooling that relies on tfexec and I would like to make it compatible with tofu exec as well

Realistically, I don't expect to really work on this until late this year at the earliest, if there are no urgent mandates that needs tackling. I'm on part time on parental leave until then and a large portion of the limited time I work right now is spent assisting the the devops team and ensuring everything is smooth for them.

Like you, we have a tool that depends on tfexec and beyond resolving the self-references in the project, my game plan once I start tackling this is to do the following with our tool on our local dev environment:

• Get an opentofu binary
• Integrate this project in our tool's codebase instead of Haschicorp's tfexec
• Fix any compilation issue that occurs
• Fix any runtime issue that occurs
• Tentatively use the modified version on some of our less sensitive pre-prod terraform pipelines, let them run in our automation servers for a week or two, see what happens and fix any problems that occur
• Expend from there to the rest of our pre-production and then our production

If you are operating on a more time-sensitive timeline than we are with this and would rather not wait, that would be my personal recommendation on how to proceed. From there, we can share problems we encounter during integration.