[
https://issues.apache.org/jira/browse/ARIA-260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16035207#comment-16035207
]
ASF GitHub Bot commented on ARIA-260:
-------------------------------------
GitHub user tliron opened a pull request:
https://github.com/apache/incubator-ariatosca/pull/145
ARIA-260 Send interface inputs as arguments
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/apache/incubator-ariatosca
ARIA-260-send-interface-inputs
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-ariatosca/pull/145.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #145
----
commit a733be67b5c9770081d94c295c47803dbd7f3ef4
Author: Tal Liron <[email protected]>
Date: 2017-06-02T18:35:21Z
ARIA-260 Send interface inputs as arguments
----
> Send interface inputs as arguments to operations
> ------------------------------------------------
>
> 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)
