e1a4f00b16
Along with all of the usual purely-mechanical updates that we get from these upgrades, these upgrades also introduce the ability for OpenTofu's "s3" state storage backend to make use of credentials issued by the "aws login" command recently added to the official AWS CLI. Behind the scenes, this command uses OAuth to issue a refresh token, and then the AWS SDK implementation uses that refresh token to request time-limited session credentials. Successfully running "aws login" causes there to be a new "login_session" setting in the AWS config file, specifying which principal ARN was used to log in. Whenever that setting is present, the SDK expects to find a valid refresh token in a new cache directory kept in "~/.aws/login", and will fail if no valid token is present in that cache directory. Signed-off-by: Martin Atkins <mart@degeneration.co.uk> |
||
|---|---|---|
| .github | ||
| cmd/tofu | ||
| contributing | ||
| docs | ||
| internal | ||
| rfc | ||
| scripts | ||
| testing | ||
| tools | ||
| version | ||
| website | ||
| .copywrite.hcl | ||
| .devcontainer.json | ||
| .gitattributes | ||
| .gitignore | ||
| .golangci.yml | ||
| .goreleaser.yaml | ||
| .licensei.toml | ||
| .tfdev | ||
| CHANGELOG.md | ||
| CHARTER.md | ||
| CODE_OF_CONDUCT.md | ||
| codecov.yml | ||
| CODEOWNERS | ||
| CONTRIBUTING.md | ||
| CONTRIBUTING.RELEASE.md | ||
| Dockerfile | ||
| Dockerfile.minimal | ||
| go.mod | ||
| go.sum | ||
| GOVERNANCE.md | ||
| LICENSE | ||
| MAINTAINERS.md | ||
| Makefile | ||
| README.md | ||
| RELEASE.md | ||
| SECURITY.md | ||
| WEEKLY_UPDATES.md | ||
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.
Getting help and contributing
- Have a question?
- Post it in GitHub Discussions
- Open a GitHub issue
- Join us in the #opentofu channel on the CNCF Slack!
- Want to contribute?
- Please read the Contribution Guide.
- Recurring Events
- Community Meetings on Wednesdays at 12:30 UTC (calendar)
- Technical Steering Committee Meetings every other Tuesday at 4pm UTC (calendar)
Tip
For more OpenTofu events, subscribe to the OpenTofu Events Calendar!
Key features
-
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
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.
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. For more details, see the Registry Inclusion Policy.