[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [tosca] TOSCA property/attribute functions and entity name and type uniqueness
Hi, I agree with you. The problem comes from the matching being done on the capability type, not name.
I can only repeat the example below. NodeB calls the capability âRealâ nodeC calls it Deal. The âpropertyInCapabilityNameâ
exists in both since itâs decided by the capability type not the capability name. But I cannot get to the property in both cases, since I must use the capability name in the get_property path. It would be good if I could also use the capability type as an alternative to the name to solve this problem. BR, /Calin From: <tosca@lists.oasis-open.org> on behalf of Tal Liron <tliron@redhat.com> On Fri, Sep 13, 2019 at 11:38 AM Calin Curescu <calin.curescu@ericsson.com> wrote:
My understanding is that get_property uses the capability name, not the capability
type name. And that name should be unique in the node type. E.g.: MyNodeType: capabilities: myCapabilityName: type: MyCapabilityTypeName { get_property: [
myNodeTemplateName, CAPABILITY, myCapabilityName, propertyInCapabilityName ] } |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]