Support for different environments files
Bug #1147136 reported by
Ben Howard
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
juju-core |
Won't Fix
|
Low
|
Menno Finlay-Smits |
Bug Description
I need the ability to have to diffent environments.yaml files to support different environments and different levels of access. For example, I could have a "production", "beta", "alpha" environemnts.yaml file. The use cases for this is to allow people to share environments in a production environment, store complete files in a shared repository, and to support enterprise type workflows.
Example Juju:
juju --config /nfs/juju/
tags: | added: improvement |
Changed in juju-core: | |
importance: | Wishlist → Low |
Changed in juju-core: | |
assignee: | nobody → Menno Smits (menno.smits) |
Changed in juju-core: | |
status: | Triaged → In Progress |
milestone: | none → 1.19.2 |
Changed in juju-core: | |
milestone: | 1.19.2 → none |
To post a comment you must log in.
You can currently switch between environments.yaml files by putting them in different dirs (production, beta, alpha) and setting $JUJU_HOME to the appropriate value per command.
It's not appropriate to set a different source for environments.yaml: juju stores important environment info (like the CA cert), by environment name, next to the environments.yaml file in which it is defined, and the risk of catastrophe caused by using two such files in the same dir seems to outweigh the inconvenience of specifying the environment variable.
But, hmm; would something like `--home envs/production` be useful to you? If so, that'd be very simple.