Confirm Expected Tagging Behaviour in Docker Image Workflows

[aaronskiba]

Please complete the following fields as applicable:

What version of the DMPRoadmap code are you running? (e.g. v2.2.0)

• 4.1.1+portage-4.2.3

Expected behaviour:

• To be confirmed

Actual behaviour:

docker-push-image.yml runs whenever new release is published, and docker-push-uat-image.yml is run whenever a tag matching the pattern *-uat-* is pushed. In both cases, three tagged images are pushed to Docker Hub:

For a published release, the tags are:

• X.Y.Z (the version from the release tag),
• production
• latest

For a *-uat-* tag, the tags are:

• X.Y.Z-uat-D (derived from the pushed tag),
• uat
• latest

Is generating three tags (X.Y.Z or X.Y.Z-uat-D, production or uat, and latest) the intended behavior for this workflow?