You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've been using your role a lot lately for our servers and I appreciate your work. Thank you.
This morning I found out a problem with the latest Borgmatic version which breaks the cron task.
Basically, this role always installs the latest Borgmatic pip package (variable borg_python_packages). However, from Borgmatic version Borgmatic 1.7.0 onwards, Borgmatic parameters such as --create or --prune (which are the parameters called by the cron task) have been deprecated in favor of create or -c for example for creating an archive.
I see two solutions for this quite major issue, since my latest installation of Borg using this role wouldn't work (the cron task failed) because of this change of parameters:
Create a new variable which gives the user of this role the ability to set a specific version of the Borgmatic pip package (such as it is done here
Or, update the various Borgmatic parameters in the different tasks to make them compatible with the latest Borgmatic update.
Personally, as a workaround, I have written a post-task which rollback Borgmatic pip package to 1.6.5 to be compatible with your parameters. However, it can't be a permanent solution.
Thank you!
The text was updated successfully, but these errors were encountered:
Hello,
I've been using your role a lot lately for our servers and I appreciate your work. Thank you.
This morning I found out a problem with the latest Borgmatic version which breaks the cron task.
Basically, this role always installs the latest Borgmatic pip package (variable
borg_python_packages
). However, from Borgmatic version Borgmatic 1.7.0 onwards, Borgmatic parameters such as--create
or--prune
(which are the parameters called by the cron task) have been deprecated in favor ofcreate
or-c
for example for creating an archive.I see two solutions for this quite major issue, since my latest installation of Borg using this role wouldn't work (the cron task failed) because of this change of parameters:
Personally, as a workaround, I have written a post-task which rollback Borgmatic pip package to 1.6.5 to be compatible with your parameters. However, it can't be a permanent solution.
Thank you!
The text was updated successfully, but these errors were encountered: