Closed korridor closed 2 years ago
Hello and thank you for your proposal and use case 👌
This is a backend related task to create and manage new image registry entries, I added this to our todo list and I will close this issue (without locking the conversation of course)
I'll update this issue according to our internal roadmap
Currently, the container deployment process just pushes into the
latest
tag. It would be great if the deployment process would create a new tag for each deployment. At the moment, if I deploy something and the build succeeds, but the running container does not work (f.e. because of a bug in the applications code), as far as I understand the current system, there is no fast way to roll back. With a tag per deployment I could change just change the tag in the Scaleway Console and redeploy which is way faster than having to rebuild the previous state and then deploy.