Store included configuration files within a backup archive #736
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#736
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?
What I'd like to do and why
As of #697, top-level borgmatic configuration files get stored within a backup archive when the
create
action is run. This supports subsequentconfig bootstrap
action invocations, so you can restore your borgmatic configuration on a fresh system. However, if a configuration file includes other configuration files, those configuration files don't get stored, effectively breakingbootstrap
on such systems.So as part of this ticket, consider automatically detecting includes and including those filenames in the set of configuration files to include in an archive.
Other notes / implementation ideas
Note that this will have to be done carefully since relative includes are supported, and there's existing logic to probe for these includes in multiple locations.
Implemented in main and will be part of the next release!
Released in borgmatic 1.8.7!