Add proxy_command transport setting to inspec runner #176
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
tschroeder-zendesk
force-pushed
the
proxy_command
branch
2 times, most recently
from
2d527c8 to
bbd2c55
Compare
Signed-off-by: Timothy Schroeder <[email protected]>
tschroeder-zendesk
force-pushed
the
proxy_command
branch
from
bbd2c55 to
0c9aad5
Compare
jquick
approved these changes
Jul 5, 2018
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Allow setting for proxy_command that was added to train here: inspec/train#227
Example config:
My main use case for this is we use a bastion host and therefor I need to be able to jump through the appropriate hoop to reach my instance which I can do with the above example.