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

Link fix

Browse Source 
Signed-off-by: AbstractionFactory <179820029+abstractionfactory@users.noreply.github.com>
Co-authored-by: Martin Atkins <mart@degeneration.co.uk>
This commit is contained in:
AbstractionFactory 2025-02-03 19:06:00 +01:00 committed by Martin Atkins
parent 1d2da46f25
commit 5fcf2096c6
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -11,7 +11,7 @@ However, thanks to the generic architecture of OCI registries, several implement
The OCI registry standardization and the implementation of the OpenTofu/Terraform Registry protocols (the latter used by OpenTofu) happened around the same time (see [here for providers](https://opentofu.org/docs/internals/provider-registry-protocol/) and [here for modules](https://opentofu.org/docs/internals/module-registry-protocol/)). These protocols followed different design goals. For example, the provider registry protocol concerns itself with artifact signing and decoupling the index and the download part of the registry, whereas OCI is concerned, for example, with layer pull efficiency. To this day OCI image signing is still in development and only a partially solved problem, with projects like [sigstore/cosign](https://www.sigstore.dev/) attempting to take a stab the issue.
> [!NOTE]
> We have created a [primer on OCI](20241206-oci-registries/oci-primer.md) for this RFC. If you are unfamiliar with the protocol, you may want to read it before reading this RFC.
> We have created a [primer on OCI](20241206-oci-registries/1-oci-primer.md) for this RFC. If you are unfamiliar with the protocol, you may want to read it before reading this RFC.
## Why OCI?