Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Add support for rolling back on a failed update #64

Merged
merged 2 commits into from
Jan 12, 2022
Merged

Add support for rolling back on a failed update #64

merged 2 commits into from
Jan 12, 2022

Commits on Jan 4, 2022

  1. Detect if a service update fails 

    `docker service update` will exit with `1` and write something like
`service update paused: update paused due to failure or early termination of task ...`
to stderr if the updated service fails to start or remains unhealthy.

With this change this event appears in the logs explicitly.
    @andrasmaroy
    andrasmaroy committed Jan 4, 2022
    Configuration menu
    Copy the full SHA
    a449627 View commit details
    Browse the repository at this point in the history

  2. Add support for rolling back on a failed update 

    By setting the `ROLLBACK_ON_FAILURE` variable if an update fails
Shepherd will roll it back to the previous version, thus avoiding a
service failure as a result of the update.
If the Apprise Sidecar is set it will also send a notification about
this.
    @andrasmaroy
    andrasmaroy committed Jan 4, 2022
    Configuration menu
    Copy the full SHA
    1ce11a9 View commit details
    Browse the repository at this point in the history