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

BackupController: do as much as possible #250

Merged
merged 3 commits into from
Jan 3, 2018
Merged

BackupController: do as much as possible #250

merged 3 commits into from
Jan 3, 2018

Commits on Dec 20, 2017

  1. BackupController: do as much as possible 

    When running a backup, try to do as much as possible, collecting errors
along the way, and return an aggregate at the end. This way, if a backup
fails for most reasons, we'll be able to upload the backup log file to
object storage, which wasn't happening before.

Signed-off-by: Andy Goldstein <[email protected]>
    @ncdc
    ncdc committed Dec 20, 2017
    Configuration menu
    Copy the full SHA
    1e581f1 View commit details
    Browse the repository at this point in the history

Commits on Dec 21, 2017

  1. Flatten aggregated errors 

    Signed-off-by: Andy Goldstein <[email protected]>
    @ncdc
    ncdc committed Dec 21, 2017
    Configuration menu
    Copy the full SHA
    0fc087c View commit details
    Browse the repository at this point in the history

Commits on Jan 3, 2018

  1. Log backup item action error when it occurs 

    If a backup item action errors, log the error as soon as it occurs, so
it's clear when the error happened. Also include information about the
groupResource, namespace, and name of the item in the error.

Signed-off-by: Andy Goldstein <[email protected]>
    @ncdc
    ncdc committed Jan 3, 2018
    Configuration menu
    Copy the full SHA
    1b124a3 View commit details
    Browse the repository at this point in the history