Handle relative ssh key paths in TF JSON #1398
Open
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
|
I don't know how this is supposed to work anymore. |
added 9 commits
June 13, 2019 11:31
kke
changed the title
kke
commented
Jun 13, 2019
| Dir.chdir(config_yaml.dirname) do | ||
| if command_list.empty? |
There was a problem hiding this comment.
Config parsing in ssh/exec interactive mode was not done in config_yaml.dirname context.
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.
Fixes #1397
Fixes #1402
Makes ssh_key_path option handle relative paths (relative to the tf.json location)