Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id D7E89200C79 for ; Fri, 19 May 2017 11:21:11 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id D5234160BD1; Fri, 19 May 2017 09:21:11 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 27662160BBE for ; Fri, 19 May 2017 11:21:11 +0200 (CEST) Received: (qmail 50673 invoked by uid 500); 19 May 2017 09:21:10 -0000 Mailing-List: contact issues-help@ariatosca.incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ariatosca.incubator.apache.org Delivered-To: mailing list issues@ariatosca.incubator.apache.org Received: (qmail 50664 invoked by uid 99); 19 May 2017 09:21:10 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 19 May 2017 09:21:10 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id F0864180692 for ; Fri, 19 May 2017 09:21:09 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -99.201 X-Spam-Level: X-Spam-Status: No, score=-99.201 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id fT1ci5UGeuiX for ; Fri, 19 May 2017 09:21:07 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id 984425FD8E for ; Fri, 19 May 2017 09:21:05 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 09ACDE0D49 for ; Fri, 19 May 2017 09:21:05 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 5830221B5B for ; Fri, 19 May 2017 09:21:04 +0000 (UTC) Date: Fri, 19 May 2017 09:21:04 +0000 (UTC) From: "Ran Ziv (JIRA)" To: issues@ariatosca.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (ARIA-119) Syntax for executing a relationship operation on a specific edge (source/target) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Fri, 19 May 2017 09:21:12 -0000 [ 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)