fix: also push image-tag-based metadata tag when syncing container images#142
Merged
fix: also push image-tag-based metadata tag when syncing container images#142
Conversation
…ages Signed-off-by: Tomas Pizarro Moreno <tomas.pizarro@broadcom.com>
beltran-rubo
approved these changes
Mar 20, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Description
When pushing metadata artifacts to a target registry, only the sha256-based tag (
sha256-<hex>.metadata) was being published. The source registry also provides a shorter, human-readable metadata tag (<image-tag>-metadata, e.g.39.0.1-redhatubi-9-r2-metadata) that makes it easy to match security artifacts with their associated image.Changes
Modified
pkg/artifacts/artifacts.goto introduce a new internal functionpushMetadataTagsthat pushes the same local OCI-layout artifact to the target registry under both tag formats:sha256-<hex>.metadata— digest-based tag (existing behaviour, unchanged)<image-tag>-metadata— human-readable tag (new)The pull side is left unchanged: artifacts are still fetched from the source using the sha256-based tag, which has always been present.