document different docker tagging strategies about kalix-jvm-sdk HOT 5 OPEN

The reason that we use timestamp across the samples is that k8 will not always pick up latest from re-used tag and we saw users having problems with deploying new versions of their projects. A unique timestamp-tag makes sure that the version of the image deployed is the intended one.

from kalix-jvm-sdk.

Does commit id work if you iterate on a project without comitting, but redeploying several times (does it add a +n or something?)

from kalix-jvm-sdk.

Unfortunately not. Here is everything that could be part of the description: https://github.com/git-commit-id/git-commit-id-maven-plugin/blob/master/docs/git-describe.md

In that case, maybe we could give some hints to the users in docs/pom.xml samples with a link to the plugin.

from kalix-jvm-sdk.

Or in the CI/CD documentation perhaps? I guess another option could be to explicitly specify a tag from somewhere else, the CI run or the git tag for example when triggering deploy from a "release" tag like we do for many projects.

from kalix-jvm-sdk.

Yeah, we could clarify that users can apply different versioning/tagging strategies and slightly warn the timestamp might not be a good idea for production setup.

from kalix-jvm-sdk.