juju docs recommend "juju init -w" but that fails
Bug #1221127 reported by
Tom Haddon
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
pyjuju |
Fix Released
|
Low
|
Martin Packman |
Bug Description
https:/
"""First configure your environment local environment, if you've not set up Juju before do a:
juju init -w"""
However, "juju init -w" gives "error: flag provided but not defined: -w"
I'm using juju-core 1.13.3-
Related branches
lp:~gz/juju-core/boilerplate_doclinks
- Juju Engineering: Pending requested
-
Diff: 34 lines (+3/-3)2 files modifiedprovider/local/environprovider.go (+1/-1)
provider/openstack/provider.go (+2/-2)
Changed in juju: | |
status: | In Progress → Fix Released |
To post a comment you must log in.
<mgz> mthaddon: looking at juju.ubuntu.com and the branch, the local provider setup instructions say `juju generate-config` not `juju init -w` it seems /juju.ubuntu. com/get- started/ local/ ? /juju.ubuntu. com/docs/ config- local.html
<wallyworld_> wow, generate-config is old
<TheMue> it's an alias
<mthaddon> mgz: is that different from https:/
<mgz> ...yes
<mgz> hm, clicking on local configuration from the getting started link gets me to the right page, but not that one...
<TheMue> oh, just seen, we're inconsistent in our internal help texts. some times "init -w", some times "generate-config -w".
<mthaddon> ah, I see - if you navigate from the website you get to https:/
<mthaddon> I was following the link in the generated juju env file from "juju init"
<mthaddon> I'll note that in the bug report