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

builder/triton: Replace deprecated joyent/gosdc library with joyent/triton-go #4838

Merged
merged 5 commits into from
Apr 26, 2017
Merged

builder/triton: Replace deprecated joyent/gosdc library with joyent/triton-go #4838

merged 5 commits into from
Apr 26, 2017

Conversation

jen20
Copy link
Collaborator

@jen20 jen20 commented Apr 26, 2017

This pull request replaces the client library used by the Triton builder for a newer one. We also make some modifications to make private_key_material optional in order to allow signing HTTP requests to Triton using encrypted keys which are stored in an SSH agent.

In addition, a bug with default networks is fixed, and the documentation is updated to reflect the new behaviour.

This commit substitutes the now-deprecated gosdc library for the newer
triton-go library. This is transparent from a user perspective, except
for the fact that key material can now be ommitted and requests can be
signed with an SSH agent. This allows for both encrypted keys and ECDSA
keys to be used.

In addition, a fix is made to not pass in an empty array of networks if
none are specified in configuration, thus honouring the API default of
putting instances with no explicit networks specified on the Joyent
public and internal shared networks.
This commit adds an actual public/private key pair for testing since
these are now validated.
@mwhooker mwhooker added this to the v1.0.1 milestone Apr 26, 2017
Copy link
Contributor

@mwhooker mwhooker left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

seems good to me. Any thoughts on if #4829 is still relevant?

I'll see if I can spin up the example and should be able to reconcile the two, but probably won't be able to get to it today

@mwhooker
Copy link
Contributor

In addition, a bug with default networks is fixed, and the documentation is updated to reflect the new behaviour.

Do you think that could be responsible for #4623?

@jen20
Copy link
Collaborator Author

jen20 commented Apr 26, 2017

@mwhooker It seems unlikely to be related to #4623, but I can investigate that from this side too. I can reconcile with #4829 - I'll follow up with a new PR for that.

@jen20 jen20 merged commit a0271a1 into hashicorp:master Apr 26, 2017
@jen20 jen20 deleted the triton-new-lib branch April 26, 2017 22:14
mwhooker added a commit that referenced this pull request Apr 26, 2017
@ghost ghost locked and limited conversation to collaborators Apr 4, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants