opentofu / get.opentofu.org Goto Github PK

The website hosting the OpenTofu Installer script and installation resources

License: Apache License 2.0

TypeScript 0.76% Shell 61.81% PowerShell 28.65% Dockerfile 0.02% Go 8.76%

get.opentofu.org's Introduction

OpenTofu

OpenTofu is an OSS tool for building, changing, and versioning infrastructure safely and efficiently. OpenTofu can manage existing and popular service providers as well as custom in-house solutions.

The key features of OpenTofu are:

Infrastructure as Code: Infrastructure is described using a high-level configuration syntax. This allows a blueprint of your datacenter to be versioned and treated as you would any other code. Additionally, infrastructure can be shared and re-used.
Execution Plans: OpenTofu has a "planning" step where it generates an execution plan. The execution plan shows what OpenTofu will do when you call apply. This lets you avoid any surprises when OpenTofu manipulates infrastructure.
Resource Graph: OpenTofu builds a graph of all your resources, and parallelizes the creation and modification of any non-dependent resources. Because of this, OpenTofu builds infrastructure as efficiently as possible, and operators get insight into dependencies in their infrastructure.
Change Automation: Complex changesets can be applied to your infrastructure with minimal human interaction. With the previously mentioned execution plan and resource graph, you know exactly what OpenTofu will change and in what order, avoiding many possible human errors.

Getting help and contributing

Have a question? Post it in GitHub Discussions or on the OpenTofu Slack!
Want to contribute? Please read the Contribution Guide.
Want to stay up to date? Read the weekly updates, TSC summary, or join the community meetings on Wednesdays at 14:30 CET / 8:30 AM Eastern / 5:30 AM Western / 19:00 India time on this link: https://meet.google.com/xfm-cgms-has (📅 calendar link)

Tip

For more OpenTofu events, subscribe to the OpenTofu Events Calendar!

Reporting security vulnerabilities

If you've found a vulnerability or a potential vulnerability in OpenTofu please follow Security Policy. We'll send a confirmation email to acknowledge your report, and we'll send an additional email when we've identified the issue positively or negatively.

Reporting possible copyright issues

If you believe you have found any possible copyright or intellectual property issues, please contact [email protected]. We'll send a confirmation email to acknowledge your report.

License

Mozilla Public License v2.0

get.opentofu.org's People

Contributors

Stargazers

Watchers

Forkers

cam72cam timofurrer jjshanks sanskruti-shahu kazzhar bunniseng ksemele matthewjohn

get.opentofu.org's Issues

Provide latest OpenTofu release via ./install-opentofu.sh --install-method apk

OpenTofu Version

1.6.2-r2

Use Cases

Installing OpenToFu in Container-Images, e.g. for automation with GitLab or GitHub Actions

Attempted Solutions

The standalone installer allows to use some parameter --opentofu-version "${OPENTOFU_VERSION}" to install the OpenToFu version defined in ${OPENTOFU_VERSION}.

./install-opentofu.sh --install-method apk --opentofu-version "${OPENTOFU_VERSION}"

The installer using the install-method apk does not support this version argument.

./install-opentofu.sh --install-method apk

The parameter --opentofu-version "${OPENTOFU_VERSION}" is ignored.

Additionally the apk-installer installs version 1.6.2-r2 whereas the standalone-installer installs 1.7.1 or OpenToFu.

Proposal

Please support the argument --opentofu-version "${OPENTOFU_VERSION}" for the apk-installer and provide all release-versions via the apk-installer.

References

No response

GPG verification support for Windows

Currently, the Windows version of the installer script doesn't support GPG. The install guide claims they do, so this should be fixed.

The script is running this command:

gpg.exe --no-default-keyring --keyring ...\opentofu.asc.gpg --verify ...\tofu_1.6.0_SHA256SUMS.gpgsig ...\tofu_1.6.0_SHA256SUMS

The main issue is that GnuPG 2.4 I have installed on Windows (as opposed to 2.2 on Linux) seems to not be able to use keyrings like this:

gpg.exe --no-default-keyring --keyring ...\opentofu.asc.gpg --list-keys

Linux install script should support hardened environments

See opentofu/opentofu#1126

Installer bug: usage not shown if install-method is not selected

When no install-method is selected, the Bash script does not emit usage info. Also, it does not error on an incorrect install-method.

Add shellcheck to CI

Add shellcheck to the CI pipeline.

Code signing for scripts

It would be good if the installer scripts were signed via cosign/GPG/signing certificate.

This is currently a low priority issue, please thumbs up this issue if it is important to you.

Install scripts: remove support for alpha and beta versions

Currently, both the Powershell and the POSIX script support standalone installations with early alpha and beta releases, which needs some extra code, for example:

https://github.com/opentofu/get.opentofu.org/blob/main/src/install-opentofu.ps1#L325
https://github.com/opentofu/get.opentofu.org/blob/main/src/install-opentofu.sh#L748
https://github.com/opentofu/get.opentofu.org/blob/main/src/install-opentofu.sh#L831

However, we should explicitly warn users that these versions cannot be installed using the script to avoid confusion.

As 1.6.0 is stable, it is unlikely that someone would want to install these early versions. In addition, alpha versions don't work with the current registry anymore.

Note: we are not removing the early binaries, merely the support for installing them via an install script. You can still download any of the early binaries from the releases page.

Self-update for shell scripts

Add a functionality that updates the installer script from the installer script while making sure that the script is correctly signed. This requires the scripts to be signed via GPG / a code signing certificate.

This is currently a low priority issue, please thumbs up this issue if this is important for you.

Specify OpenTofu version in standalone mode

When running:

./install-opentofu.sh --install-method standalone --opentofu-version 1.6.0

the script currently fails with:

Error: Unknown option: --opentofu-version.

Judging by looking at the script it looks like the --opentofu-version option is simply not implemented.

This is currently a blocker for us and it would be great to have a fix for this :)

OpenSUSE Installation correction

Discussed in https://github.com/orgs/opentofu/discussions/1176

^{Originally posted by sentairanger January 22, 2024}
I successfully installed Open Tofu on OpenSUSE, however this line caused an issue when I first attempted to install.

./install-opentofu.sh --install-method rpm

I resolved this by adding sudo. This should be updated to reflect that.

Fix PackageCloud archive upload in release pipeline

In https://github.com/opentofu/opentofu/releases/tag/v1.7.2 version 1.7.2 of OpenTofu was released. As far as I can see this release is distributed in the Alpine Edge community repos (see https://pkgs.alpinelinux.org/package/edge/community/x86_64/opentofu) already.

Unfortunately, it seems like https://packages.opentofu.org/opentofu/tofu/ is still missing this release. I'm a little surprised by that, because the build assets of https://github.com/opentofu/opentofu/releases/tag/v1.7.2 show the files, so it doesn't seem to be a build or availability issue.

It feels like they were never placed (automatically) in the repos for the traditional package managers like apt or yum. Maybe some automation got stuck?

Can you have a look or move/copy this issue to the appropriate project?