brooklyn-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mike Zaccardo <mike.zacca...@cloudsoftcorp.com>
Subject Re: Creating a wrapper application for camp plans
Date Mon, 09 Nov 2015 15:29:38 GMT
+1 I ran into this when developing BDP and found it odd

On Mon, Nov 9, 2015, 01:57 John McCabe <john@johnmccabe.net> wrote:

> Much more concise, +1
>
> On Mon, 9 Nov 2015 at 09:33 Mark McKenna <mark.mckenna@cloudsoftcorp.com>
> wrote:
>
> > +1
> >
> > On Fri, 6 Nov 2015, 16:51 Svetoslav Neykov <
> > svetoslav.neykov@cloudsoftcorp.com> wrote:
> >
> > > Hi devs,
> > >
> > > I propose that we change the rules for creating a wapper application
> for
> > > CAMP plans. There's an unexpected side effect presently where pointing
> > to a
> > > catalog item and giving a top-level name to the plan will prevent
> > > unwrapping. It's surprising to users and even more so because it wasn't
> > the
> > > case a few months ago.
> > >
> > > For example the following catalog item:
> > >
> > > brooklyn.catalog:
> > >   id: simpleApp
> > >   version: 1.0
> > >    displayName: Simple App
> > >    itemType: template
> > >   item:
> > >     services:
> > >     - type: my-simple-app
> > >
> > > when started in the Application Wizard and given a name, equivalent to
> > the
> > > following plan:
> > >
> > > name: My App
> > > services:
> > >   - type: "simpleApp:1.0"
> > >
> > > will result in this hierarchy:
> > >
> > > * My App (BasicApplication)
> > >     * Simple App (my-simple-app)
> > >
> > > I propose that we change the logic such that the root level name will
> > > overwrite the child's name, so the hierarchy becomes:
> > >
> > >  * My App (my-simple-app)
> > >
> > >
> > > There's a PR opened for this change at
> > > https://github.com/apache/incubator-brooklyn/pull/1007.
> > >
> > > Svet.
> > >
> > >
> > >
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message