Fix problem when setting public key from String. #15
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
This needs to return the RSA encoded public key instead of the tuple (Array). It was failing attempting to call #to_pem here.
jkeiser
added a commit
that referenced
this pull request
Aug 22, 2014
Fix problem when setting public key from String.
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.
While using the chef_client resource this failed because I wasn't passing
OpenSSL::PKey::RSAbut instead aStringas the API indicates is acceptable. The formatter returns an Array tuple which fails a little bit further down when setting the JSON (assuming for payload) using the#to_pemmethod call.