user-admin password no longer found in environments.yaml

[Jesse Meek]

admin-secret is now found in ~/.juju/environments/local.jenv not ~/.juju/environments.yaml. The message on the login screen needs to be updated.

[Jeff Pihach (hatch)]

Is this a change in 1.17.1?
What about non-local environments?
Will environments.yaml be deprecated?

The Juju documentation still tells the user to use the environments.yaml file and it works according to the message on 1.17.0

Thanks

[Gary Poster (gary)]

For quickstart, this is particularly problematic, I think.

If a value is set in a .jenv file and in environments.yaml, which wins?

[William Reade (fwereade)]

Making people set their own admin-secret sucks, and we end up with passwords like "nothing". The .jenv is now the expected location of the autogenerated admin-secret, and we should update the docs to point to it.

In general, soon, we do want to be able to drop environments.yaml entirely, and get to the point where you can just do `juju bootstrap --provider hpcloud --template /path/to/config/template`.

[Francesco Banconi (frankban)]

Quickstart actions:
   - retrieve the username and the admin-secret from the jenv-file (high);
   - make the envs admin-secret field optional.

GUI actions:
   - in the login view, point the user to the jenv file: its path is
     `$JUJU_HOME/environments/{env name}.jenv`, e.g.:
     `~/.juju/environments/local.jenv`.
This can be problematic for two reasons: IIRC
1) we currently have no way to check the juju-core version from the GUI and
2) the API exposes the environment name only to authenticated users.

[Gary Poster (gary)]

For the GUI, we agreed on the following steps:

0) GUI team will change GUI login text to ask users to look in the jenv
files for admin secrets.

1) GUI team will change Juju Core to add JUJU_ENV_NAME environment
variable for charms, providing the human readable name of the environment.

2) GUI team will change charm to include the environment name in the
configuration file sent to the GUI, if it exists.

3) GUI team will change GUI login text to give exact jenv file to look
in for the admin secret, if the name is available; otherwise it will
fall back to the message from step 0.

User effect:

- Quickstart users continue to have best authentication experience.

- Users of newer Juju + GUI environments are told exactly where to look
for their admin secret (password).

- Users of older Juju environments with newer GUI are at least directed
to the right directory to find the appropriate jenv file with the admin
secret.

I think this bug can be closed on the GUI side once we do step 0. After that, we'll want to tackle the rest ASAP, but the bug itself will be (minimally) addressed by only the step 0 bit.