mirror of
https://github.com/opentffoundation/opentf.git
synced 2025-12-19 17:59:05 -05:00
Added future plans
Signed-off-by: AbstractionFactory <179820029+abstractionfactory@users.noreply.github.com>
This commit is contained in:
committed by
Martin Atkins
parent
3468302422
commit
0fa58254ce
@@ -50,4 +50,8 @@ These solutions would also work towards the goal of making the ecosystem fully d
|
||||
|
||||
That being said, neither of these solutions are as convenient as OCI since the infrastructure for this protocol is ubiquitous and cheap.
|
||||
|
||||
## Future plans
|
||||
## Future plans
|
||||
|
||||
When it comes to providers, the current RFC mainly addresses OCI as a private registry for providers. This is a limitation stemming from the fact that provider addresses are virtual, as described in [Design Considerations](20241206-oci-registries/3-design-considerations.md). In a future OpenTofu version we would like to address this shortcoming and enable everyone to use OCI as a public provider source without relying on configuration options in the `.tofurc` file.
|
||||
|
||||
Additionally, currently the OCI registry implementation doesn't have the equivalent of the [OpenTofu Registry Search](https://search.opentofu.org). We envision this to be resolved similar to how Linux packages often publish a supplemental `doc` package, containing the related documentation. This, however, will need tooling in OpenTofu to render and show that documentation. While much of the code can be reused from the [Search source code](https://github.com/opentofu/registry-ui), that project was not written with reuse in mind and will need some additional work to adapt as a general-purpose documentation viewer.
|
||||
Reference in New Issue
Block a user