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/09/13 13:13:00 UTC

[jira] [Created] (ARIA-375) Built-in workflows terminology

Ran Ziv created ARIA-375:
----------------------------

             Summary: Built-in workflows terminology
                 Key: ARIA-375
                 URL: https://issues.apache.org/jira/browse/ARIA-375
             Project: AriaTosca
          Issue Type: Task
            Reporter: Ran Ziv
            Priority: Trivial


There are several workflows under the {{workflows/builtin}} package|https://github.com/apache/incubator-ariatosca/blob/0.1.1/aria/orchestrator/workflows/builtin/execute_operation.py] which aren't in fact TOSCA normative workflows - yet they are built-in in ARIA (i.e. don't require manual declaration by users as custom workflows, using the {{aria.Workflow}} policy type).

There might be room for a change in terminology (perhaps "core workflows" as opposed to "builtin"?).
Beyond that, it might be better not to have any non-normative TOSCA workflows be part of the services anyway - and instead have these workflows declared in {{aria-1.0.yaml}}, to be optional built-in custom workflows.




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)