IntenseWebs/opentofu
3
0
Fork 0
mirror of https://github.com/opentofu/opentofu.git synced 2025-02-25 18:45:20 -06:00
Code Issues Packages Projects Releases Wiki Activity

Added potential alternatives

Browse Source 
Signed-off-by: AbstractionFactory <179820029+abstractionfactory@users.noreply.github.com>
This commit is contained in:
AbstractionFactory 2025-02-07 15:04:55 +01:00 committed by Martin Atkins
parent 4923e96ef1
commit 59d3d8f92b
1 changed files with 10 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
rfc/20241206-oci-registries.md
View File

@ -41,3 +41,13 @@ The following additional sections discuss potential implementation details of th
9. [Authentication-related implementation details](20241206-oci-registries/9-auth-implementation-details.md)
10. [Provider installation implementation details](20241206-oci-registries/10-provider-implementation-details.md)
11. [Module installation implementation details](20241206-oci-registries/11-module-implementation-details.md)
## Potential alternatives
OCI resolves a very real pain-point for enterprise users wanting to run a private registry. A potential alternative would be, of course, making the use of a private registry easier, or creating a tool that can maintain a private registry purely based on static files. On that note, we could also implement running the OpenTofu Registry on the same dataset privately, which has been [documented in this issue](https://github.com/opentofu/registry/issues/1518).
These solutions would also work towards the goal of making the ecosystem fully decentralized.
That being said, neither of these solutions are as convenient as OCI since the infrastructure for this protocol is ubiquitous and cheap.
## Future plans