Support custom SSH config file for SSH connection #5082
Closed
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.
SSH Docker host connections support specifying an SSH username, hostname, port, and socket path with
ssh://…
. Furthermore, the default user SSH config file located at~/.ssh/config
is respected.However, it would be useful to specify a path to a custom SSH config on the CLI. Use cases are per-project SSH configs or SSH configs generated on the fly (e.g., by
vagrant ssh-config
).- What I did
With this commit, a path to a custom SSH config can be specified as part of the SSH Docker host URL.
This closes #1301. Related issues: #1463, #2539.
- How I did it
An SSH config file can be specified by appending a URL fragment component to the end of the SSH address (that is, behind a hash
#
). The given file path is passed to SSH using thessh -F
option. Example:- How to verify it
Set up:
Test:
Tear down:
- Description for the changelog
- A picture of a cute animal (not mandatory but encouraged)