You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ariatosca.apache.org by "Ran Ziv (JIRA)" <ji...@apache.org> on 2017/05/19 09:21:04 UTC

[jira] [Commented] (ARIA-119) Syntax for executing a relationship operation on a specific edge (source/target)

    [ https://issues.apache.org/jira/browse/ARIA-119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16017110#comment-16017110 ] 

Ran Ziv commented on ARIA-119:
------------------------------

Since this JIRA issue had been created, it was decided that in fact it didn't make sense for this decision to be taken by the workflow author, but rather by the interface author, so instead the default for which edge to run the operation on is now specified in an {{_extensions}} section named {{relationship_edge}} ([Example|https://github.com/apache/incubator-ariatosca/blob/master/extensions/aria_extension_tosca/profiles/tosca-simple-1.0/interfaces.yaml#L67]).

This Issue, however, is still relevant - as the ability to override this for a specific operation implementation, as well as the syntax suggested, might still be useful.

> Syntax for executing a relationship operation on a specific edge (source/target)
> --------------------------------------------------------------------------------
>
>                 Key: ARIA-119
>                 URL: https://issues.apache.org/jira/browse/ARIA-119
>             Project: AriaTosca
>          Issue Type: Story
>            Reporter: Ran Ziv
>            Priority: Minor
>
> TOSCA doesn't define a syntax for specifying which edge (source/target) of the relationship a relationship operation should run on. At the moment, this will be determined by the workflow author.
> We could provided a syntax where the `implementation` field value would also hold the information for the edge, e.g.:
> {{implementation: script.sh @ SOURCE}}
> SOURCE and TARGET are already familiar "TOSCA constants", and the implementation field already has special syntax using the "@" sign so this seems to make the most sense.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)