This commit rescopes what was originally a draft about provider installation from OCI registries into a more general document about how we intend to use OCI container images and OCI registries as a distribution vehicle for at least two different kinds of OpenTofu dependency packages (module and provider packages). This document already had good content about how OCI registries and artifacts work _in general_, and its associated PR was already attracting general discussion about whether to use Docker-style or ORAS-style conventions across both provider and module packages, so we'll now use this document to discuss just the overall question of what style of packaging we intend to use (across both package types) and will discuss the module-specific and provider-specific details in other RFCs. This also reworks the document to now propose using the Docker-like conventions instead of the ORAS-like conventions, since that matches what we've been exploring in prototypes. Of course, that decision is not final until this RFC is accepted and merged, but we have considerably better understanding of how this would work under the Docker-like approach than ORAS and it seems like consensus is so far heading in that direction. We may revise this document again if we learn of some strong arguments in favor of the ORAS approach. Signed-off-by: Martin Atkins <mart@degeneration.co.uk> |
||
---|---|---|
.github | ||
cmd/tofu | ||
docs | ||
internal | ||
rfc | ||
scripts | ||
testing | ||
tools | ||
version | ||
website | ||
.copywrite.hcl | ||
.devcontainer.json | ||
.gitignore | ||
.go-version | ||
.golangci-complexity.yml | ||
.golangci.yml | ||
.goreleaser.yaml | ||
.licensei.toml | ||
.tfdev | ||
CHANGELOG.md | ||
CODE_OF_CONDUCT.md | ||
codecov.yml | ||
CODEOWNERS | ||
CONTRIBUTING.md | ||
CONTRIBUTING.RELEASE.md | ||
Dockerfile | ||
Dockerfile.minimal | ||
go.mod | ||
go.sum | ||
LICENSE | ||
MAINTAINERS | ||
Makefile | ||
README.md | ||
RELEASE.md | ||
SECURITY.md | ||
tools.go | ||
TSC_SUMMARY.md | ||
WEEKLY_UPDATES.md |
OpenTofu
- Manifesto
- About the OpenTofu fork
- How to install
- Join our Slack community!
- Weekly OpenTofu Status Updates
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 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.