Bump borgmatic from 1.6.6 to 1.7.9 in /base

[dependabot]

Bumps borgmatic from 1.6.6 to 1.7.9.

Release notes

Sourced from borgmatic's releases.

borgmatic 1.7.9

• #295: Add a SQLite database dump/restore hook.
• #304: Change the default action order when no actions are specified on the command-line to: "create", "prune", "compact", "check". If you'd like to retain the old ordering ("prune" and "compact" first), then specify actions explicitly on the command-line.
• #304: Run any command-line actions in the order specified instead of using a fixed ordering.
• #564: Add "--repository" flag to all actions where it makes sense, so you can run borgmatic on a single configured repository instead of all of them.
• #628: Add a Healthchecks "log" state to send borgmatic logs to Healthchecks without signalling success or failure.
• #647: Add "--strip-components all" feature on the "extract" action to remove leading path components of files you extract. Must be used with the "--path" flag.
• Add support for Python 3.11.

borgmatic 1.7.8

• #620: With the "create" action and the "--list" ("--files") flag, only show excluded files at verbosity 2.
• #621: Add optional authentication to the ntfy monitoring hook.
• With the "create" action, only one of "--list" ("--files") and "--progress" flags can be used. This lines up with the new behavior in Borg 2.0.0b5.
• Internally support new Borg 2.0.0b5 "--filter" status characters / item flags for the "create" action.
• Fix the "create" action with the "--dry-run" flag querying for databases when a PostgreSQL/MySQL "all" database is configured. Now, these queries are skipped due to the dry run.
• Add "--repository" flag to the "rcreate" action to optionally select one configured repository to create.
• Add "--progress" flag to the "transfer" action, new in Borg 2.0.0b5.
• Add "checkpoint_volume" configuration option to creates checkpoints every specified number of bytes during a long-running backup, new in Borg 2.0.0b5.

borgmatic 1.7.7

• #642: Add MySQL database hook "add_drop_database" configuration option to control whether dumped MySQL databases get dropped right before restore.
• #643: Fix for potential data loss (data not getting backed up) when dumping large "directory" format PostgreSQL/MongoDB databases. Prior to the fix, these dumps would not finish writing to disk before Borg consumed them. Now, the dumping process completes before Borg starts. This only applies to "directory" format databases; other formats still stream to Borg without using temporary disk space.
• Fix MongoDB "directory" format to work with mongodump/mongorestore without error. Prior to this fix, only the "archive" format worked.

borgmatic 1.7.6

• #393, #438, #560: Optionally dump "all" PostgreSQL/MySQL databases to separate files instead of one combined dump file, allowing more convenient restores of individual databases. You can enable this by specifying the database dump "format" option when the database is named "all".
• #602: Fix logs that interfere with JSON output by making warnings go to stderr instead of stdout.
• #622: Fix traceback when include merging configuration files on ARM64.
• #629: Skip warning about excluded special files when no special files have been excluded.
• #630: Add configuration options for database command customization: "list_options", "restore_options", and "analyze_options" for PostgreSQL, "restore_options" for MySQL, and

... (truncated)

Changelog

Sourced from borgmatic's changelog.

1.7.9

• #295: Add a SQLite database dump/restore hook.
• #304: Change the default action order when no actions are specified on the command-line to: "create", "prune", "compact", "check". If you'd like to retain the old ordering ("prune" and "compact" first), then specify actions explicitly on the command-line.
• #304: Run any command-line actions in the order specified instead of using a fixed ordering.
• #564: Add "--repository" flag to all actions where it makes sense, so you can run borgmatic on a single configured repository instead of all of them.
• #628: Add a Healthchecks "log" state to send borgmatic logs to Healthchecks without signalling success or failure.
• #647: Add "--strip-components all" feature on the "extract" action to remove leading path components of files you extract. Must be used with the "--path" flag.
• Add support for Python 3.11.

1.7.8

• #620: With the "create" action and the "--list" ("--files") flag, only show excluded files at verbosity 2.
• #621: Add optional authentication to the ntfy monitoring hook.
• With the "create" action, only one of "--list" ("--files") and "--progress" flags can be used. This lines up with the new behavior in Borg 2.0.0b5.
• Internally support new Borg 2.0.0b5 "--filter" status characters / item flags for the "create" action.
• Fix the "create" action with the "--dry-run" flag querying for databases when a PostgreSQL/MySQL "all" database is configured. Now, these queries are skipped due to the dry run.
• Add "--repository" flag to the "rcreate" action to optionally select one configured repository to create.
• Add "--progress" flag to the "transfer" action, new in Borg 2.0.0b5.
• Add "checkpoint_volume" configuration option to creates checkpoints every specified number of bytes during a long-running backup, new in Borg 2.0.0b5.

1.7.7

• #642: Add MySQL database hook "add_drop_database" configuration option to control whether dumped MySQL databases get dropped right before restore.
• #643: Fix for potential data loss (data not getting backed up) when dumping large "directory" format PostgreSQL/MongoDB databases. Prior to the fix, these dumps would not finish writing to disk before Borg consumed them. Now, the dumping process completes before Borg starts. This only applies to "directory" format databases; other formats still stream to Borg without using temporary disk space.
• Fix MongoDB "directory" format to work with mongodump/mongorestore without error. Prior to this fix, only the "archive" format worked.

1.7.6

• #393, #438, #560: Optionally dump "all" PostgreSQL/MySQL databases to separate files instead of one combined dump file, allowing more convenient restores of individual databases. You can enable this by specifying the database dump "format" option when the database is named "all".
• #602: Fix logs that interfere with JSON output by making warnings go to stderr instead of stdout.
• #622: Fix traceback when include merging configuration files on ARM64.
• #629: Skip warning about excluded special files when no special files have been excluded.
• #630: Add configuration options for database command customization: "list_options", "restore_options", and "analyze_options" for PostgreSQL, "restore_options" for MySQL, and

... (truncated)

Commits

• bdfe4b6 Bump version for release.
• ca44618 Add support for Python 3.11.
• 7605838 Add "--repository" flag to all actions where it makes sense (#564).
• 7a784b8 Add "--repository" flag to common actions (where it makes sense) (#652).
• 3e22414 Update tests
• 5f87ea3 Add "--repository" flag to the "create" action
• a8aeace Add "--repository" flag to the "compact" action
• 480addd Add "--repository" flag to the "check" action
• ce0ce4c Merge mostly repetetive tests
• 7de9260 Remove test now that --repository isn't expected to error
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)