New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Please add sftp.extra_args #4241
Comments
Hi, having the same problem. Workaround is presented in #312 (comment) and #312 (comment). Seeing restic/src/restic/backend/sftp/sftp.go Line 140 in 1733b24
|
Yes, an option to influence how buildSSHCommand works is much needed. Precisely for adding custom options such as |
Allow setting custom arguments for the `sftp` backend, by using the `sftp.args` option. This is similar to the approach already implemented in the `rclone` backend, to support new arguments without requiring future code changes for each different SSH argument. Closes restic#4241
I have created #4519, looking forward to solve this issue and make those workarounds obsolete. |
Allow setting custom arguments for the `sftp` backend, by using the `sftp.args` option. This is similar to the approach already implemented in the `rclone` backend, to support new arguments without requiring future code changes for each different SSH argument. Closes restic#4241
|
Output of
restic version
restic 0.15.1 compiled with go1.19.5 on linux/amd64
What should restic do differently? Which functionality do you think we should add?
I need to point ssh restic is using to a specific keyfile. In order to provide both repository and ssh command like this:
Can you please add something like
sftp.extra_args
that would be used directly inbuildSSHCommand
and just added to the command line? I can then say--option sftp.command=-i\ /etc/restic/keys/foo
and the whole thing would look cleaner.The solution suggested in the manual (using
~/.ssh/config
) is nice, but I'd really like to keep all config file in a single place, and avoid having them intermixed with otherwise unrelated entries in ssh's config. I can make a separate config file for this purpose, but then I need to point ssh to it, which brings us to the same problem as my initial one :)What are you trying to do? What problem would this solve?
The
restic
command line invocation would look cleaner.Did restic help you today? Did it make you happy in any way?
Eyeballing
restic
as borgbackup replacement; doing so would allow me to use a cheaper backend storage :)Thanks!
The text was updated successfully, but these errors were encountered: