On 8 June 2016 at 10:41, Andrew Wilkins <andrew.wilk...@canonical.com> wrote:
> Hi folks,
>
> We're in the midst of making some changes to model configuration in Juju
> 2.0, separating out things that are not model specific from those that are.
> For many things this is very clear-cut, and for other things not so much.
>
> For example, api-port and state-port are controller-specific, so we'll be
> moving them from model config to a new controller config collection. The end
> goal is that you'll no longer see those when you type "juju
> get-model-config" (there will be a separate command to get controller
> attributes such as these), though we're not quite there yet.
Interesting - seems like a good change.
Will this change the internal and API representations too, so there
are two groups
of mutually-exclusive attributes? Does this also mean that the
really-not-very-nice
ConfigSkeleton API method will go too?
cheers,
rog.
--
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/juju
