New feature for charmers - min-juju-version

[Ryan Beisner]

On Wed, Mar 23, 2016 at 1:03 PM, roger peppe <roger.peppe at canonical.com>
wrote:

> On 23 March 2016 at 15:06, David Ames <david.ames at canonical.com> wrote:
> > On 03/21/2016 06:54 PM, Stuart Bishop wrote:
> >>
> >> On 22 March 2016 at 11:42, Rick Harding <rick.harding at canonical.com>
> >> wrote:
> >>>
> >>> I believe that went out and is ok Stuart. The charmstore update is
> >>> deployed
> >>> and when you upload a multi-series charm to the charmstore it creates
> >>> separate charms that work on older clients. If you hit issues with that
> >>> please let me know.
> >>
> >>
> >> Its only fixed for charms served from the charm store. CI systems and
> >> such test branches, for example ensuring tests pass before uploading a
> >> release to the charm store. I suspect this is exactly what Ryan needs
> >> to do and why I mentioned the open bug. Unless 1.25 is updated to
> >> handle the different data types, CI systems will need to work around
> >> the issue by either roundtripping through the charm store (in a
> >> personal namespace to avoid mid air collisions) or munging
> >> metadata.yaml.
>
> ISTM that munging metadata.yaml could be a reasonable way
> to go here. It's not too hard. Here's a program you could use:
> http://play.golang.org/p/xl7yArJhtT
>
>
Indeed that is an option, and that approach would require additional work
on other tooling to enable metadata munging for 1.25.x use.  Such as:
 bundletester, amulet, mojo, juju-deployer.

Whereas, if it is addressed in `juju deploy` for 1.25.x, then it's
addressed in one place for every scenario that I've observed.

To summarize:
If we do nothing with regard to juju 1.25.x or the various tools, and if a
relevant charm grows a series list in metadata, a load of existing
validation and demo bundles will no longer be deployable with 1.25.x
because `juju deploy` on 1.25.x traces when receiving a list type as a
metadata series value.  These type of bundles often point at gh: and lp:
charm dev/feature branches, so the charm series metadata is as it is in the
dev charm's trunk (unmodified by the charm store).




> --
> Juju mailing list
> Juju at lists.ubuntu.com
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/juju
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/juju/attachments/20160323/3fd18c39/attachment.html>