juju min version feature

[William Reade]

On Mon, Dec 15, 2014 at 6:13 PM, John Meinel <john at arbash-meinel.com> wrote:
> Can't we just as easily provide tools to find out what version of Juju
> provides a particular feature? Certainly a CLI of:
>  $ juju supported-features
>   leader-election
>   container-addressibility
>
> Or even possibly something that talks to something like the charm-store:
>  $ juju known-features
>  leader-election: juju >= 2.2
>  container-addressibility: juju >= 2.0
>
> I'm personally on the side of having charm *authors* talk about the features
> they want. Because then in juju-world we can enable/disable specific
> features based on them being requested, which makes charm authors get the
> features they need right. (e.g., if the charm doesn't say it needs
> leader-election, then it doesn't get leader tools exposed.)
>
> min-version, otoh, leads to people just setting it to the thing they are
> using, and doesn't give Juju a way to smartly enable/disable functionality.
> It also suffers from when we want to drop a feature that didn't turn out
> quite like what we thought it would.

Thanks John, +100 to all of this.