Retry getting private key without the driver config if its not originally found #503
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.
I was trying to initialize a fog driver, when I kept running into this issue:
Much to my frustration, the key it was looking for were in both of those locations. I traced the issue back to this method, which passes the driver config into the Cheffish module method. If the config doesn't have :private_key_paths set, then it just returns nil, and ultimately the driver fails back up the stack.
This fix tries to get the private key using the driver config first, and if nothing returned, will try again without the driver config (and Cheffish will just default to pulling its own node's config in).