On Thu, Mar 5, 2015 at 1:04 AM, Nate Finch wrote:
> There is a bug about us defaulting to uploading the user's private id_rsa
> ssh key to joyent as a part of bootstrapping a new server. This is
> obviously a bad thing. bug:
> https://bugs.launchpad.net/juju-core/+bug/1415671
>
> However, the p
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
wrote:
> On 4 March 2015 at 17:23, Eric Snow wrote:
> > On Wed, Mar 4, 2015 at 10:04 AM, Nate Finch
> wrote:
> >> My suggested solution is that we d
On 4 March 2015 at 17:23, Eric Snow wrote:
> On Wed, Mar 4, 2015 at 10:04 AM, Nate Finch 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 th
On Wed, Mar 4, 2015 at 10:04 AM, Nate Finch 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.
Makes s
There is a bug about us defaulting to uploading the user's private id_rsa
ssh key to joyent as a part of bootstrapping a new server. This is
obviously a bad thing. bug:
https://bugs.launchpad.net/juju-core/+bug/1415671
However, the proposed solution (generate our own key and use that) doesn't
wo
