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/11 14:29:10 UTC
[jira] [Updated] (ARIA-246) Built-in workflows not appear on
workflows list
[ https://issues.apache.org/jira/browse/ARIA-246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ran Ziv updated ARIA-246:
-------------------------
Description:
The built-in workflows are not stored on the service model's {{workflow}} field.
This can make sense in some ways, but can also cause awkward behavior, such as having an empty list returned when listing workflows in the CLI for a service which has no custom workflows.
It might be better to partially or fully push the built-in workflows into the service model's {{workflows}} field for it to be more whole.
This could also simplify some code in {{WorkflowRunner}} as there'd be no need to separate the cases of custom and built-in workflows anymore (except for, possibly, when referring to the workflow implementation)
was:
The built-in workflows are not stored on the service model's {{workflow}} field.
This can make sense in some ways, but can also cause awkward behavior, such as having an empty list returned when listing workflows in the CLI for a service which has no custom workflows.
It might be better to partially or fully push the built-in workflows into the service model's {{workflows}} field for it to be more whole.
> Built-in workflows not appear on workflows list
> -----------------------------------------------
>
> Key: ARIA-246
> URL: https://issues.apache.org/jira/browse/ARIA-246
> Project: AriaTosca
> Issue Type: Story
> Reporter: Ran Ziv
> Priority: Trivial
>
> The built-in workflows are not stored on the service model's {{workflow}} field.
> This can make sense in some ways, but can also cause awkward behavior, such as having an empty list returned when listing workflows in the CLI for a service which has no custom workflows.
> It might be better to partially or fully push the built-in workflows into the service model's {{workflows}} field for it to be more whole.
> This could also simplify some code in {{WorkflowRunner}} as there'd be no need to separate the cases of custom and built-in workflows anymore (except for, possibly, when referring to the workflow implementation)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)