Use manifest-tool/docker manifest to "retag" manifests for staging?

[estesp]

Use manifest-tool/docker manifest to "retag" manifests for staging?

[estesp]

Hey @StefanScherer can you let me know if you think #32 helps here? You would still need the YAML definition, but would allow you to roughly "remote tag" an existing tag, although it would do the calculations of cross-repo mounts, digests, etc. for the original tag first. Almost wonder if there is a use case here for a true "remote tagging" operation by just pulling the manifest (in your case the org/app:testing existing manifest list) and pushing it with the new tag. That would require no extra calculations or cross-repo blob mounts as the command would expect all that "worked" because the image/manifest is already in the registry.

[StefanScherer]

Thanks @estesp. Between tagging "testing" and "production" there are running tests to multiple such images. When all the images pass the tests we want to tag all them that have the "testing" tag and tag it for next stage.
Otherwise we have to handle lots of different version numbers of each microservice (semver per service).
So #32 doesn't help here (but looks good to tag major-only, major+minor, ... tags 👍 ) as it is not at the same time to create both tags.
Any other idea/best practise to move several images that have independent version numbers from one stage to another?