Force overwrite of docker images in github actions

[prasadtalasila]

The github actions are supposed to publish only new versions of packages. This behavior is observed in npm packages but not docker images. In the case of docker images, all the commits to client/ or servers/lib of feature/distributed-demo branch result in overwrite of existing images. This behavior is undesirable.

[nichlaes]

@prasadtalasila can you describe a bit more in depth, what the desired behavior is?

[prasadtalasila]

@nichlaes
If the same version of docker image is already in the github container image registry, github actions must skip the docker image publication.

[prasadtalasila]

@nichlaes
This github action does not go to docker image publishing unless the npm publishing is successful. Does lib-ms.yml has the problem described in this issue?

[prasadtalasila]

@nichlaes This github action does not go to docker image publishing unless the npm publishing is successful. Does lib-ms.yml has the problem described in this issue?

The docker publication job in the lib-ms depends on npm-publish-package job and this workflow graph shows the dependence clearly. Thus an npm package publish fails, docker image publish also fails. So it is not a problem for lib-ms package.

The problem is with the client. The docker publication job in the client only depends on the successful running of the tests.
This workflow graph of client shows the problem clearly. If the tests are successful, docker image is either newly published or existing image rewritten.

The PR can be confirmed by checking the result on the client docker image.