Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this PR change? What problem does it solve?
The code to filter snapshots is currently dispersed throughout the code. When loading a single snapshot, the special id "latest" must be handled manually (except for
ls
which used the code to load multiple snapshots). When loading multiple snapshots, half of the code was located incmd/restic/find.go
and the other half ininternal/restic/snapshot_find.go
which is rather confusing. Some of the snapshot functions also only returned the snapshot ID making it necessary to add code to load the snapshot each time.This PR unifies the snapshot loading into three functions
FindSnapshot
,FindFilteredSnapshot
andFindFilteredSnapshots
as part of the restic package. This unification complements #3912,initSingleSnapshotFilterOptions
is now always used together withFindFilteredSnapshot
andinitMultiSnapshotFilterOptions
withFindFilteredSnapshots
. This ensures consistent behavior across commands.The user visible changes are rather minimal. The help text for
dump
has been fixed. Andls
returns exit code 1 the snapshot cannot be loaded. Besides that some error messages have changed if a snapshot fails to load.Was the change previously discussed in an issue or on the forum?
No.
Checklist
[ ] I have added documentation for relevant changes (in the manual).changelog/unreleased/
that describes the changes for our users (see template).gofmt
on the code in all commits.