ok good. that what ive been using. i know all keys its ok.
On Oct 10, 2017 11:22 AM, "Tal Liron" <[email protected]> wrote:
> No, sorry, copy-paste error. Correction
>
> data_types:
> Element:
> properties:
> a: { type: string, required: false }
> c: { type: string, required: false }
> e: { type: string, required: false }
>
> On Tue, Oct 10, 2017 at 11:15 AM, DeWayne Filppi <[email protected]>
> wrote:
>
> > Really? Two layers of properties?
> >
> > On Tue, Oct 10, 2017 at 11:10 AM, Tal Liron <[email protected]> wrote:
> >
> > > You did not mention any error in this thread.
> > >
> > > The only other option I can think of is to define all the keys
> explicitly
> > > as not required. This means you need to know the possible keys in
> > advance.
> > > Example:
> > >
> > > data_types:
> > > Element:
> > > properties:
> > > data:
> > > properties:
> > > a: { type: string, required: false }
> > > c: { type: string, required: false }
> > > e: { type: string, required: false }
> > >
> > > On Tue, Oct 10, 2017 at 11:06 AM, DeWayne Filppi <[email protected]>
> > > wrote:
> > >
> > > > Doesn't quite do it. The inability to describe this may be causing
> the
> > > > error I recently mentioned.
> > > >
> > > > I'm looking for:
> > > >
> > > > prop:
> > > > - a: b
> > > > - c: d
> > > >
> > > > *not*
> > > >
> > > > prop:
> > > > - {data: {a:b}}
> > > > - {data { c:d))
> > > >
> > > > The Cloudify plugin I'm trying to reuse requires the first form.
> > > >
> > > > DeWayne
> > > >
> > > > On Mon, Oct 9, 2017 at 9:00 AM, Tal Liron <[email protected]> wrote:
> > > >
> > > > > It's an interesting problem, and the solution is clumsy due to the
> > odd
> > > > way
> > > > > TOSCA defines entry schema. I see no choice but to add an extra
> > nesting
> > > > > property. Something like this:
> > > > >
> > > > > data_types:
> > > > > Element:
> > > > > properties:
> > > > > data:
> > > > > type: map
> > > > > entry_schema: string
> > > > >
> > > > > node_types:
> > > > > MyNode:
> > > > > properties:
> > > > > my_property:
> > > > > type: list
> > > > > entry_schema: Element
> > > > >
> > > > > topology_template:
> > > > > node_templates:
> > > > > my_node:
> > > > > type: MyNode
> > > > > properties:
> > > > > my_property:
> > > > > - {data: {a: b}}
> > > > > - {data: {c: d}}
> > > > > - {data: {e: f, g: h, i: j}}
> > > > >
> > > > >
> > > > > On Fri, Oct 6, 2017 at 5:50 PM, DeWayne Filppi <
> [email protected]>
> > > > > wrote:
> > > > >
> > > > > > How would one define a property that was a list of maps, e.g.
> > > > > >
> > > > > > prop:
> > > > > > - a: b
> > > > > > - c: d
> > > > > >
> > > > > >
> > > > > > -- DeWayne
> > > > > >
> > > > >
> > > >
> > >
> >
>
