Use .ssh/config to setup SSH proxy jump #64
Merged
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.
Unfortunately, my previous attempt to route deployment through a jumphost1 doesn't work. Turns out that specifying a proxyjump host inline doesn't support specifying an SSH key to authenticate with. It worked well on my machine because some default key was used transparently, but it fails on CD where no such key exist.
The new approach tries to address the problem by moving away from inline SSH configuration towards the .ssh/config file, which has everything needed specified.
Footnotes
7aec773 ↩