Add an ability to roll back service deployment such that one can if needed deploy the previous version of the service (say for a specific git hash or built image) on demand.
This will be necessary when the latest version introduced some bugs, and you want to roll back the service so as to work on it. The current system only allows for building container for the latest code changes.
Describe the solution you'd like
Ability to roll back to a previous deployment or build for specific git hash.
Something like this:
Describe alternatives you've considered
docker service rollback
Additional context
Here is an example of how an alternative; coolify handles this
And here is an example of how the alternative Caprover handles this
What problem will this feature address?
Add an ability to roll back service deployment such that one can if needed deploy the previous version of the service (say for a specific git hash or built image) on demand.
This will be necessary when the latest version introduced some bugs, and you want to roll back the service so as to work on it. The current system only allows for building container for the latest code changes.
Describe the solution you'd like
Ability to roll back to a previous deployment or build for specific git hash.
Something like this:
Describe alternatives you've considered
docker service rollback
Additional context
Here is an example of how an alternative; coolify handles this
And here is an example of how the alternative Caprover handles this