9d7e64bcfb
This RFC describes an alternative approach for issue #300 that treats it as a dynamic evaluation problem rather than as an early-eval problem. For the moment my goal of this proposal is not to actually replace the existing early eval proposal, but rather to draw attention to some aspects of it that would be difficult to translate to fully-dynamic eval if we heard requests for that later. This document therefore aims to ask the question of firstly whether we'd like to impose some similar constraints on the early eval approach even though they aren't strictly needed there, and secondly whether this realization that we don't have any current experience retroactively changing a feature from early eval to dynamic eval represents enough risk that we might prefer to put even the early-eval approach on pause while we analyze the potential risks in more detail. It's likely that if we _did_ choose to implement the dynamic approach we'd want to refine this RFC further to draw out some more detail in the implementation section. I've intentionally skimped on that section here because the priority is to have the conversation about the potential new user-facing constraints, and not to actually implement what this proposal describes in the near future. The implementation details are included as a starting point, but are insufficiently detailed to actually begin implementation. 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.yml | ||
| .goreleaser.yaml | ||
| .licensei.toml | ||
| .tfdev | ||
| CHANGELOG.md | ||
| CODE_OF_CONDUCT.md | ||
| codecov.yml | ||
| CODEOWNERS | ||
| CONTRIBUTING.md | ||
| Dockerfile | ||
| 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.