You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now referenced images are pushed with just their digest to the destination registry. Is there value in allowing the tool or user to decide to preserve the original tag as well?
The text was updated successfully, but these errors were encountered:
In our case we have a microservices based software that is installed as part of other platform then deployed mostly to airgapped environments to their customers.
Individual components following mostly semver approach, where we have a platform release denoted for the overall release, e.g. 1.2 but a new component in that release will use 1.0 and some components that had significant changes, might be on 1.4.
As we do not have much control over how these images will be relocated it'd help us to easily identify the actual version based on tags, instead of hashes.
Also according to image relocation currently tags could be defined in relocation maps, hence they could be preserved. https://github.com/cnabio/cnab-spec/blob/master/103-bundle-runtime.md#relocation-mapping
Right now referenced images are pushed with just their digest to the destination registry. Is there value in allowing the tool or user to decide to preserve the original tag as well?
The text was updated successfully, but these errors were encountered: