juju commands don't detect a fresh juju 1.X user and helpfully tell them where to find juju 1.X
Bug #1565991 reported by
Gui Bot
This bug report is a duplicate of:
Bug #1564622: Suggest juju1 upon first use of juju2 if there is an existing JUJU_HOME dir.
Edit
Remove
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| juju-core |
Triaged
|
High
|
Unassigned | ||
Bug Description
When a Juju 1.X user is dist-upgrading to xenial and uses Juju 2.0 for the first time, Juju should help the user along with the change in 1.X -> 2.X by providing a one time message hint that Juju 1 is still available at a new location for them to continue using.
An example user flow:
do-
.... lots of things
juju switch
Welcome to Juju 2.0. You can continue using juju-1.25.5 with the command juju-1 e.g. `juju-1 switch`
It should detect this situation if the user has existing juju 1.X config but no juju 2.X config. It should also only be run on the first occasion so that we don't spam the user over and over.
| Changed in juju-core: | |
| status: | New → Triaged |
| importance: | Undecided → High |
| milestone: | none → 2.0-beta4 |
To post a comment you must log in.
