Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do * not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment
Tell us about your request
What do you want us to build?
Disclaimer: this is not the built-in rollback ability of the blue/green deployment.
When using the build from code method, save the previous deployment to allow us to rollback to it. This could be a "Roll back" button next to the "Deploy" button in the console. If a deployment is pushed that passes the health check, but has breaking business logic changes, it would be wonderful to rapidly roll back to the prior deployment rather than waiting at least 5 minutes to merge, build, and health check the next image.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
The alternative to recover from the scenario provided is to wait at least 5 minutes to build and health check a new image.
Additional context
Anything else we should know?
Mainly relevant for the build from code deployment method.
Attachments
If you think you might have additional information that you'd like to include via an attachment, please do - we'll take a look. (Remember to remove any personally-identifiable information.)
Community Note
Tell us about your request What do you want us to build? Disclaimer: this is not the built-in rollback ability of the blue/green deployment. When using the build from code method, save the previous deployment to allow us to rollback to it. This could be a "Roll back" button next to the "Deploy" button in the console. If a deployment is pushed that passes the health check, but has breaking business logic changes, it would be wonderful to rapidly roll back to the prior deployment rather than waiting at least 5 minutes to merge, build, and health check the next image.
Describe alternatives you've considered A clear and concise description of any alternative solutions or features you've considered. The alternative to recover from the scenario provided is to wait at least 5 minutes to build and health check a new image.
Additional context Anything else we should know? Mainly relevant for the build from code deployment method.
Attachments If you think you might have additional information that you'd like to include via an attachment, please do - we'll take a look. (Remember to remove any personally-identifiable information.)