paulfantom/ansible-restic

Deploy restic backup program

ansible-restic's Issues

"Deploy cron script" task treats “dest” as a directory instead of as a file and fails

I suspect this will be a "works for me", but maybe you can help me out. I have posted a question to stack overflow

What ansible-restic should do here is to deploy a cron script based on a template, with name restic-backups-test, inside directory /etc/cron.d/ . However, it looks like ansible interprets that the directory should be /etc/cron.d/restic-backups-test and the file name just the epoch timestamp like 1551799877
I'm afraid it has to do with my environment instead, but I don't know what could make ansible change this behaviour, and my playbook doesn't do black magic.

Restic installation directory chmod

Hi, thanks for this project.

The binary gets installed to /usr/local/bin, but the task named "Ensure restic installation directory exist" overwrites the folder's permissions, effectively disabling access to other binaries in that folder for regular users.

I checked Ansible's file module but it states that the directory is created only if it doesn't exist. I've found no option to let existing permissions stay intact.

Repository initialization missing environment variables

In configure.yml/Initialize restic repositories the environment variables needed to authenticate with, e.g., backblaze aren't set, so it fails with an error like "Fatal: create repository at b2:wttw-whatever:/wherever failed: Fatal: unable to open B2 backend: Account ID ($B2_ACCOUNT_ID) is empty".

I'm guessing it needs the remote_credentials passed in, much as they are in restic.cron.j2.

I've worked around it here, but I'm not quite fluent enough in ansible to do it the right way.

Request to publish a new tag for PR#61

Hi @paulfantom - We're wanting to take on the improvement in #61 (check if a repo needs initialization) but this hasn't been released in a tag. We'd very much appreciate it, if you would please make new tag/release so we can refer to that in our deployments?

replace custom wrapper scripts with runrestic

This role shouldn't reinvent the wheel and implement custom scripts for various restic functionalities. There are already many projects providing a simple to use wrapper on restic and those could be used instead.

We could use runrestic which is written in python3 and available via pip3 install runrestic. Personally I like this one as it has clear configuration and includes instrumentation to push metrics to prometheus monitoring system.

This is only an idea, but implementing this should greatly simplify second day operations and reduce role maintenance.

ansible-restic fails in check-mode (when /tmp/restic-0.9.6-SHA256SUMS is missing)

Just stumbled over this: if /tmp/restic-0.9.6-SHA256SUMS is missing, check-mode fails:

% ansible-playbook -D -C site-backup01.yml
[...]
  TASK [paulfantom.restic : Get checksum list from github]
  changed: [backup01.example.com]

  TASK [paulfantom.restic : Set checksum variable]
  fatal: [backup01.example.com]: FAILED! => {"ansible_facts": {"discovered_interpreter_python": "/usr/bin/python"}, "changed": false, "msg": "file not found: /tmp/restic-0.9.6-SHA256SUMS"}
[...]

It would be nice if the role does not cause a change if a temporary file is missing and it certainly should not fail. Thank you.