-
Notifications
You must be signed in to change notification settings - Fork 32
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Retention: Align host filter with "backup" #227
Conversation
Yes this is a good idea 👍🏻 I was also thinking we should fix the inconsistency of Sorry I'm very busy this week, and the next one as well. We're deploying a new project to production next week 😉 |
Codecov ReportPatch coverage:
Additional details and impacted files@@ Coverage Diff @@
## master #227 +/- ##
==========================================
+ Coverage 77.39% 77.48% +0.09%
==========================================
Files 93 93
Lines 10034 10074 +40
==========================================
+ Hits 7765 7805 +40
Misses 2004 2004
Partials 265 265
Flags with carried forward coverage won't be shown. Click here to find out more.
☔ View full report in Codecov by Sentry. |
Also auto-enable "after-backup" if nothing was specified
db462a3
to
5086f67
Compare
5086f67
to
3e0d095
Compare
@creativeprojects , think the PR is ready for review now. What do you think? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM 😄
BTW we should keep track of all the subtle differences between v1 and v2 so we can make a exhaustive upgrade documentation
Thanks 😉
Guess we’ll need to review usages of |
Aligns the
--host
filter of "retention" (forget) with "backup" in restic (if host is not set, it defaults toos.Hostname()
in restic, but forget has no default matching all hosts if unset)After this change, when using
retention
in version 2 configs, all 3 filterspath
,tags
andhost
are aligned with thebackup
section if not redefined.Other changes:
after-backup: true
if nothing was specified explicitly butkeep-*
is set(to avoid case like `backup` followed by `forget --prune` in a schedule #226).
tag
copy frombackup
. Tags must be copied as single flag ("tag1,tag2,tag3,..."
) instead of multiple flags to match correctly(mentioned in Configuring a retention on a stdin profile applies the retention policy to the whole repository #225)
@creativeprojects : before I create tests, what do you think on this?