manipulate content as artifact.OCI interface
#59
Merged
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
…l content using oci layouts Signed-off-by: Josh Wolf <josh@joshwolf.dev>
…ean up layer interface used by file/chart
This was
linked to
issues
Nov 10, 2021
This was
linked to
issues
Nov 10, 2021
Closed
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.
defines
artifact.OCIas a "generic" type of content that minimally defines how to store content in an oci layout. Use the oci layout spec as the transport mechanism between sinks (registries for now).This better defines the
contentfootprint as extendable interfaces, but also sets us up better for the future with user definedcontent/collections.This also closes a bunch of other issues (linked).