peter/borgmatic
1
0
Fork 0
mirror of https://github.com/borgmatic-collective/borgmatic.git synced 2026-08-01 22:23:01 +02:00
Code Issues Packages Projects Releases Wiki Activity

Rephrase documentation and link to docs on exit codes feature (#798).

Browse Source
This commit is contained in:
Dan Helfman
2024-01-21 14:47:21 -08:00
parent 5f921a7f80
commit f9998b50e8
2 changed files with 5 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
NEWS
+3 -1
View File
@@ -1,7 +1,9 @@
1.8.7
* #736: Store included configuration files within each backup archive in support of the "config
bootstrap" action. Previously, only top-level configuration files were stored.
* #798: Elevate specific Borg warnings to errors or squash errors to warnings.
* #798: Elevate specific Borg warnings to errors or squash errors to
* warnings. See the documentation for more information:
https://torsion.org/borgmatic/docs/how-to/customize-warnings-and-errors/
* #810: SECURITY: Prevent shell injection attacks within the PostgreSQL hook, the MongoDB hook, the
SQLite hook, the "borgmatic borg" action, and command hook variable/constant interpolation.
* #814: Fix a traceback when providing an invalid "--override" value for a list option.
docs/how-to/customize-warnings-and-errors.md
+2 -2
View File
@@ -82,5 +82,5 @@ a backup file is not found:
terminating with warning status, rc 107
```
The exit status to use in that case would be `107` if you want to configure
borgmatic to treat it as an error.
So if you want to configure borgmatic to treat this as an error instead of a
warning, the exit status to use is `107`.