Skip to content
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

Alignment/Consolidation of Predefined Annotations to Support Artifact Types #980

Closed
sabre1041 opened this issue Dec 10, 2022 · 8 comments
Closed
Assignees

Comments

@sabre1041
Copy link

Currently, there is guidance on the set of predefined annotation keys that can be placed upon the different types. However, with the addition of artifact type, there are only two annotations that are explicitly documented.

  • org.opencontainers.artifact.created
  • org.opencontainers.artifact.description

The majority of the annotations prefixes which are currently documented using the org.opencontainers.image.* would also apply to artifacts in addition to the two that were previously documented.

Updated guidance and documentation is needed if indeed these same keys also apply to artifact types.

@imjasonh
Copy link
Member

This specification defines the following annotation keys, intended for but not limited to image index, image manifest, artifact, and descriptor authors.

I interpret this to mean that all the annotations can be used for images, artifacts, indexes, and descriptors. It's a bit of an unfortunate misnomer, but I think we should interpret the spec to mean that, e.g., org.opencontainers.image.documentation is still usable by an artifact manifest.

If there's wording you think could help make this clearer, feel free to propose some here or send a PR.

@sudo-bmitch
Copy link
Contributor

I had briefly considered duplicating the annotations for artifacts, but that felt worse than using the image annotations for artifacts. It's more work for consumers to search multiple names and handle conflicts if both are defined. So I agree with @imjasonh that using the image annotations for artifacts is a valid use.

@sabre1041
Copy link
Author

sabre1041 commented Dec 14, 2022

@sudo-bmitch @imjasonh Perfect, and it aligns with my thoughts as well.

As for the documentation, propose that the annotations be modified to a form similar to org.opencontainers.<type>.created and defining the valid types explicitly beforehand (ie image and artifact).

Thoughts?

@sajayantony
Copy link
Member

Duplication of annotations also makes conversions harder. Don’t see any concern reusing the defined annotations for multiple manifest even though they are under .image.

@sajayantony
Copy link
Member

@sabre1041 - Do we need additional verbiage now since the both manifests now have an artifactType and with #1078 avoids the duplicates. Basically trying to close out all issue in the v1.1 milestone.

As per annotations.md


This specification defines the following annotation keys, intended for but not limited to image index, image manifest, and descriptor authors.

@jdolitsky
Copy link
Member

this may not make any sense after #999 ? should we close?

@jonjohnsonjr jonjohnsonjr removed this from the v1.1.0 milestone Jun 22, 2023
@tianon
Copy link
Member

tianon commented Jun 24, 2023

I agree; I would personally have used the existing annotations for artifacts too, and having consolidated artifacts under the image manifest makes that seem even more correct. 😅

@sabre1041
Copy link
Author

Closing as artifact specific annotations have been removed, thus there is no longer any overlap to support consolidation

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants