Add support for configuration syntax of borgmatic > 1.8.0#187
Add support for configuration syntax of borgmatic > 1.8.0#187m3nu merged 4 commits intoborgbase:masterfrom
Conversation
|
We tried this and seems to work perfectly without any changes to our configuration. It also gives us the ability to use loki for monitoring, which we were planning to do. Finally, this looks like a good approach to also support borgmatic >2.0 templates. |
|
In our team, we had to develop our own custom config to support latest borgmatic versions. This is definitely a nice contribution and quite frankly, a much needed one. |
|
@m3nu is there any chance you have some time to check this out? We could also contribute a template with the changes for boegmatic >2. |
|
@m3nu happy new year! Could we get this PR merged? |
- Rename templates to version-based naming (config_1.7.yaml.j2) - Use command module instead of shell for version detection - Add check_mode: false for version detection task - Fix deprecated remote_rate_limit → upload_rate_limit for 1.8+ 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
- Incorporate retries and retry_wait options from master - Adapt new options to both legacy (1.7) and new (1.8+) config formats 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
|
Thanks for this contribution! I had this planned, but the person working on it couldn't finish it. So this is very welcome. I just made a small change to avoid the shell task and found one wrong option name. |
4 participants
Hello,
my take at updating the configuration syntax to the newer borgmatic versions. I went with separating the two config templates, I think it is less messy this way, and should be easier to remove the legacy one once the old version is no longer supported. Also, makes easier to add new options, unsupported by the old version. Downside is the added maintenance burden with keeping the two templates in sync. I think it is worth it.
Should resolve #145.