971513049d
Previously the ReferenceTransformer just had a broad rule that any node which implements GraphNodeDestroyer has its expression references completely ignored. Now that we're starting to allow dynamic expressions for destroy-related settings like "prevent_destroy", we need to be able to represent the dependencies implied by those expressions. However, the assumption that configuration is mostly ignored when planning destroy is load-bearing for minimizing awkward dependency problems in the destroy-planning graph, so this introduces a new concept of "destroy references" which means that we can implement only a small, curated subset of references -- for now, just the ones from prevent_destroy -- that get considered for any node type that implements GraphNodeDestroyer. Having GraphNodeDestroyer effectively take priority over GraphNodeReferencer seems like the least disruptive way to retrofit this idea surgically as a small change to the previous unilateral rule against any references at all, because in practice all of the destroy nodes embed NodeAbstractResourceInstance and therefore implement GraphNodeReferencer, so it is important that we continue to ignore that type's GraphNodeReferencer implementation whenever it's embedded in something that is also a GraphNodeDestroyer. 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.