"juju init" creates a file that includes comments recommending -e to switch environments

[Tom Haddon]

This is taken from a pristine .juju/environments.yaml file created with "juju init":

## 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"

[Tom Haddon (mthaddon)]

<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

[John A Meinel (jameinel)]

I don't think this is a regression, it is just that the position of -e
is required to be after the command.

juju bootstrap -e FOO
not
juju -e FOO bootstrap

I'm not sure how to fix this in the init docs.

On Mon, Mar 10, 2014 at 8:01 PM, Curtis Hovey <email address hidden> wrote:
> ** Tags added: regression
>
> ** Changed in: juju-core
> Importance: Low => High
>
> --
> You received this bug notification because you are subscribed to juju-
> core.
> https://bugs.launchpad.net/bugs/1221134
>
> Title:
> "juju init" creates a file that includes comments recommending -e to
> switch environments
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/juju-core/+bug/1221134/+subscriptions

[Dimiter Naydenov (dimitern)]

In the linked branch I've clarified the way to pass -e envName in the generated boilerplate code. So I can close this once it lands.

If the ability to pass -e env both before or after the command is needed, let's open another bug for it.