Allow to provide custom OCI annotations #133
Open
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.
Hey ππ»
Description
This pull request basically allows to provide custom OCI annotations to be added to the final artifacts (using either
apko-publish
orapko-snapshot
actions).If we want to add annotations without these changes, we likely need to use a separate action to update the config file before calling
apko-publish
(orapko-snapshot
) (see example) or implement some other workaround. The main idea here is to make this process easier.Basic Testing
apko-publish
: this version worked well here (see job, for instance).example manifest
revision
,created
, andversion
are the annotations we are interested in.apko-snapshot
: this version is working well here (see job, for instance).example manifest
revision
,created
, andversion
are the annotations we are interested in.Let me know if these changes make sense for this project or if you have any concerns.