I believe --config can take a file rather than just a 'key=value' pairing. So you can save all your config to a file and pass it in with '--config myconf.yaml'
There was discussion of having a default search path for some of the config, but I'm not sure if that got implemented, nor if it is actually better since it is another magic place that you have to discover. John =:-> On Tue, Apr 26, 2016 at 9:14 PM, David Britton <david.brit...@canonical.com> wrote: > On Tue, Apr 26, 2016 at 11:58:38AM -0500, Cheryl Jennings wrote: > > > > > > On Apr 25, 2016 12:55, "Andreas Hasenack" <andr...@canonical.com> > wrote: > > > > > >> Uh, so in essence there are now three "files"? Cloud definition, > config > > >> for that cloud and credentials? And the config has to be passed each > time, > > >> whereas the other two are " imported"? > > >> > > > Yes, that's correct. 1 - The cloud definition (built in for public > > clouds), 2 - credentials, and 3 - config that can be specified upon each > > bootstrap. > > Are there any plans to allow this to be stored between controller > bootstraps? > > Background -- We have some substrates where specifically the default > timeout is too low for the maas provider. There are also considerations > like proxies, apt proxies, etc that all become quite cumbersome to type > and remember on the command line. > > -- > David Britton <david.brit...@canonical.com> > > -- > Juju mailing list > Juju@lists.ubuntu.com > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/juju >
-- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
