donat-b / ansible-restic Goto Github PK

This role lack repository initialization, which is kind of crucial in new production systems.

Right now this role is tied to AWS S3 backend since it only allows to use AWS_* environment variables.

Would be nice to be able to use at least another backend, like B2 for instance:

https://restic.readthedocs.io/en/latest/030_preparing_a_new_repo.html#backblaze-b2

The only place that I see that we use those authentication environment variables is in the cron job. Probably we could infere the backend in some way form the repository name/URL?

I did a major rework of this role in my fork. Changes include:

• major change in passing restic configuration for cron jobs and restic repositories
• downgraded molecule to 1.25
• added TravisCI and molecule tests
• automatic import to ansible galaxy
• added support for older ansible version (>2.2)
• added automatic tagging with semver
• MIT license since main repo didn't have license file
• removed other installation method than downloading from github
• added support for systems other than linux and for other system architectures
• removed operating systems from supported list when they are not tested by molecule
• added centos 7 support
• upgraded restic to 0.8.1
• all variables which can be changed by user are defined in defaults/main.yml
• some changes in README file
• simplified cron template and made it more generic
• added CONTIRBUTE instructions

If you want we could merge it somehow, or not 😄

Please add a LICENSE file. Saying "BSD" in readme doesn't help since there are two BSD licenses (2-clause) and (3-clause).
github has a good and simple guide of adding license file: https://help.github.com/articles/adding-a-license-to-a-repository/

Using RESTIC_PASSWORD instead of RESTIC_PASSWORD_FILE in cronfile in /etc/cron.d can simplify this role. This way there is no need to create /var/lib/restic directory and password files. Providing that cronfile has limited file permissions, which it should since it already holds some sensitive data.

We should leverage checksums provided with the release binaries to make sure we received valid data.

@donat-b I can start adding CI pipeline based on travis ci to run molecule tests before accepting PRs. However I need some answers first:

1. Do you want CI?
2. Is testing in docker ok for you?
3. What is your approach to versioning? Do you want to automatically apply new version after successful merge? And what do you think about semver?

This would also need you to link your github account with travis (travis ci account creation) and configuring repository in travis (I can help with some screenshots).

Also since you are using molecule 2.x it will probably take me some time to set up proper CI pipeline with docker containers.

Hello there!

What is the current status of this ansible role?

The last commit was just a few days ago. And also the restic version used is not quite the same as the current Release.

How does it look like? Is it still maintained here?