Fix problem with -i argument to rsync/ssh #17
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.
Hi, I found a small problem with the rsync command when using non-default ssh keys. I noticed things would work only if I would create a ~/.ssh/config file and add there by hand the server I wanted to rsync to plus the key I wanted to use. Spelunked a bit more and put the following two statements near the point you create the rsync command and got this:
So, in the code you seem to be giving as key path to the ssh -i argument, the keyfile element of your vagrant provider, but that item is not part of the ssh_info hash which you are using to populate your rsync. The needed info however is in ssh_info[:private_key_path] as can be seen above.
So I just changed that and now I do not need to use a .ssh/config file.
HTH.