Skip to content

Releases: maxhoesel-ansible/ansible-collection-borgbackup

v2.0.1

30 Aug 15:47
6b7bb1b
Compare
Choose a tag to compare

Changes

Bug Fixes and Patches

v2.0.0

20 Jul 15:35
e7bf9a5
Compare
Choose a tag to compare

Changes

Major Changes

Features and Minor Changes

v1.0.2

06 Jun 17:56
be3a263
Compare
Choose a tag to compare

Changes

Bug Fixes and Patches

v1.0.0

31 Mar 18:54
90ab1ba
Compare
Choose a tag to compare

This is a backwards-incompatible release that clears up the codebase a lot in preparation for future borg/borgmatic releases.

Breaking Changes and Major Features

borgmatic role: Full Compatibility with Borgmatic 1.8+

With borgmatic 1.8, the configuration format changed from a couple of top-level keys with subsections (such as location) to a flat hierarchy.
Previously, the borgmatic role relied on these keys for finding all configuration variables passed into it by the user, such as borgmatic_location_xxx or borgmatic_storage_xxx.
These variables were then assembled into a configuration file inside the role.

With this release, borgmatic configuration is now handled through a simple variable: borgmatic_config. This variable will be directly templated out as the borgmatic configuration, meaning that future changes in borgmatics configuration format will not affect this roles core functionality.

Example:

# instead of this...
borgmatic_location_source_directories:
  - /home
  - /etc
  - /var
borgmatic_location_repositories:
  - [email protected]:{fqdn}
borgmatic_storage_encryption_passphrase: "mysupersecretpassphrase"
borgmatic_retention_keep_daily: 5

# ... just do this (for borgmatic >=1.8)
borgmatic_config:
  source_directories:
    - /home
    - /etc
    - /var
  repositories:
    - path: ssh://[email protected]/./my_repository_name
      label: backupserver
  encryption_passphrase: "mysupersecretpassphrase"
  keep_daily: 7

# ... or this (for borgmatic <1.8):
borgmatic_config:
  location:
    source_directories:
      - /home
      - /etc
      - /var
    repositories:
      - path: ssh://[email protected]/./my_repository_name
        label: backupserver
  storage:
    encryption_passphrase: "mysupersecretpassphrase"
  retention:
    keep_daily: 7

This change also allows users to easily reuse an existing borgmatic config by passing it as borgmatic_config, instead of having to manually set a bunch of variables.

roles: Add Debian 12, Remove Ubuntu 18

Ubuntu 18 LTS is no longer supported upstream outside of commercial settings and will not be tested with this collection going forward.
Meanwhile, Debian 12 has been added to the officially supported distributions.

borgmatic: Remove the scheduled check job

This role previously included the option to set up a separate check job for borgmatic. Borgmatic versions 1.6 and up already offer a similar feature in their configuration, so this separate job was rarely needed. More importantly, there was no safeguard against both jobs running against the same time, leading to one job failing due to a missing lock.
Since this mechanism was rather unsound, the feature has been removed and users are advised to use borgmatics builtin check frequency setting.

Changelog

Major Changes

Bug Fixes and Patches

  • fix borgmatic failing when borgmatic_ssh_manage_known_hosts is false @maxhoesel (#154)

v0.1.15

17 Mar 11:03
d38c1b7
Compare
Choose a tag to compare

Changes

Bug Fixes

v0.1.14

29 Dec 16:11
97b3678
Compare
Choose a tag to compare

Changes

  • Fix collection installs after the most recent release, whoops!

v0.1.13

29 Dec 16:06
655e347
Compare
Choose a tag to compare

Changes

  • Removed unneeded files from the collection tarball (including requirements.txt, which is only used for development). This shouldn't have any meaningful changes for end-users, aside from a slightly reduced collection file size

v0.1.12

23 Dec 19:20
ef99606
Compare
Choose a tag to compare

Changes

v0.1.11

23 Dec 19:01
5961f5c
Compare
Choose a tag to compare

Changes

Bug Fixes

0.1.10

13 Mar 17:17
Compare
Choose a tag to compare
v0.1.10

Release 0.1.10