Comment 6 for bug 834930

Let's please not add a core feature for this before the Go port is live.

gustavo @ http://niemeyer.net
On Apr 26, 2012 12:16 PM, "Clint Byrum" <email address hidden> wrote:

> As a workaround for not having this, a subordinate charm can be used.
>
> The basic gist would be:
>
> * sub charm has config option for allowed SSH keys
> * deploy/relate it to all nodes
> * juju set my-ssh-keys authorized_keys=`cat /the/true/lsit`
>
> The config-changed hook can then update all machines' ssh keys to the
> ones given in authorized_keys.
>
> The only trouble here is you will have to manually update the key on
> node 0, *or* deploy a dummy service to it with "placement: local" which
> can then have the my-ssh-keys subordinate related to it.
>
> --
> You received this bug notification because you are a member of juju
> hackers, which is the registrant for juju.
> https://bugs.launchpad.net/bugs/834930
>
> Title:
> Need a way to manage SSH keys in a juju environment.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/juju/+bug/834930/+subscriptions
>