- #450: Add an InfluxDB database hook for dumping and restoring InfluxDB 1 and 2 databases. See the
documentation for more information:
https://torsion.org/borgmatic/reference/configuration/data-sources/influxdb/ - #1332: For the MongoDB hook, add a "password_transport" option for customizing how borgmatic
transmits passwords to the database client. See the documentation for more information:
https://torsion.org/borgmatic/reference/configuration/data-sources/mongodb/ - #1345: Add a 1Password credential hook for loading credentials from the 1Password CLI. See the
documentation for more information:
https://torsion.org/borgmatic/reference/configuration/credentials/onepassword/ - #1346: Add an OpenLDAP database hook for dumping and restoring OpenLDAP databases with slapcat
and slapadd. See the documentation for more information:
https://torsion.org/borgmatic/reference/configuration/data-sources/openldap/ - #1348: Add support for "rest://" repository URLs introduced in Borg 2.0.0b22.
- #1348: BREAKING: For the "prune" action, remove Borg 2's "--oldest", "--newest", "--older", and
"--newer" flags, as Borg 2.0.0b22 has removed them. - #1348: For the "prune" action, add support for Borg 2's "--from" flag.
- #1349: Fix for Borg 2.0.0b23 dropping support for the "--remote-path" flag in favor of an
environment variable. - #1349: Document the "upload_rate_limit" and "upload_buffer_size" option as Borg 1.x only.
- #1340: For the
--repairflag on thecheckaction, don't attempt to runborg infofirst,
as it can fail on a corrupted repository—like the kind you might by trying to repair. Also ignore
any check frequency/days configuration and skip recording check timestamps. - #1352: Fix a hang in which PostgreSQL child processes prevented borgmatic from exiting when Borg
errored out. - #1353: Fix for soft failures in command hooks incorrectly being treated as hard failures,
resulting in monitoring ping fails. - For the "user_runtime_directory" option and the "XDG_RUNTIME_DIR" environment variable, create a
temporary directory for borgmatic within the given runtime directory. This makes cleanup easier
and prevents unintentional runtime file reuse across borgmatic runs.