Hello, I’m having an issue where Qovery won’t deploy the latest version of my image when the tag has already been deployed previously (eg.
- from Github Action CI,
- when a production deployment workflow is triggered
- I tag the to-be-deployed images with the
productiontag on my image repository (ie. AWS ECR)
- using the Qovery CLI, I instruct Qovery to deploy my service using the tag
During the previous deploy Qovery has already deployed my service with the
production tag, but during a new deploy, the image tagged with
production is a new and different image.
However Qovery seems to be deploying a previous image.
backend:production image cached at the Qovery level (ie. Qovery image mirroring process qovery-mirror-2274d177-cf13-4316-ac22-bfc52abf9312)?
What can I do to ensure that Qovery deploy the latest image using my
More info :
My container service setting on Qovery
Settings > General > Container settings > Image Tag
seems to be updated each time I deploy using the CLI
qovery container deploy \ --organization my-org \ --project my-org-monorepo \ --environment prod \ --container "backend" \ --tag production \ --watch
In the meantime I updated the workflow to use the git commit hash of my images to prevent Qovery deploying an older version of my image (eg. backend:2274d1c)