[OASIS Issue Tracker] (TOSCA-217) Add new simplified, single-line list notation / grammar for Requirement Def.

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

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

Paul Lipton  commented on TOSCA-217:
------------------------------------

Thomas may have a use case. 


> Add new simplified, single-line list notation / grammar for Requirement Def.
> ----------------------------------------------------------------------------
>
>                 Key: TOSCA-217
>                 URL: https://issues.oasis-open.org/browse/TOSCA-217
>             Project: OASIS Topology and Orchestration Specification for Cloud Applications (TOSCA) TC
>          Issue Type: New Feature
>          Components: Profile-YAML
>    Affects Versions: CSD2
>            Reporter: Matthew Rutkowski 
>            Assignee: Matthew Rutkowski 
>            Priority: Minor
>             Fix For: CSD2
>
>
> The current grammar for Requirement Def. is as follows:
> <requirement_name>: 
>   node: <node_type_or_template_name>
>   capability: <capability_type_or_template_name>
>   relationship: <relationship_type_or_template_name>
> The new notation would allow the a single-line, list notation for a very common case where only the 'tuple names (i.e., node, capability,  name are needed (no target_filter) as follows:
>       requirement: [ <node_name>, <capability_name>, <relationship_name> ]
> For example, the new notation would allow the following host requirement:
>       requirements:
>         - db_admin_console:
>             node: my_database 
>             capability: db_admin_endpoint
>             relationship: my_connection
> to be written more simple as:
>       requirements:
>         - db_admin_console: [ my_database, db_admin_endpoint, my_connection ]
> ------------
> Note: we may want to discuss ordering of list to put relationship in the 2nd entry in the list instead of the capability, whatever seems to be the most common use case (i.e., are relationships or capabilities needed more often when describing a requirement?).



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