[add-cloud] users are told to bootstrap prematurely
Bug #1749583 reported by
Peter Matulis
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Fix Released
|
Medium
|
Peter Matulis |
Bug Description
At the completion of every add-cloud dialog the following output is printed (assuming a cloud name of 'mycloud'):
> Cloud "mycloud" successfully added
> You may bootstrap with 'juju bootstrap mycloud'
This is very misleading. That *is* the command to use but it won't work until a credential is added.
Suggestion:
> Cloud "mycloud" successfully added
> Add a credential with 'juju add-credential mycloud'
> You may bootstrap with 'juju bootstrap mycloud'
Note that the Manual cloud does not need a Juju-added credential so logic would be needed to account for that (suppress the second line of the suggested output).
---
See also bug #1649567 and bug #1732079 and bug #1749302
Changed in juju: | |
assignee: | nobody → Anastasia (anastasia-macmood) |
status: | New → Triaged |
importance: | Undecided → Medium |
tags: | added: usability |
Changed in juju: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
@PPeter Matulis,
I can see that you have already added necessary lines as part of the https:/ /github. com/juju/ juju/commit/ 4cd4e5043ec26d2 5c356995f9b87ae 2da946b475. Thank you!
I think that it is good enough for now, although for the clouds that do not require a credential, i.e. that have an auth type of empty, this message will be redundant. I do not think that we have any cloud that have only that auth type - they usually have another auth type too. In any case, if we do encounter clouds with auth type empty exclusively, we can revisit this message as part of a different bug and make it conditional.