You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be nice for POST_BACKUP_SCRIPT to be able to detect when a backup failed, so that it can send out a notification in case of an error (e.g., an unhandled restic state). This was one of the use cases for the feature originally described in #89, but I don't see any way for a post-backup script to currently tell if something went awry.
I think all this would take is passing the exit code (and possibly some stderr output?) from the backup stage as an argument to the script on this line:
It was something I meant to address, but never got around to doing so. Passing the exit code would likely suffice, though I think the set -e at the start of backup-loop.sh might have to be removed? Or at least disabled for the line that runs the backup. Since iirc that makes bash bail on the first command that dies.
It would be nice for
POST_BACKUP_SCRIPT
to be able to detect when a backup failed, so that it can send out a notification in case of an error (e.g., an unhandled restic state). This was one of the use cases for the feature originally described in #89, but I don't see any way for a post-backup script to currently tell if something went awry.I think all this would take is passing the exit code (and possibly some stderr output?) from the backup stage as an argument to the script on this line:
docker-mc-backup/backup-loop.sh
Line 499 in 037f49d
The text was updated successfully, but these errors were encountered: