OpenTofu lets you declaratively manage your cloud infrastructure.
OpenTofu lets you declaratively manage your cloud infrastructure.
Homepage | Slack | Get Started
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.
[!TIP] For more OpenTofu events, subscribe to the OpenTofu Events Calendar!
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.
Nightly builds are available for testing the latest changes on main. These are experimental and not intended for production use. Each build is removed after 30 days.
Nightly builds can be found at https://nightlies.opentofu.org/nightlies. For those who want to automate with tooling, https://nightlies.opentofu.org/nightlies/latest.json will be kept up to date with the latest build information.
For more details, see RELEASE.md.
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.
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.
In an effort to comply with applicable sanctions, we block access from specific countries of origin. For more details, see the Registry Inclusion Policy.
prevent_destroy from a variable makes destroy unplannable when a count/for_each module instance is removed
[v1.13] Add warning when `base64gzip` or `base64gunzip` usage is detected in resource arguments
tofu does not supply available credentials (for example from credentials.tfrc.json) to the http request attempting to download a provider package from a registry.
tofu test: a run block's `variables` cannot reference the test file's top-level `variables`
Top-Ranking Issues 📊
Mocked module executing code in test scenario
Sequential Groupings
RFC tracker: Linting support
`-target` makes a non-targeted module instance evaluate its resources as an empty tuple, failing the plan
A first-class `tofu drift` command for detecting infrastructure changed outside of OpenTofu