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.
On 30/04/15 20:46, roger peppe wrote: > At the Nuremberg sprint, I saw a demo of juju status that produced > tabular format > by default. I'm guessing that this issue means that can never actually be > enabled. > > Although... it could be done backwardly compatibly (with a required > environment > variable or configuration file setting) and perhaps that shows the way forward > here. We could allow a user to change a setting that enables backwardly > incompatible features (such as removing environment fallback or > producing tabular format status). That doesn't help with the code cruft issue > though. > > > On 30 April 2015 at 11:29, Michael Hudson-Doyle > <[email protected]> wrote: >> I don't want to bore on and on about this, but one thing. >> >> On 30 April 2015 at 22:06, Nate Finch <[email protected]> wrote: >>> If someone needs 1.18 CLI compatibility, they can use 1.18. It's that >>> simple. >> >> It's not that simple to do that though, as long as new versions of >> juju go into trusty-updates. You'd have to pin the version or do >> apt/preferences junk to prefer trusty over trusty-updates for >> juju-core or something. I'm not even sure, and I'm much more familiar >> with this sort of thing than it makes sense to assume our users are. >> >> Cheers, >> mwh >> >> -- >> Juju-dev mailing list >> [email protected] >> Modify settings or unsubscribe at: >> https://lists.ubuntu.com/mailman/listinfo/juju-dev > -- Juju-dev mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev
