It indeed should *not* be required. I just verified that it you are correct, and a match is not made if only the capability is specified without a node type/template.
This is a regression, because it used to work correctly. There is currently work in progress to refactor that mechanism, so I will add a test case to make sure the regression is fixed. See my test case and follow progress here: https://issues.apache.org/jira/browse/ARIA-174 On Tue, Jul 25, 2017 at 3:28 AM, Vaishnavi K.R <[email protected]> wrote: > Hi ARIA folks, > > > I had a look at the source code of ARIA on how the target node is > identified based on the requirement and capability information furnished in > the node template and its corresponding node type. But I find that only few > of the combinations are supported i.e., as per the TOSCA spec, in the > requirement section of a node template, the 'node' option is not mandatory, > but ARIA expects that to be present. > > > In my use-case, my node template has a requirement on a node which has a > particular capability. So I just specify the capability type in my node > template under the requirement section. As ARIA expects the 'node' option > to be present, this use-case fails. > > > So I wish to get clarified is there any specific reason for mandating the > 'node' option or if TOSCA spec compliance on this target identification > based on the capability name or type will be supported in the future > versions? > > > Thanks, > > /Vaish >
