[
https://issues.apache.org/jira/browse/ARIA-83?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15899196#comment-15899196
]
Ran Ziv commented on ARIA-83:
-----------------------------
Built-in workflow policies and execution plugin's policy should actually not be
imported (breaks TOSCA).
They could still in principle be made into a YAML that gets auto-imported, but
possibly it'd just be better to handle those cases in code.
the plugin/workflow policy definitions still need to be moved to the location
specified, so this issue is still relevant.
> Store built-in YAMLs in TOSCA extension
> ---------------------------------------
>
> Key: ARIA-83
> URL: https://issues.apache.org/jira/browse/ARIA-83
> Project: AriaTosca
> Issue Type: Story
> Reporter: Ran Ziv
> Assignee: Tal Liron
>
> The built-in YAMLs (plugin/workflow policy definitions, built-in workflow
> policies, execution plugin's types and policy) should sit under the TOSCA
> extension to be easily importable.
> (This also includes first writing the execution plugin's types and policy)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
