Re: developer commands

2017-08-28 Thread Tim Penhey
I don't think the YAML format for status should be the serialized model description as it holds more info, and not all relevant for status. dump-model was originally used to test export code. dump-db was used to get access to the contents of the db without going through mongo shell. Both very

Re: developer commands

2017-08-28 Thread Andrew Wilkins
On Mon, Aug 28, 2017 at 5:17 PM Tim Penhey 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

Re: developer commands

2017-08-28 Thread Anastasia Macmood
Furthermore, if you are seeing any problems with these commands or if you *think* that they no longer behave as per your expectations, let me know :D On 28/08/17 21:18, Anastasia Macmood wrote: > Tim, > > Completely agree :) > > By changing where these commands fit within command infrastructure,

Re: developer commands

2017-08-28 Thread Anastasia Macmood
Tim, Completely agree :) By changing where these commands fit within command infrastructure, they gained access to some useful methods. Thus, eliminating code duplication and inconsistencies. The versions of command, acting as "controller" type commands, that take no arguments, indeed exist.

Re: developer commands

2017-08-28 Thread Tim Penhey
FYI, the developer commands were originally designed like the controller commands. You don't say "juju destroy-model -m foo". 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

Fwd: developer commands

2017-08-28 Thread Anastasia Macmood
-- Here is un-encrypted version \o/ -- 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

Re: developer commands

2017-08-28 Thread John Meinel
I don't think you intended to send the email as PGP encrypted. John =:-> 2017-08-28 12:06 GMT+04:00 Tim Penhey : > -BEGIN PGP MESSAGE- > Version: GnuPG v2 > > hQIMA233D38ktbXXAQ/+P+Wl6YvVE3PVo1tsN/ynVPSeR5Xu3SfKLoRmXvxM0om/ >

Re: developer commands

2017-08-28 Thread Tim Penhey
binMOC2fYDKR9.bin Description: PGP/MIME version identification encrypted.asc Description: OpenPGP encrypted message -- Juju-dev mailing list Juju-dev@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev

developer commands

2017-08-28 Thread Anastasia Macmood
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