chore: candidate unique tag

candidate images will now have a unique name so they may be identified precisely.
this can help prevent all sorts of race conditions in our CI that relies on the candidate image for testing and retagging.

Author: Shesekino

.circleci/config.yml

@@ -37,7 +37,7 @@ jobs:
             npm run build &&
             npm run test:unit &&
             docker login --username ${DOCKERHUB_USER} --password ${DOCKERHUB_PASSWORD} &&
-            IMAGE_NAME_CANDIDATE=snyk/kubernetes-monitor:staging-candidate &&
+            IMAGE_NAME_CANDIDATE=snyk/kubernetes-monitor:staging-candidate-${CIRCLE_SHA1} &&
             ./scripts/build-image.sh ${IMAGE_NAME_CANDIDATE} &&
             docker push ${IMAGE_NAME_CANDIDATE} &&
             ./scripts/slack-notify-push.sh ${IMAGE_NAME_CANDIDATE} &&

scripts/approve-image.sh

@@ -8,7 +8,7 @@ if [ $1 == "null" ]; then
   echo Semantic-Release did not create a new version, not pushing a new approved image
   ./scripts/slack-notify-success-no-release.sh
 else
-  IMAGE_NAME_CANDIDATE=snyk/kubernetes-monitor:staging-candidate
+  IMAGE_NAME_CANDIDATE=snyk/kubernetes-monitor:staging-candidate-${CIRCLE_SHA1}
   IMAGE_NAME_APPROVED=snyk/kubernetes-monitor:${1}-approved
 
   docker pull ${IMAGE_NAME_CANDIDATE}