Copy: Switch away from deprecated "2" suffix #452
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
In v0.14.0 (released Aug 2022), restic has deprecated the copy command options with the "2" suffix (e.g., --repo2 / RESTIC_REPOSTORY2) in favor of the "RESTIC_FROM_" prefix. The old format is still supported, but new options will not be backported. Notably, even restic does not (yet?) map all relevant options in its copy command. For instance, while the backup command supports RESTIC_REST_PASSWORD, the copy command does not consider RESTIC_FROM_REST_PASSWORD.
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
|
I tested this PR and this indirectly solves this issue copy to backblaze fails #219 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
In v0.14.0 (released Aug 2022), restic has deprecated the copy command options with the "2" suffix (e.g., --repo2 / RESTIC_REPOSTORY2) in favor of the "RESTIC_FROM_" prefix. The old format is still supported, but new options will not be backported.
Notably, even restic does not (yet?) map all relevant options in its copy command. For instance, while the backup command supports RESTIC_REST_PASSWORD, the copy command does not consider RESTIC_FROM_REST_PASSWORD.