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/25 14:16:04 UTC

[jira] [Commented] (ARIA-260) Send interface inputs as arguments

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

Ran Ziv commented on ARIA-260:
------------------------------

How do you mean exactly?
Currently, inputs passed to the operation from the workflow override those of the operation - If we were to merge these with interface ones as well, I'd expect the precedence to be as follows  - interface on the bottom, operation inputs in the template, operation inputs passed from the workflow (each one getting overridden by the one after it)

By the way, do we even store interface inputs on our model at the moment? I thought this hasn't been handled yet. 

> Send interface inputs as arguments
> ----------------------------------
>
>                 Key: ARIA-260
>                 URL: https://issues.apache.org/jira/browse/ARIA-260
>             Project: AriaTosca
>          Issue Type: Story
>            Reporter: Tal Liron
>
> We currently send all operation inputs as arguments to the task function.
> However, we are utterly ignoring interface inputs. The task function can of course retrieve them in complicated ways from the context, but it seems that for completion the interface inputs should be sent to the function in same way as operation inputs.



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