Provide password option to 'juju register' and automatically add to accounts.yaml
Bug #1887737 reported by
Haw Loeung
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Triaged
|
Low
|
Unassigned |
Bug Description
Hi,
On creating a new user on a Juju controller, we're presented with a command to run 'juju register' with a base64-encoded blob. On running this command, it prompts for a password 3 times (new, confirm, and to use).
The prompts:
| user@host:~$ juju register MIHc...
| Enter a new password:
| Confirm password:
| Enter a name for this controller [controller]:
| Initial password successfully set for myuser.
| please enter password for myuser on controller:
|
| Welcome, myuser. You are now logged into "controller".
Any chance of adding an option to pass through a password avoiding these 3 prompts? This lets us easily automate (without expect and such).
summary: |
- Provide password option to 'juju register' + Provide password option to 'juju register' and automatically + accounts.yaml |
summary: |
- Provide password option to 'juju register' and automatically + Provide password option to 'juju register' and automatically add to accounts.yaml |
To post a comment you must log in.
And then we have to edit ~/.local/ share/juju/ accounts. yaml and add the password to the relevant stanza so that we don't have to keep logging in (or have our cron jobs that run against the model start failing when the cookie or whatever expires).