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 <dewa...@cloudify.co> wrote:
> How would one define a property that was a list of maps, e.g.
>
> prop:
> - a: b
> - c: d
>
>
> -- DeWayne
>
