$ juju switch --format

[David Britton]

Hi William, 

On Fri, Jun 06, 2014 at 07:40:47PM +0200, William Reade wrote:
> 
> To restate your point, I think: you want to be able to keep seeing and
> reading simple names for the contexts you have available to work in.

Yes.  Agreed.

> 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,
IIRC it was like:

  $ juju env
  Current Environment: "local" (from JUJU_ENV)
  $

That was a lot to extract the name from. :)

> 
> "As a user, I want to be able to refer to particular environment connections by short simple names"
> "As a user, I want to be able to see what environment connections I have available"
> "As a user, I want to be able to see what environment connection is currently active"

I'd slightly modify to:

"As a user, I want to print without annotation the currently active environment connection"

If that even makes sense to do in the new world order.  I'll leave that
for you to judge.

> "As a user, I want to be able to quickly activate a given environment connection"
> "As a user, I want to be able to see the details (env uuid, env name, state-servers, etc) of my environment connections"
> 

Agreed with the rest.  Thanks for writing those out.

I see that there are changes coming, and I'm looking forward to what you
have in store.

Thanks to all for taking the time to consider the issues involved.  Good
to see you are taking seriously existing scripts,  the burden of
maintaining old ways of doing things going forward, progress, etc.

-- 
David Britton <david.britton at canonical.com>