Comment 1 for bug 1718775

I believe we pass all options on to ssh that trail the initial request. So
I *think* that:
juju ssh 0 -i ~/.ssh/mykey

is likely to work as you want.

On Fri, Sep 22, 2017 at 12:32 AM, Peter Matulis <<email address hidden>
> wrote:

> Public bug reported:
>
> Currently (2.3), in order for a non-controller-admin Juju user to
> connect to a machine via SSH the person must either:
>
> - rename their private key (corresponding to the public one added with
> `juju add-ssh-key`) to `id_rsa`
> - add their private key to ssh-agent (`ssh-add`). Note that if ssh-agent
> is not running then starting it is not obvious to many
>
> This can all be done away with if Juju implemented the expected
> behaviour: to be able to specify a key like you can with the native SSH
> client:
>
> `juju ssh -i ~/.ssh/mykey-id_rsa <machine #>`
>
> ** Affects: juju
> Importance: Undecided
> Status: New
>
>
> ** Tags: docteam
>
> --
> You received this bug notification because you are subscribed to juju.
> Matching subscriptions: juju bugs
> https://bugs.launchpad.net/bugs/1718775
>
> Title:
> [feature request] implement native ssh '-i' option
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/juju/+bug/1718775/+subscriptions
>