05c27d982f
The GODEBUG environment variable is a side-channel that allows dynamically opting in to a million billion different variations of Go runtime and standard library behavior, and we can obviously not routinely test OpenTofu's behavior across all of those different variations. Just in case someone encounters a problem caused by running OpenTofu with a combination of settings that are not enabled in our default build configuration, we'll include an explicit note in the logs so that we can tell when we're investigating a bug report that it might only be reproducible when the Go runtime behavior has been overridden in this way, and so that someone debugging their own problem can notice that they are using OpenTofu in an unsupported way and could potentially solve their own problem by unsetting that environment variable. This is a generalization of the previous addition of a log message when running in FIPS 140-3 mode, which is also updated here to use [WARN] instead of [WARNING] as the prefix because our logging system does not actually understand "WARNING" as a valid prefix. Keeping the separate specialized message for FIPS 140-3 mode is warranted because we _know_ that OpenTofu does not behave as intended when that mode is enabled, while we've not tested with any other combination of settings so we cannot predict whether they will cause misbehavior or not. Signed-off-by: Martin Atkins <mart@degeneration.co.uk>
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
- Open a GitHub issue
- Join the OpenTofu Slack!
- Want to contribute?
- Please read the Contribution Guide.
- Recurring Events
- Community Meetings on Wednesdays at 12:30 UTC at this link: https://meet.google.com/xfm-cgms-has (📅 calendar link)
- Technical Steering Committee Meetings every other Tuesday at 4pm UTC at this link: https://meet.google.com/cry-houa-qbk (📅 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 liaison@opentofu.org. We'll send a confirmation email to acknowledge your report.
Registry Access
In an effort to comply with applicable sanctions, we block access from specific countries of origin.