ansible-role-borgbackup/tasks/client_create_scripts_each.yml, branch v1.0.5 Ansible role for deploying scheduled borgbackup configurations Handle special characters around BORG_PASSPHRASE variable 2026-01-23T15:24:02+00:00 Magnus Kühne 73171182+magkue@users.noreply.github.com 2026-01-23T15:24:02+00:00 f6294fe0b2bb4ec2be2587434da60dc187ee59b4 If passphrase contains special characters like (!, $, &, ^, *, @), this needs to be escaped. Co-authored-by: Colin Wilk <colin@wilk.cx> 
If passphrase contains special characters like (!, $, &, ^, *, @), this needs to be escaped.

Co-authored-by: Colin Wilk <colin@wilk.cx>
 Migrate role from cron to systemd 2023-11-04T13:02:38+00:00 Colin Wilk colin.wilk@tum.de 2023-11-03T18:45:20+00:00 50a2795c3a6c72203262400db5029f5afdf1d49c Systemd gives us the ability to monitor backup job status using existing monitoring solutions (node exporter) and allows us greater control over the scheduling of the backup jobs. This introduces a breaking change that requires users to manually remove the old repositories from the clients and redeploying them with the role. You will have to remove the Cron job that was created by the Ansible script, everything else will be overwritten with a run from the newer version. - name: Remove backup cron jobs ansible.builtin.cron: name: BORG (Application level backups) state: absent become: true - name: Remove env for backup cron job ansible.builtin.cron: name: BORG_PASSPHRASE env: true state: absent become: true Performing manual migrations on the Borg server is not required. We now additionally support multiple Borg repositories per client host using the `borg_backup_argument` variable. Signed-off-by: Colin Wilk <colin.wilk@tum.de> 
Systemd gives us the ability to monitor backup job status using existing
monitoring solutions (node exporter) and allows us greater control over
the scheduling of the backup jobs.

This introduces a breaking change that requires users to manually remove
the old repositories from the clients and redeploying them with the
role. You will have to remove the Cron job that was created by the
Ansible script, everything else will be overwritten with a run from the
newer version.

- name: Remove backup cron jobs
  ansible.builtin.cron:
    name: BORG (Application level backups)
    state: absent
  become: true
- name: Remove env for backup cron job
  ansible.builtin.cron:
    name: BORG_PASSPHRASE
    env: true
    state: absent
  become: true

Performing manual migrations on the Borg server is not required.

We now additionally support multiple Borg repositories per client host
using the `borg_backup_argument` variable.

Signed-off-by: Colin Wilk <colin.wilk@tum.de>