juju credentials <cloud> doesn't verify if the cloud exists
Bug #1624069 reported by
Nate Finch
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Canonical Juju |
Invalid
|
Medium
|
Unassigned | ||
Bug Description
if you do juju credentials asdfgghjkl ... what you get is
$ juju credentials asdfghjkl
CLOUD CREDENTIALS
$
We should be printing an error that you typed a cloud that doesn't exist. A more convincing use case is if you typo the name of your cloud... you just get an empty list of credentials, which is confusing, rather than a helpful error message that you typoed the cloud name.
| tags: | added: usability |
| Changed in juju: | |
| status: | New → Triaged |
| importance: | Undecided → Medium |
| milestone: | none → 2.0-rc2 |
| Changed in juju: | |
| milestone: | 2.0-rc2 → 2.0.1 |
| Changed in juju: | |
| milestone: | 2.0.1 → none |
Revision history for this message
| Anastasia (anastasia-macmood) wrote | #1 |
| Changed in juju: | |
| status: | Triaged → Invalid |
To post a comment you must log in.
Since this report was filed, Juju has moved to a multi-cloud world where a cloud may not be known to a client but may exist on the controller for this user.
As such, the desire described in this report is no longer relevant. It makes more sense to specify where we've looked for such a cloud and whether we have found it or not.
For eg, in the case above we'd have:
$ juju credentials afssfs
No locally stored credentials to display.