-
Notifications
You must be signed in to change notification settings - Fork 102
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Migrate to OCI Artifact from ORAS Artifact #271
Comments
Should we start a new branch for OCI now that you have go structs for OCI. Similarly, for oras - CLI? |
Any update on this work? |
@rdpsin We will be working on this after releasing |
Just a clarification that we'll need to maintain support for ORAS artifacts, until all registries have migrated to the OCI Artifact spec.
|
The initial iteration will not have the fallback to ORAS Artifact referrers. The fallback will be added in the second iteration after proper discussions. |
Oras needs to consume RC2 since it includes the subject field - opencontainers/image-spec#958 |
What fallback are we talking about here? From what I read, it seemed like falling back to ORAS Artifacts wouldn't be compatible with the tag-based fallback already proposed in the OCI distribution-spec, now an RC. |
On the call today we discussed that the fall back to ORAS is not going to be supported. This issues needs to be updated to reflect that and the next update to the libraries will remove the ORAS artifact types and move to OCI with OCI image fallback. |
Closing as all sub tasks are resolved. |
We will migrate to OCI Artifact from ORAS Artifact once the following PRs are merged.
Tasks:
artifactspec.Descriptor
toocispec.Descriptor
#307oras.PackArtifact()
intooras.Pack()
#309oras.ExtendedCopy()
caused by information loss due to descriptor conversions #310Referers
API #311subject
field #312subject
field #347This issue covers #267 and #268.
The text was updated successfully, but these errors were encountered: