Configuration passed during bootstap should be inherited in all newly created models
Bug #1647760 reported by
Dean Maniatis
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Invalid
|
Undecided
|
Unassigned |
Bug Description
When bootstrapping a fresh controller and you pass configuration key-value pairs these are applied to the controller and default model. Any new model though does not inherit these and in my case where i have to operate juju behind proxy whenever i create a new model i have to re-configure that from scratch. It can get even more complicated if you have multiple common configuration keys such as proxy, apt-cache, etc. and have to set these every time you add a new a model.
To post a comment you must log in.
In order to have all models inherit custom key-value configuration, you need to use model-defaults option on bootstrap, see 'juju help bootstrap' for more information:
--model-default (= )
Specify a configuration file, or one or more configuration
options to be set for all models, unless otherwise specified
(--config config.yaml [--config key=value ...])
Alternatively, on an already bootstrapped controller, you can run model-defaults commands, see 'juju help model-defaults'.
Both will allow newly added models to inherit these configuration items.