$ juju switch --format

[John Meinel]

...


> > Do the following use cases express your needs (even if you weren't
> > hitherto aware that you were specifically manipulating environment
> > *connections*)?
>
> Ah, ok, things are changing, got it.  Making sure patterns like the
> following are still easily grok-able (even if it's a different command)
> is nice:
>
>   juju destroy-environment $(juju env)
>
> Juju env used to print a lot of decoration around the environment name,
>

As a side note, I love how the explicit request to us was "juju destroy
environment is too easy to destroy the wrong thing, can you please make it
so that you have to type the explicit name so we know we are destroying the
right thing", and people quickly figured out how to write a command that
destroys whatever the current environment is to workaround the exact syntax
we put in place to protect it.

Nothing to do with you specifically, just that people's use cases are
different. I certainly hope we never document "juju destroy-environment
$(juju env)" as a recommended thing. But it does signal that some people
really don't want the extra safety measures and would much rather have a
clean way of disabling them.

John
=:->
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/juju-dev/attachments/20140607/acde5cab/attachment.html>