Skip to content
This repository was archived by the owner on May 15, 2024. It is now read-only.

Conversation

@wmesard
Copy link

@wmesard wmesard commented Aug 9, 2022

I have a use case where each element in the blobs array is associated with the corresponding element in the layers array of the referent OCI image. However, a blob may be omitted for any particular layer. Therefore, I would like to modify the description of blob elements to explicitly state that nulls are allowed.

If this PR is accepted, I will submit a PR against oras-go to allow that.

The workaround (if the current PR is not accepted) would be to create a zero-length artifact, just so that I'll have something to stick in the array, and push to the remote. This is doable, but less elegant.

@sajayantony
Copy link
Contributor

@wmesard given that the OCI working group is closer to landing a proposal - my hope is that ORAS will consume/produce the OCI artifact as the project does stand for "OCI Registry As Storage" :)

It would be good to continue the discussion here - opencontainers/image-spec#934 (comment) and gauge if there is a desire to do something like this. I think the push would be to use an annotation in the blob rather than try to map the index of the element.

@wmesard
Copy link
Author

wmesard commented Aug 15, 2022

Closing this PR in favor of the similar comment I posted over in opencontainers/image-spec#934 (comment)

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants