For JAAS, doesn't a 'default model property' need to be a user level setting, because it doesn't make sense as at a Controller level because all-of-JAAS is your Controller (we don't expose the individual controllers).
We should also consider how Migration is impacted by defaults like this. John =:-> On Tue, Jun 14, 2016 at 11:54 AM, Mark Shuttleworth <m...@ubuntu.com> wrote: > On 14/06/16 08:33, Ian Booth wrote: > >> That's why I prefer: > >> > >> set-controller-config > >> set-model-config > >> set-model-default > >> > > I like the above too. But some folks we've talked to have thought that > > introducing 3 commands (the ones above) is cognitive overhead. > > Heh. Ian, if you like, and I like it, let's just do it :) > > What will we do for JAAS, where there will be many controller and many > clouds? Seems like we should make sure that any cloud-specific defaults > / properties are not inadvertently implemented as model config/defaults. > > Mark > > > -- > Juju-dev mailing list > Juju-dev@lists.ubuntu.com > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/juju-dev >
-- Juju-dev mailing list Juju-dev@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev
