support ~/.juju/environments.d

Bug #1155276 reported by Sidnei da Silva
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Canonical Juju
Fix Released
Low
Unassigned
juju-core
Won't Fix
Low
Unassigned
1.25
Won't Fix
Low
Unassigned

Bug Description

It's nice that ~/.juju/environments.yaml is structured and all that, but would be much nicer if one could add/remove environment configs by adding/deleting a file under ~/.juju/environments.d/<name>.yaml instead.

Tags: improvement
Revision history for this message
Dave Cheney (dave-cheney) wrote :

Hello,

For the 1.9.12 release the juju cli tool now supports a JUJU_HOME environment variable. This defaults to $HOME/.juju but can be used to switch between juju configurations.

Please let me know if you find this sufficient.

Changed in juju-core:
status: New → Fix Committed
milestone: none → 1.9.12
milestone: 1.9.12 → none
status: Fix Committed → New
Revision history for this message
William Reade (fwereade) wrote :

I think this is a distinct and valid use case.

Changed in juju-core:
importance: Undecided → Wishlist
status: New → Triaged
Curtis Hovey (sinzui)
tags: added: improvement
Curtis Hovey (sinzui)
Changed in juju-core:
importance: Wishlist → Low
Revision history for this message
Cheryl Jennings (cherylj) wrote :

With Juju 2.0, there is no longer a need for environments.yaml. Public clouds are "built in" and private clouds can be defined using `juju add-cloud`.

Bootstrapping additional controllers doesn't require additional configuration, just specify a different name at bootstrap time.

Changed in juju-core:
status: Triaged → Fix Released
affects: juju-core → juju
Changed in juju-core:
importance: Undecided → Low
status: New → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.