Ability to only install Borg and Borgmatic, disable config creation

[snapshotleisure]

Hi,

I was wondering if its possible to modify the role so it only installs Borg and Borgmatic. I would like to handle the config with a different ansible playbook.

The reason being I have a ansible flow like below:

• When I first setup a server I will run the ansible-role-borgbackup role to install borg and borgmatic
• Afterwards I have a playbook which installs docker apps (For each docker app I would create a seperate config file and stick it in /etc/borgmatic.d/)
• When its time to backup, I will let borgmatic handle the sequence of the config files and backup sequentially.

I have currently modified the role to remove the config generation and also update the cron/systemd timers to use borgmatic, rather than borgmatic -c .

The proper solution would be to add a flag like BORG_CREATE_CONFIG true/false to turn on or off this feature

I am happy to try and contribute this change, but would like to discuss first if this is desired.

[kisamoto]

For what it's worth I have a similar use case, I want to place multiple files in /etc/borgmatic.d/ to be picked up rather than using /etc/borgmatic/config.yaml.

Also, in situations where I have only a single config file I want to include other options such as sqlite_databases which I currently do by just overwriting and reloading the systemd service in tasks after the role completes. Not ideal though as a failure means I end up with an incorrect config.yaml rather than none at all.