4fc494ef8a
The idea is quite simple but the commited implementation is definitely not in the final shape. Right now, OpenTofu is handling the providers, from the installation, sub-process mantainance, configuration and cleanup of it. By doing so, this adds a lot of run time. This commit is exploring on how to instruct OpenTofu to work with providers pre-configured and hosted by a different process. Therefore, a providers server has been created and can be found in https://github.com/opentofu/hackathon-providers-server. With this commit, was introduced the support of this new experimental block: terraform { // ... preconfigured_providers { playground = { source = "opentofu/playground" addr = "localhost:50051" protocol_version = 6 } } } Having this configured, OpenTofu will just create a gRPC client to communicate with the indicated addr. The server is running the same protobuf schema and it's supposed to function exactly the same as a provider mantained by OpenTofu itself. One important thing to note, is that for every provider that is registered in OpenTofu as pre-configured, the following calls should not be performed: * ValidateProviderConfig * ConfigureProvider Signed-off-by: Andrei Ciobanu <andrei.ciobanu@opentofu.org>
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.