Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[LIBCLOUD-647] - in newCCI changing the value of sshKeys to a list conta... #416

Closed
wants to merge 1 commit into from

Conversation

@doberloh
Copy link
Contributor

doberloh commented Dec 16, 2014

...ining a dictionary with format {'id':<numcerical_key_value>}

…ntaining a dictionary with format {'id':<numcerical_key_value>}
@Kami
Copy link
Member

Kami commented Dec 16, 2014

Can you please provide more background and reference to the documentation which explains how the payload of sshKeys attribute should look like?

Thanks

@doberloh
Copy link
Contributor Author

doberloh commented Dec 16, 2014

So I found this issue while trying to use libcloud v0.16.0. I suspected there was an issue in the libcloud code when I was getting errors back from the softlayer API while sending ex_keyname='keyname' into the create_node function. I opened a ticket with them and they sent me back a short code snippet using their python library here: https://github.com/softlayer/softlayer-python/tree/master/SoftLayer. In it they sent sshKeys as a list of one dictionary in the format of the change I have made. You can see where they handle ssh keys in their python library at line 350 of the _generate_create_dict method: https://github.com/softlayer/softlayer-python/blob/master/SoftLayer/managers/vs.py. It is the same code that I have modified the libcloud code to be. Hopefully that was enough info :)

@asfgit asfgit closed this in 788ced3 Dec 16, 2014
@Kami
Copy link
Member

Kami commented Dec 16, 2014

Thanks for the clarification.

Looks good, merged into trunk. Thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked issues

Successfully merging this pull request may close these issues.

None yet

2 participants
You can’t perform that action at this time.