asking about local vs remote inconsistent between add-cloud and add-credential
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Fix Released
|
Medium
|
Anastasia | ||
2.7 |
Fix Released
|
Medium
|
Anastasia |
Bug Description
When adding a cloud I get dropped straight into the workflow and selecting the type, submitting a name, etc. Only at the end do I get the question of adding this new cloud locally or on a controller. I prefer this workflow personally.
When you add a credential you get distracted right off the bat.
This operation can be applied to both a copy on this client and to the one on a controller.
No current controller was detected and there are no registered controllers on this client:
either bootstrap one or register one.
Do you ONLY want to add a credential to this client? (Y/n):
In this case where I have no controllers I also get questioned about a controller when there is none which seems unnecessary.
It'd be smoother if the commands were more consistent with their workflows.
Changed in juju: | |
status: | In Progress → Fix Committed |
Changed in juju: | |
status: | Fix Committed → Fix Released |
Interestingly the credentials command deals with the lack of a controller much better. This would be great to also be more consistent.
% juju credentials
No credentials from any controller to display.
Client Credentials:
Cloud Credentials
google company
guimaas rharding
guimaas-ip rharding
localhost localhost*