[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [tosca] key_schema in TOSCA 1.3?
Hi, I think this is a well-known usage of how to do pair definition in a list, so we donât need to have it in the spec.
BR, /C From: <tosca@lists.oasis-open.org> on behalf of Tal Liron <tliron@redhat.com> Thanks everybody for the discussion and quick decision! As an addendum, I'll just point out there is a workaround for cases where you need to send a map with arbitrary keys to an external system. Just use a list of entries: data_types: MyEntry: Key: MyKeyType Value: MyValueType node_types: MyNode: properties: my_fake_map: type: list entry_schema: MyEntry The one caveat is that TOSCA would not be able to verify the uniqueness of keys, but at least there is a functional solution. Is it worth pointing this out in the spec to preempt questions about the key_schema limitation? On Mon, Sep 16, 2019 at 4:15 PM Chris Lauwers <lauwers@ubicity.com> wrote:
|
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]