Borgmatic

Latest version: v1.8.10

Safety actively analyzes 621751 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 1 of 28

1.8.10

* 656 (beta): Add a "spot" consistency check that compares file counts and contents between your
source files and the latest archive, ensuring they fall within configured tolerances. This can
catch problems like incorrect excludes, inadvertent deletes, files changed by malware, etc. See
the documentation for more information:
https://torsion.org/borgmatic/docs/how-to/deal-with-very-large-backups/#spot-check
* 779: When "--match-archives *" is used with "check" action, don't skip Borg's orphaned objects
check.
* 842: When a command hook exits with a soft failure, ping the log and finish states for any
configured monitoring hooks.
* 843: Add documentation link to Loki dashboard for borgmatic:
https://torsion.org/borgmatic/docs/how-to/monitor-your-backups/#loki-hook
* 847: Fix "--json" error when Borg includes non-JSON warnings in JSON output.
* 848: SECURITY: Mask the password when logging a MongoDB dump or restore command.
* Fix handling of the NO_COLOR environment variable to ignore an empty value.
* Add documentation about backing up containerized databases by configuring borgmatic to exec into
a container to run a dump command:
https://torsion.org/borgmatic/docs/how-to/backup-your-databases/#containers

1.8.9

* 311: Add custom dump/restore command options for MySQL and MariaDB.
* 811: Add an "access_token" option to the ntfy monitoring hook for authenticating
without username/password.
* 827: When the "--json" flag is given, suppress console escape codes so as not to
interfere with JSON output.
* 829: Fix "--override" values containing deprecated section headers not actually overriding
configuration options under deprecated section headers.
* 835: Add support for the NO_COLOR environment variable. See the documentation for more
information:
https://torsion.org/borgmatic/docs/how-to/set-up-backups/#colored-output
* 839: Add log sending for the Apprise logging hook, enabled by default. See the documentation for
more information:
https://torsion.org/borgmatic/docs/how-to/monitor-your-backups/#apprise-hook
* 839: Document a potentially breaking shell quoting edge case within error hooks:
https://torsion.org/borgmatic/docs/how-to/monitor-your-backups/#error-hooks
* 840: When running the "rcreate" action and the repository already exists but with a different
encryption mode than requested, error.
* Switch from Drone to Gitea Actions for continuous integration.
* Rename scripts/run-end-to-end-dev-tests to scripts/run-end-to-end-tests and use it in both dev
and CI for better dev-CI parity.
* Clarify documentation about restoring a database: borgmatic does not create the database upon
restore.

1.8.8

* 370: For the PostgreSQL hook, pass the "PGSSLMODE" environment variable through to Borg when the
database's configuration omits the "ssl_mode" option.
* 818: Allow the "--repository" flag to match across multiple configuration files.
* 820: Fix broken repository detection in the "rcreate" action with Borg 1.4. The issue did not
occur with other versions of Borg.
* 822: Fix broken escaping logic in the PostgreSQL hook's "pg_dump_command" option.
* SECURITY: Prevent additional shell injection attacks within the PostgreSQL hook.

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. 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.

1.8.6

Not secure
* 767: Add an "--ssh-command" flag to the "config bootstrap" action for setting a custom SSH
command, as no configuration is available (including the "ssh_command" option) until
bootstrapping completes.
* 794: Fix a traceback when the "repositories" option contains both strings and key/value pairs.
* 800: Add configured repository labels to the JSON output for all actions.
* 802: The "check --force" flag now runs checks even if "check" is in "skip_actions".
* 804: Validate the configured action names in the "skip_actions" option.
* 807: Stream SQLite databases directly to Borg instead of dumping to an intermediate file.
* When logging commands that borgmatic executes, log the environment variables that
borgmatic sets for those commands. (But don't log their values, since they often contain
passwords.)

1.8.5

Not secure
* 701: Add a "skip_actions" option to skip running particular actions, handy for append-only or
checkless configurations. See the documentation for more information:
https://torsion.org/borgmatic/docs/how-to/set-up-backups/#skipping-actions
* 701: Deprecate the "disabled" value for the "checks" option in favor of the new "skip_actions"
option.
* 745: Constants now apply to included configuration, not just the file doing the includes. As a
side effect of this change, constants no longer apply to option names and only substitute into
configuration values.
* 779: Add a "--match-archives" flag to the "check" action for selecting the archives to check,
overriding the existing "archive_name_format" and "match_archives" options in configuration.
* 779: Only parse "--override" values as complex data types when they're for options of those
types.
* 782: Fix environment variable interpolation within configured repository paths.
* 782: Add configuration constant overriding via the existing "--override" flag.
* 783: Upgrade ruamel.yaml dependency to support version 0.18.x.
* 784: Drop support for Python 3.7, which has been end-of-lifed.

Page 1 of 28

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.