[OASIS Issue Tracker] (TOSCA-191) CSD02 - Document the “augmentation” behavior after relationship is selected in a requirement

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

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

Matthew Rutkowski  commented on TOSCA-191:
------------------------------------------

Fixed YAML issues so the text now reads as such:

  ClientNode:
    derived_from: SoftwareComponent
    properties:
      # omitted here for sake of brevity
    requirements:
      - server: 
          node: ServerNode  
          relationship:	
            type: ConnectsTo
            # Augment resulting Relationship’s interfaces by providing inputs
            interfaces:
              Configure:
                inputs: 
                 targ_notify_port: { get_attribute: [ TARGET, notification_port ] }
                # other operation definitions omitted here for sake of brevity

HOWEVER, the "inputs" for all methods of the interface are still at the same level as the method names.  This seems odd, but would require another keyname to logically separate method names from the "inputs" keyword.

> CSD02 - Document the “augmentation” behavior after relationship is selected in a requirement
> --------------------------------------------------------------------------------------------
>
>                 Key: TOSCA-191
>                 URL: https://issues.oasis-open.org/browse/TOSCA-191
>             Project: OASIS Topology and Orchestration Specification for Cloud Applications (TOSCA) TC
>          Issue Type: Task
>          Components: Profile-YAML
>    Affects Versions: CSD2
>            Reporter: Matthew Rutkowski 
>            Assignee: Matthew Rutkowski 
>             Fix For: CSD2
>
>
> Need to document how augmentation of requirements works as a special section under Requirement definition grammar.
> An example in Section 17 shows this:
> ------
>  requirements:
>       - server: ServerNode
>         relationship: ConnectsTo
>         # MUSTFIX: Document that the following statements (as a general facilty) can augment a requirement 
>         # (relationship) that was identified/instantiated by the previous 2 lines.
>         # Specifically, in this example, the following augment resulting Relationship’s "interfaces" keyword
>         interfaces:
>           Configure:
>             inputs: 
>             targ_notify_port: { get_attribute: { [ TARGET, notification_port ] } }
>             # other operation definitions omitted here for sake of brevity



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