Joyent SSH key

Nate Finch nate.finch at canonical.com
Wed Mar 4 21:36:03 UTC 2015


I updated my branch to simply error out if there's no private key set.
http://reviews.vapour.ws/r/861

On Wed, Mar 4, 2015 at 1:30 PM, Nick Veitch <nick.veitch at canonical.com>
wrote:

> On 4 March 2015 at 17:23, Eric Snow <eric.snow at canonical.com> wrote:
> > On Wed, Mar 4, 2015 at 10:04 AM, Nate Finch <nate.finch at canonical.com>
> wrote:
> >> My suggested solution is that we do what we do for all the rest of the
> >> providers, which is to make the user give us authentication credentials
> in
> >> the environments.yaml file, and we just use that, and not create
> anything
> >> ourselves.
>
> That is currently the advice in the documentation - to generate a new
> key and explicitly provide it in the environments.yaml. I think if we
> removed the default action (using the default ssh key) that would be
> fine, as long as there was a suitable error message. It isn't as
> though users will have to configure it every day, it's a one-time
> inconvenience, but one that doesn't make any unnecessary assumptions.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/juju-dev/attachments/20150304/b7b06c2c/attachment-0001.html>


More information about the Juju-dev mailing list