Allow warnings to not result in a "failed" backup #204
Labels
No Label
bug
data loss
design finalized
good first issue
new feature area
question / support
security
waiting for response
No Milestone
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: borgmatic-collective/borgmatic#204
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
What I'm trying to do and why
Borg considers exit code 1 as a warning and not a failure (https://borgbackup.readthedocs.io/en/stable/usage/general.html#return-codes). I would like Borgmatic to honor that by having an option to not end in error if Borg ended in rc 1.
I'll do ya one better. I'll just make that the default behavior. Thanks for the suggestion!
Okay, implemented and released in borgmatic 1.3.14 as default behavior. Please let me know if you have any issues with it.
Such service! Thank you!
Anything for you, @spacerodent!