Bug 834930
For those folks wanting a way to manage authorised ssh keys within Juju, trunk
now has that functionality. There are 4 commands:
add - add ssh keys for a Juju user
delete - delete ssh keys for a Juju user
list - list ssh keys for a Juju user
import - import Launchpad or Github ssh
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 13-12-13 03:55 AM, Ian Booth wrote:
I'm guessing people will mostly use import to pull in ssh keys from
Launchpad or Github eg juju authorised-keys import lp:wallyworld.
But for clouds which do not have access to the internet, add is
useful
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 14/12/13 00:22, Aaron Bentley wrote:
On 13-12-13 03:55 AM, Ian Booth wrote:
I'm guessing people will mostly use import to pull in ssh keys from
Launchpad or Github eg juju authorised-keys import lp:wallyworld.
But for clouds which do not have
whether it supports gh:username is somewhat dependent on distro version,
afaics precise versions of ssh-import-id do not support it. if we want to
support the large repository of keys and users from gh on precise, we
should just implement the lookup and addition in go.. key retrieval from
either
