Use ResticRepository's resticIdentifier field as the source of truth for repo IDs #557
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.
Builds on #532 , only the last commit is new.
This PR:
RepoPrefix
field onPodVolumeBackup
andPodVolumeRestore
with aRepoIdentifier
field, which contains the full restic repo identifier (populated by the Ark server by pulling from the relevantResticRepository
CR)repoPrefix
field from thepkg/restic/repositoryManager
and instead sources repos' identifiers from theResticRepository
CRs (paving the way for supporting heterogeneous restic backends - no need for them all to be the same, or to be AWS/Azure/GCP anymore)PodVolumeRestore
, similarly to for backups