[OASIS Issue Tracker] (TOSCA-218) Make "valid_node_types" part of Capability metamodel not a property

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

    [ https://issues.oasis-open.org/browse/TOSCA-218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=58551#comment-58551 ] 

Matthew Rutkowski  commented on TOSCA-218:
------------------------------------------

The valid_node_types property was renamed to "valid_source_types" and promoted to the top-level Capability Type definition grammar.  

This was fixed in WD05, Rev05
The final grammar (with name change) appears in WD05, Rev06

> Make "valid_node_types" part of Capability metamodel not a property
> -------------------------------------------------------------------
>
>                 Key: TOSCA-218
>                 URL: https://issues.oasis-open.org/browse/TOSCA-218
>             Project: OASIS Topology and Orchestration Specification for Cloud Applications (TOSCA) TC
>          Issue Type: Improvement
>          Components: Profile-YAML
>    Affects Versions: CSD2
>            Reporter: Matthew Rutkowski 
>            Assignee: Matthew Rutkowski 
>             Fix For: CSD2
>
>
> Currently, "valid_node_types" is a property of just the  tosca.capabilities.Container.  However, we agreed long ago that this should be a top-level key of the CapabilityType grammar so that all Capabilities can declare the types of Nodes they accept "relationships" from (when needed).



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)