On Mon, Aug 28, 2017 at 5:17 PM Tim Penhey <tim.pen...@canonical.com> wrote:
> FYI, the developer commands were originally designed like the controller > commands. > > You don't say "juju destroy-model -m foo". > I think that holds for "dump-model", but I'm not so sure about "dump-db". It feels natural enough to me to say "juju dump-db -m foo", or "juju dump-db". I'm wondering about the future of "dump-model". Since you've been looking at using the model description to feed "juju status", I wonder if it wouldn't make sense to update the "juju status" YAML format to be exactly the model description. Then "dump-model" becomes redundant. We'd have to make it an option, though, because backwards compatibility. Cheers, Andrew > Tim > > On 28/08/17 19:48, Anastasia Macmood wrote: > > Hi > > > > Just a quick note for developers that use developer commands. > > > > 'juju dump-model' and 'juju dump-db' are changing on develop tip [1], > > from 2.3.x. > > These commands are now fully-fledged model commands as they were > > originally designed. > > This means that they will now accept model name as an option instead of > > as a positional argument. > > > > i.e. > > 'juju dump-model -m modelName' NOT 'juju dump-model modelName' > > 'juju dump-db -m modelName' NOT 'juju dump-db modelName' > > > > Happy juju-ing! > > > > Sincerely Yours, > > Anastasia > > > > [1] > > https://github.com/juju/juju/pull/7797 > > > > > > -- > 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
