Missing "juju-2"/"juju2" command.
Bug #1613864 reported by
Eric Snow
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Canonical Juju |
Invalid
|
High
|
Unassigned | ||
| juju-release-tools |
Fix Committed
|
High
|
Unassigned | ||
| juju-core (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Bug Description
For Juju 1 I found the following commands installed:
* /usr/bin/juju
* /usr/bin/juju1
* /usr/bin/juju-1
* /usr/bin/juju-1.25
* /usr/lib/
For Juju 2 I found:
* /usr/bin/juju-2.0
* /usr/lib/
* /usr/bin/
The problem is that, unlike Juju 1, to use the Juju 2 CLI one must hard-code the specific version (e.g. 2.0). Once the next major Juju version (e.g. 2.1) comes out and is installed, such hard-coded, version-specific binary paths will break.
To avoid this problem, I'd like a "/usr/bin/juju2" (and/or "juju-2") be installed alongside the others.
Revision history for this message
| Martin Packman (gz) wrote | #1 |
| Changed in juju-core: | |
| importance: | Undecided → High |
| milestone: | none → 2.1.0 |
| status: | New → Triaged |
Revision history for this message
| Launchpad Janitor (janitor) wrote | #2 |
| Changed in juju-core (Ubuntu): | |
| status: | New → Confirmed |
| affects: | juju-core → juju |
| Changed in juju: | |
| milestone: | 2.1.0 → none |
| milestone: | none → 2.1.0 |
Revision history for this message
| Anastasia (anastasia-macmood) wrote | #3 |
| Changed in juju: | |
| milestone: | 2.1.0 → none |
| tags: | added: usability |
Revision history for this message
| Nicholas Skaggs (nskaggs) wrote | #4 |
| Changed in juju-core (Ubuntu): | |
| status: | Confirmed → Invalid |
| Changed in juju: | |
| status: | Triaged → Invalid |
| Changed in juju-release-tools: | |
| status: | New → Fix Committed |
| Changed in juju-release-tools: | |
| importance: | Undecided → High |
| Changed in juju-release-tools: | |
| status: | Fix Committed → Confirmed |
| status: | Confirmed → Fix Committed |
| status: | Fix Committed → In Progress |
| Changed in juju: | |
| status: | Invalid → In Progress |
| Changed in juju-core (Ubuntu): | |
| status: | Invalid → In Progress |
Revision history for this message
| Anastasia (anastasia-macmood) wrote | #5 |
| Changed in juju: | |
| status: | In Progress → Invalid |
| Changed in juju-core (Ubuntu): | |
| status: | In Progress → Invalid |
| Changed in juju-release-tools: | |
| status: | In Progress → Fix Committed |
To post a comment you must log in.
Ideally we don't have that many aliases for the same thing (and some of those /usr/bin files are not from our latest packaging)?
I think what you really want is to just run `/usr/bin/juju` but realise having juju-1-default makes that more complicated as well. So, I see some benefit in a any-2-series juju alias, but think we'll get pushback on usability of having too many similarly named commands installed by default.
See thread from when this was originally being discussed for some more info:
<https:/