You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ariatosca.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2017/04/02 08:46:41 UTC

[jira] [Commented] (ARIA-134) Service.workflows field is not populated

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

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

Github user ran-z commented on a diff in the pull request:

    https://github.com/apache/incubator-ariatosca/pull/91#discussion_r109303723
  
    --- Diff: extensions/aria_extension_tosca/simple_v1_0/modeling/__init__.py ---
    @@ -446,6 +451,29 @@ def get(name):
         return model
     
     
    +def create_workflow_operation_template_model(context, service_template, policy):
    +    model = OperationTemplate(name=policy._name,
    --- End diff --
    
    Do we want workflows to be modeled as OperationTemplates?
    There are indeed many similarities though some fields don't really apply, e.g. `retry_interval`; What do you think?


> Service.workflows field is not populated
> ----------------------------------------
>
>                 Key: ARIA-134
>                 URL: https://issues.apache.org/jira/browse/ARIA-134
>             Project: AriaTosca
>          Issue Type: Bug
>            Reporter: Ran Ziv
>            Assignee: Tal Liron
>
> Service.workflows field is not populated
> It should be populated with policies whose role is set to Workflow



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