[release-0.2] images: fix the tagging docker images build from new tags #146
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When docker image build workflow is triggered based on the new tag push which usually includes v as prefix, the workflow drops the v prefix. As such, when
v0.2.0
tag is pushed to GitHub, we end up with0.2.0
tags in the docker images. This commit fixes the workflow to keep the v prefix. Currently, our deployments are taggingv0.2.0
tags for the plugins while published images don't include thev
and deployment are failing.