6915483ade
This is admittedly "scope creep" for a job that was originally intended only to run the end-to-end tests, but we have a separate e2etest job specifically because some of these tests interact with the live OpenTofu Registry and certain GitHub repositories and so it's nice to have these external dependencies isolated into their own job so that outages of any of these external services should only affect this one test job. The TF_ACC=1-constrained tests in packages initwd and registry are set up that way because they too interact with OpenTofu Registry and GitHub repositories, so grouping these together retains the idea of limited these external dependencies to only one job while giving us a little more test coverage for our PR checks. The motivation for doing this now is that both of these packages had acceptance tests that had been broken by changes in the past and we didn't notice because nothing was routinely running these tests: - package registry had been failing ever since OpenTofu existed because one of its tests seems to have been depending on an undocumented registry protocol feature that OpenTofu Registry has never implemented - package initwd got broken more recently by a change to use a dependency inversion style for the module installer's use of module registry client and package fetcher, but these particular tests were not passing in working clients for the module installer to use. Both of those problems were already fixed in earlier commits, and so this is just an attempt to avoid similar problems happening again in future. (This doesn't address the more common case of acceptance tests that require live credentials to access a service that doesn't support anonymous access. Those will still need to run manually in development environments because we cannot pass live credentials to a job that runs in response to third-party pull requests.) 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.