Closed tesshuflower closed 1 month ago
Issues
0 New issues
0 Accepted issues
Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code
All modified and coverable lines are covered by tests :white_check_mark:
Project coverage is 67.4%. Comparing base (
b46916a
) to head (ed1c9c6
). Report is 9 commits behind head on main.
/cc @JohnStrunk
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: JohnStrunk, tesshuflower
The full list of commands accepted by this bot can be found here.
The pull request process is described here
/retest
Describe what this PR does
Updates the ensure_initialized function in the restic mover script.
I came across this info in the restic docs: https://restic.readthedocs.io/en/stable/075_scripting.html#check-if-a-repository-is-already-initialized
Essentially it recommends using
restic cat config
in order to determine if a repo has been initialized.A few things:
Generally this may not be needed as restic init is still supposed to fail if the repo has been previously initialized, but this moves more towards the recommended way for restic.
Also adds an e2e test for the gitops scenario of restoring from a non-existent bucket/repo.
Is there anything that requires special attention?
Related issues: