[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] (TOSCA-196) Enhance "capabilities" section in nested templates
[ https://issues.oasis-open.org/browse/TOSCA-196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=50484#comment-50484 ] Matthew Rutkowski commented on TOSCA-196: ------------------------------------------ If we effectively create a nested template (which is essentially a virtual node type) it should have all the keynames / features of a node type (in this case capabilities). We do have capabilities, but it is not enough perhaps. We need to be able to point to a specific capability of a node within the template. > Enhance "capabilities" section in nested templates > -------------------------------------------------- > > Key: TOSCA-196 > URL: https://issues.oasis-open.org/browse/TOSCA-196 > Project: OASIS Topology and Orchestration Specification for Cloud Applications (TOSCA) TC > Issue Type: Improvement > Components: Profile-YAML > Reporter: Chris Lauwers > Priority: Minor > > The "capabilities" section in a nested template "exports" capabilities of individual node templates by specifying the names of those node templates whose capabilities need to be exposed. However, if a node template has multiple capabilities, there should be a mechanism to specify which of those capabilities should get exposed. -- This message was sent by Atlassian JIRA (v6.2.2#6258)
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]