On Fri, Sep 26, 2014 at 12:57 AM, Tim Penhey <tim.pen...@canonical.com> wrote:
> Hi folks, > > All environments that exist so far have had an "admin" user being the > main (and only) user that was created in the environment, and it was > used for all client connections. > > Code has landed in master now that makes this initial username > configurable. The juju client is yet to take advantage of this, but > there is work due to be finished off soon that does exactly that. > > Soon, the 'juju bootstrap' command will use the name of the currently > logged in user as the initial username to create [1]. So, for me > > juju bootstrap > > would create the initial user "tim" (or "thumper" if I am logged in as > my other user). > > If the current username is not translatable to a valid username, the > command will fail and require the user to specify the name of the > initial user on the command line. > > juju bootstrap --user eric > > After talking with Rick this morning, he mentioned that 'juju > quickstart' had "admin" hard coded, and there are bound to be other > places too. > > Your about to break alot of api using programs out there without having given a reason for why? Ie. can we do admin and logged in user for the bootstrapping user? I've moved jujuclient to using jenv files for connections (as its the only way to get the username, password, api servers, and cert info), i'll see about issuing an update for it to use the login user from there as well. The issue is for remote environments / ie servers interacting with juju, there is no logged in environment user (and no jenv), and no clear way to get one without changing user interfaces for the user to input one if they know it (was it thumper or tim)? cheers, Kapil
-- Juju-dev mailing list Juju-dev@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev
