-
Notifications
You must be signed in to change notification settings - Fork 694
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
config: DRY up labels with annotations reference #639
config: DRY up labels with annotations reference #639
Conversation
from opencontainers#635 (comment) it was clear that all the rules for `Labels` are the same as annotations, so let's DRY that up a bit. Signed-off-by: Vincent Batts <[email protected]>
cc @stevvooe how's this? |
oh, hmm, seems reasonable enough |
Keys using the `org.opencontainers.image` namespace are reserved and MUST NOT be used by subsequent specifications. | ||
If there are no labels then this property MAY either be absent or an empty map. | ||
Implementations that are reading/processing this configuration file MUST NOT generate an error if they encounter an unknown labels key. | ||
This OPTIONAL property MUST use the [annotation rules](annotations.md#rules). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
While the other annotations references (e.g. here) use the “This OPTIONAL property…” pattern, config.md
puts the OPTIONAL/REQUIRED-ness in the same line as the property name (while manifest.md
does not). My preferred larger fix would be to follow runtime-spec and consistently declare OPTIONAL/REQUIRED-ness in the same line as the property name, but if that's too big to bite off here, I'd rather reword this line to not repeat OPTIONAL. Something like:
This property MUST use the annotation rules.
would be fine.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
follow up?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
follow up?
Filed as #642.
from
#635 (comment)
it was clear that all the rules for
Labels
are the same asannotations, so let's DRY that up a bit.
Signed-off-by: Vincent Batts [email protected]