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 40FBC200C6E for ; Mon, 8 May 2017 14:31:08 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 3FA70160BA5; Mon, 8 May 2017 12:31:08 +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 85D51160B99 for ; Mon, 8 May 2017 14:31:07 +0200 (CEST) Received: (qmail 70759 invoked by uid 500); 8 May 2017 12:31:06 -0000 Mailing-List: contact dev-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 dev@ariatosca.incubator.apache.org Received: (qmail 70748 invoked by uid 99); 8 May 2017 12:31:06 -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; Mon, 08 May 2017 12:31:06 +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 5E50B180A5A for ; Mon, 8 May 2017 12:31:06 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -100.002 X-Spam-Level: X-Spam-Status: No, score=-100.002 tagged_above=-999 required=6.31 tests=[RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id ImLbHsOTOckb for ; Mon, 8 May 2017 12:31:05 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id 0ACF15F1B3 for ; Mon, 8 May 2017 12:31: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 559ECE0272 for ; Mon, 8 May 2017 12:31:04 +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 0A3C221B53 for ; Mon, 8 May 2017 12:31:04 +0000 (UTC) Date: Mon, 8 May 2017 12:31:04 +0000 (UTC) From: "Ran Ziv (JIRA)" To: dev@ariatosca.incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (ARIA-226) Task, interface and operation inputs MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Mon, 08 May 2017 12:31:08 -0000 [ https://issues.apache.org/jira/browse/ARIA-226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ran Ziv updated ARIA-226: ------------------------- Priority: Minor (was: Trivial) > Task, interface and operation inputs > ------------------------------------ > > Key: ARIA-226 > URL: https://issues.apache.org/jira/browse/ARIA-226 > Project: AriaTosca > Issue Type: Story > Reporter: Ran Ziv > Priority: Minor > > Currently, the inputs passed into an operation function are the result of a merge between the Operation inputs (defined in the service-template for the operation) and the Task inputs (defined by the workflow author), with the latter overriding the former if necessary. > This is consistent with how service-template/service and workflow/execution inputs are handled, and uses the same mechanism. > However, in TOSCA there's also interface inputs (also provided in the service-template), which are currently not passed to the operation at all. > One way to handle this would be to treat interface inputs as another (the base-most) level, i.e. values which will be applied by default unless overridden by either the Operation inputs or the Task inputs. > Another option would be to treat all three inputs paths as separate, and provide the operation function with all three sets of inputs. -- This message was sent by Atlassian JIRA (v6.3.15#6346)