previously valid amazon environment now invalid?

[Ian Booth]

On 30/04/15 21:04, roger peppe wrote:
> On 30 April 2015 at 11:55, Ian Booth <ian.booth at canonical.com> wrote:
>> Right now, the default tabular output is behind a feature flag because it's
>> experimental. We still need to decide how to allow users to have that output by
>> default without the feature flag, but also without breaking 1.18 script
>> compatibility. The best option IMO for this case is an env variable on the
>> user's client machine since the change is a client only one and I don't want to
>> pollute the CLI with --v2 type cruft and introduce yet another thing to support
>> in the future.
> 
> The danger here is that we end up with 100 environment variables, each
> tweaking some aspect of the Juju client's behaviour, and that
> debugging becomes hard because every user has some
> uniquely different combination of settings.
> 
> Perhaps a single environment variable, say JUJU_COMPAT,
> defining the oldest version required for backward compatibility,
> might work here? The default value would be whatever
> is the oldest version that we currently support.
> 

Agreed. That's what I was alluding to with the --v2 arg example.
When Juju 2.0 ships we can turn on the new behaviour by default. Until then,
people should have an easy way to choose the new behaviour if they want  to use it.