ariatosca-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ARIA-260) Send interface inputs as arguments to operations
Date Tue, 06 Jun 2017 19:17:18 GMT

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

ASF GitHub Bot commented on ARIA-260:
-------------------------------------

Github user tliron commented on a diff in the pull request:

    https://github.com/apache/incubator-ariatosca/pull/145#discussion_r120454702
  
    --- Diff: tests/end2end/test_nodecellar.py ---
    @@ -40,3 +40,21 @@ def _verify_deployed_service_in_storage(service_name, model_storage):
         assert service.name == service_name
         assert len(service.executions) == 0  # dry executions leave no traces
         assert len(service.nodes) == 10
    +    assert set(service.nodes['loadbalancer_host_1'].interfaces['Standard'].operations['create']
\
    --- End diff --
    
    I created a new tests/instantiation package and put them there for now.


> 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
>            Assignee: 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)

Mime
View raw message