"juju init" creates a file that includes comments recommending -e to switch environments
Bug #1221134 reported by
Tom Haddon
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
juju-core |
Fix Released
|
High
|
Dimiter Naydenov |
Bug Description
This is taken from a pristine .juju/environme
## The default environment is chosen when one is not specified using either:
## -e, --environment command line parameter
## JUJU_ENV environment variable
## If both -e and JUJU_ENV are specified, the command line parameter has precedence.
However, if you try juju -e you get "error: flag provided but not defined: -e"
Related branches
lp:~dimitern/juju-core/330-general-improvements
- Juju Engineering: Pending requested
-
Diff: 1961 lines (+551/-446)35 files modifiedcmd/juju/destroyenvironment.go (+1/-1)
cmd/juju/destroyenvironment_test.go (+2/-2)
cmd/juju/help_topics.go (+31/-25)
environs/boilerplate_config.go (+20/-8)
environs/bootstrap/bootstrap.go (+3/-2)
environs/bootstrap/state.go (+2/-0)
environs/cloudinit/cloudinit.go (+2/-2)
environs/cloudinit/cloudinit_test.go (+4/-4)
environs/httpstorage/storage.go (+7/-0)
environs/jujutest/livetests.go (+2/-3)
environs/jujutest/tests.go (+5/-6)
environs/manual/bootstrap_test.go (+17/-16)
environs/manual/export_test.go (+7/-0)
environs/manual/fakessh.go (+0/-87)
environs/manual/fakessh_test.go (+156/-0)
environs/manual/init.go (+9/-7)
environs/manual/init_test.go (+26/-26)
environs/manual/provisioner_test.go (+10/-9)
environs/open.go (+22/-14)
environs/sshstorage/storage.go (+6/-0)
environs/testing/storage.go (+0/-17)
environs/utils.go (+22/-0)
juju/conn_test.go (+3/-3)
provider/azure/config.go (+19/-11)
provider/common/bootstrap.go (+0/-15)
provider/ec2/ec2.go (+16/-9)
provider/joyent/config.go (+40/-19)
provider/local/environprovider.go (+15/-9)
provider/maas/environprovider.go (+4/-2)
provider/manual/environ.go (+1/-0)
provider/openstack/provider.go (+89/-59)
state/apiserver/charms.go (+3/-3)
state/apiserver/charms_test.go (+3/-3)
state/apiserver/client/client_test.go (+4/-4)
utils/ssh/testing/fakessh.go (+0/-80)
affects: | juju → juju-core |
Changed in juju-core: | |
status: | New → Triaged |
importance: | Undecided → Low |
tags: | added: doc ui |
tags: |
added: docs removed: doc |
Changed in juju-core: | |
status: | Triaged → In Progress |
assignee: | nobody → Dimiter Naydenov (dimitern) |
milestone: | none → 1.17.5 |
tags: | added: regression |
Changed in juju-core: | |
importance: | Low → High |
Changed in juju-core: | |
status: | In Progress → Fix Committed |
Changed in juju-core: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
<mgz> commands where having an environment makes sense should interpret -e
<mthaddon> mgz: how so?
<mthaddon> mthaddon@mallory:~$ juju -e amazon status
<mthaddon> error: flag provided but not defined: -e
<mgz> hm, maybe it's only registered as a normal flag now, after the plugin changes... I take it `juju status -e amazon` works?
<mthaddon> ah, yeah, it does, will update the bug report