"juju switch foo:" should switch to the current model of the controller named "foo"
Bug #1662717 reported by
Andrew Wilkins
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Fix Released
|
Medium
|
Witold Krecicki |
Bug Description
We can use "juju switch :foo" to switch to the model called "foo" within the current controller, but it is not possible to use "juju switch foo:" to switch to the current model within a named controller:
$ juju switch localhost-
ERROR model name "admin/" not valid
We should support this.
Changed in juju: | |
milestone: | 2.2-beta1 → 2.2-beta2 |
Changed in juju: | |
milestone: | 2.2-beta2 → 2.2-beta3 |
Changed in juju: | |
milestone: | 2.2-beta3 → 2.2-beta4 |
Changed in juju: | |
milestone: | 2.2-beta4 → 2.2-rc1 |
Changed in juju: | |
assignee: | nobody → Witold Krecicki (wpk) |
milestone: | none → 2.3-alpha1 |
status: | Triaged → Fix Committed |
Changed in juju: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Yes we should. Added a usability card to kanban.