✨⚗️ Add additional docker image tag to simcore github actions (⚠️ DEVOPS)

[mrnicegyu11]

What do these changes do?

Currently, we push two docker image tags to each docker image (identified by its digest) that we upload to dockerhub. One is "short" and one is "verbose" (including built date and git sha), like so:

• master-github-2023-07-26--11-57.f6fa3ed338fa4875c76f02c37c22883bb660060d (this is only for archiving purposes, it is not used anywhere)
• master-github-latest (we use this actually)

This is equivalent for staging and production. For master, this works fine with respect to the osparc-deployment-agent. We watch (read: poll / querry) for new docker images corresponding to the tag master-github-latest, and we if we find one, we roll it out.

We do the same for staging and production, but here this approach is not perfect. Ideally, we would want to roll out not the latest staging or release docker images, but the ones corresponding to the precise git tag that we are rolling out (e.g. staging_Sundae1 or v1.56.0). The deployment-agent has the information about which staging/production he is currently rolling out, given as the git tag of the github/gitlab repositories. In the past, we had issues during releases when docker image tags (like release-github-latest) were generated some minutes after the corresponding git-tag in osparc-simcore, etc.

This PR brings a third naming convention to the docker image tags, which corresponds exactly to the current (pre-)release name. For master, no third docker image tag will be added, all will stay the same. For staging, this PR would make github actions create the following docker image tags on dockerhub:

• staging-github-staging_Sundae1-2023-07-26--09-09.9988654d8bcdabba452321e45408e539bedc2669
• staging-github-latest
• ✨ staging_Sundae1

The same would be the case for production.
In a next step, the deployment agent can be adjusted to utilize these specific docker image tags on dockerhub. This will mitigate some issues we have seen during simcore-releases in the past.

BONUS:

• Github-Action Debug step that prints env-vars now prints them sorted alphabetically.

Related issue/s

I guess there are some, didnt go through the hazzle of compiling them here :(

How to test

Merge it and pray.

DevOps Checklist

To be checked once this is merged:

• Master github-actions still work
• Staging Release github-actions still work
• Production release github-actions still work
• Staging Hotfix github-actions still work
• Production Hotfix github-actions still work

[codeclimate]

Code Climate has analyzed commit 3bc4cf6 and detected 0 issues on this pull request.

View more on Code Climate.

[sanderegg]

this looks ok and I do not see any issue with doing this as long as there is no overwrite of the same tag.

I guess this might simplify your code a bit.

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
0.1% Duplication