`juju import-ssh-key`

Usage:

juju import-ssh-key [options] <lp|gh>:<user identity> ...

Summary:

Adds a public SSH key from a trusted identity source to a model.

Global Options:

--debug  (= false)

Equivalent to --show-log --logging-config==DEBUG

-h, --help  (= false)

Show help on a command or other topic.

--logging-config (= "")

Specify log levels for modules

--quiet  (= false)

Show no informational output

--show-log  (= false)

If set, write the log file to stderr

--verbose  (= false)

Show more verbose output

Command Options:

-B, --no-browser-login  (= false)

Do not use web browser for authentication

-m, --model (= "")

Model to operate in. Accepts [:]|

Details:

Juju can add SSH keys to its cache from reliable public sources (currently Launchpad and GitHub), allowing those users SSH access to Juju machines.

The user identity supplied is the username on the respective service given by ‘lp:’ or ‘gh:’.

If the user has multiple keys on the service, all the keys will be added.

Once the keys are imported, they can be viewed with the juju ssh-keys command, where comments will indicate which ones were imported in this way.

An alternative to this command is the more manual juju add-ssh-key.

Examples:

Import all public keys associated with user account ‘phamilton’ on the GitHub service:

juju import-ssh-key gh:phamilton

Multiple identities may be specified in a space delimited list:

juju import-ssh-key gh:rheinlein lp:iasmiov gh:hharrison

See also:

add-ssh-key
ssh-keys

It seems that that it imports only the last one on the list of my ssh-keys in github ( I got 4 keys).
So the statement “all the keys will be added” is false. Might be bug or feature :wink:

$ juju --version
2.8.1-mojave-amd64
$ juju controllers
Use --refresh option with this command to see the latest information.

Controller Model User Access Cloud/Region Models Nodes HA Version
jaas* jujucanonicaltest mastier1@external (unknown) 1 - - 2.7.6