check config file name #77
Labels
No Label
bug
data loss
design finalized
good first issue
new feature area
question / support
security
waiting for response
No Milestone
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: borgmatic-collective/borgmatic#77
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?
Using borgmatic, I notice that every file in /etc/borgmatic.d/ are read, even those ending with a tilda "~" that are usually a backup copy made by emacs or this kind of text editor.
In my case, I set up a backup using /etc/borgmatic.d/mybackup.yaml
then adjust some parameters and a few days after, I realize that borgmatic run my config twice, the old version (ending with "~") and the current version.
I think that borgmatic should only consider a subset of config file like the debian "run-parts" does. Or at least ignore file ending with a tilda "~"
Might make sense to look at only
*.yaml
-named files, as that'll protect against ignoring files like*~
,*.swp
, etc.Just fixed this in master. This fix will go out in the next release. Thanks for reporting it!
Great !
Looking for .yaml file is simple and robust,
but I was not sure if there is some habit to use other files extension like
.conf, .ini or so.
Thanks to have consider this PR and for writing tests along :)
Released in borgmatic 1.2.1!