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

option to set the path to ssh key #29

Closed
slatunje opened this issue Jan 6, 2015 · 4 comments
Closed

option to set the path to ssh key #29

slatunje opened this issue Jan 6, 2015 · 4 comments

Comments

@slatunje
Copy link

slatunje commented Jan 6, 2015

currently it is assumed the ssh key will be found in ~/.ssh/id_rsa.pub

I happen to have three ssh keys:

~/.ssh/id_rsa.pub
~/.ssh/CompanyA/id_rsa.pub
~/.ssh/CompanyB/id_rsa.pub

It would be nice to be able to set the path to ssh key. the benefit is that companyA and companyB can also use juju-digitalocean

@lazypower
Copy link

Commenting to add some bug heat here, just had a user land in #juju with this issue on OSX. I beleive this is actually using the ssh agent keyring is it not @kapilt?

@travenasty
Copy link

That user was me. :)

@kapilt
Copy link
Owner

kapilt commented Feb 17, 2015

the plugin doesn't touch any keys. this is more about juju' config for ssh keys, or how you have ssh configured. ssh will sniff and try a number of keys when logging into remote systems, you can explicitly specify a private key on the cli, or via using an agent. as juju is the one invoking ssh, you have to configure an explicit private key in enviroments.yaml or ssh key agent via environment variable.

@kapilt
Copy link
Owner

kapilt commented Jul 2, 2015

rephrased, this is about the user configuring environment ssh keys via juju in their juju environments.yaml configuration. do plugin simply consumes that config invokes juju where needed atm.

@kapilt kapilt closed this as completed Jul 5, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants