From 45a9e3bfc39845c30723fda7375e318b06c78059 Mon Sep 17 00:00:00 2001 From: Dan Helfman Date: Thu, 20 Jun 2024 14:25:20 -0700 Subject: [PATCH] Document that "borgmatic borg create" bypasses monitoring hooks (#882). --- docs/how-to/run-arbitrary-borg-commands.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/docs/how-to/run-arbitrary-borg-commands.md b/docs/how-to/run-arbitrary-borg-commands.md index 8962b90..9ff51e3 100644 --- a/docs/how-to/run-arbitrary-borg-commands.md +++ b/docs/how-to/run-arbitrary-borg-commands.md @@ -133,6 +133,8 @@ borgmatic's `borg` action is not without limitations: borgmatic action. In this case, only the Borg command is run. * Unlike normal borgmatic actions that support JSON, the `borg` action will not disable certain borgmatic logs to avoid interfering with JSON output. + * The `borg` action bypasses most of borgmatic's machinery, so for instance + monitoring hooks will not get triggered when running `borgmatic borg create`. * Prior to version 1.8.0 borgmatic implicitly injected the repository/archive arguments on the Borg command-line for you (based on your borgmatic configuration or the