Configuration file includes and merging #148
Labels
No Label
bug
data loss
design finalized
good first issue
new feature area
question / support
security
waiting for response
No Milestone
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: borgmatic-collective/borgmatic#148
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
As discussed in #73 and #3 and elsewhere, borgmatic configuration could benefit from better support for re-use of common config options across repositories. A common use case is: I have multiple different repositories and/or applications to backup, and they have some, but not all, config options in common (retention, consistency, etc). Therefore, it would be really handy to pull in and re-use common configuration.
The proposed mechanism for this is an include / inlining mechanism within borgmatic configuration files. The way that might look is:
Or, even fancier.. Includes with merging / local overrides! (Note that this is a shallow merge.)
This is a fairly advanced feature, and so not everyone would use it. But the idea is that it'd be there for users that need it.
Implemented and released in borgmatic 1.3.0! And documented here: https://torsion.org/borgmatic/docs/how-to/make-per-application-backups/