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

[jira] [Created] (ARIA-226) Task, interface and operation inputs

Ran Ziv created ARIA-226:
----------------------------

             Summary: 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: Trivial


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)