"juju switch foo:" should switch to the current model of the controller named "foo"

Bug #1662717 reported by Andrew Wilkins
6
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-localhost:
ERROR model name "admin/" not valid

We should support this.

Curtis Hovey (sinzui)
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
Revision history for this message
Tim Penhey (thumper) wrote :

Yes we should. Added a usability card to kanban.

Changed in juju:
milestone: 2.2-rc1 → none
importance: High → Medium
Revision history for this message
Witold Krecicki (wpk) wrote :
John A Meinel (jameinel)
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.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.