Juju environment can be specified via environment variable.

Reported by Kapil Thangavelu on 2012-02-15
18
This bug affects 3 people
Affects Status Importance Assigned to Milestone
pyjuju
Undecided
Kapil Thangavelu

Bug Description

The environment variable JUJU_ENV can now also be used to specify which
environment to use, this value takes precedence over the default in
environments.yaml, but is preceded by an explicit env on the cli args.

Related branches

lp:~hazmat/juju/env-from-env
Merged into lp:juju at revision 476
Benjamin Saller: Approve on 2012-02-23
Jim Baker (community): Approve on 2012-02-23
Changed in juju:
assignee: nobody → Kapil Thangavelu (hazmat)
milestone: none → florence
status: New → In Progress
Gustavo Niemeyer (niemeyer) wrote :

That's a nice idea, thanks.

Please do remember to mention such changes in the mailing list. It's hard to spot which bugs should be watched out for since they contain API modifications that will affect the Go port.

Changed in juju:
status: In Progress → Fix Released

Excerpts from Gustavo Niemeyer's message of 2012-02-16 03:40:55 UTC:
> That's a nice idea, thanks.
>
> Please do remember to mention such changes in the mailing list. It's
> hard to spot which bugs should be watched out for since they contain API
> modifications that will affect the Go port.
>

This was discussed on the list as part of yellow team's feedback, and then
summarized again in a separate email. Are you suggesting each change needs its
own separate email in a new thread?

-k

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers