internal/urlutil: support downloading OCI artifacts #33
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jroimartin
force-pushed
the
oci
branch
2 times, most recently
from
c940a0b to
ff3be14
Compare
|
I have converted this PR into a draft. We don't have enough experience dealing with OCI artifacts and it seems a bit risky to support them from v1.0.0. On the other hand, it is clear that we have to support HTTP (which is already implemented). So, let's start by serving the catalog via HTTP. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds support for downloading OCI artifacts to the package
internal/urlutil. It adds support for a new scheme:oci://: OCI artifact (via HTTPs)This enables us to distribute checktype catalogs as OCI artifacts.
Registry authentication will be added in a future PR.