[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:all-tabpanel ]

Matthew Rutkowski  updated TOSCA-191:
-------------------------------------

              Summary: CSD02 - Document the “augmentation” behavior after relationship is selected in a requirement  (was: Document the “augmentation” behavior after relationship is selected in a requirement)
        Fix Version/s: CSD2
    Affects Version/s: CSD2
                           (was: CSD03)

> 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)