search

kapilt / juju-digitalocean

JuDo - A juju provider for digital ocean using a client side plugin and manual provisioning.
111 stars 17 forks source link

option to set the path to ssh key #29

Closed slatunje closed 9 years ago

slatunje commented 9 years ago

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 commented 9 years ago

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 commented 9 years ago

That user was me. :)

kapilt commented 9 years ago

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 commented 9 years ago

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.