feat: support custom params and parallelism for restore (#6) #11
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.
All other basic operations already support custom flags. Even the restore itself is supposed to already support them but, as opposed to Barman, pgBackRest has two separate commands used during the restore:
Currently only the archive-get part is customizable.
Especially painful is the inability to configure parallelism as that means the main backup can take very long time to download, hence a dedicated field for it (just like for backups).