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:23:04 UTC
[jira] [Created] (ARIA-245) Dry execution of operations
Ran Ziv created ARIA-245:
----------------------------
Summary: Dry execution of operations
Key: ARIA-245
URL: https://issues.apache.org/jira/browse/ARIA-245
Project: AriaTosca
Issue Type: Story
Reporter: Ran Ziv
Priority: Trivial
It is currently possible to run a dry execution of a workflow using the {{DryExecutor}}. This execution will behave exactly like a real execution, including validating the execution inputs, building the workflow graph, and (dry-)executing the tasks in order.
However, the operations themselves don't actually get called, and thus the dry run isn't "complete". Plugins might want to have their own output for dry execution of operations.
Therefore, it might be a good idea to have a standard plugin policy property which a plugin could override to declare that it supports dry execution of operations - in which case, the dry executor would actually call the operation, providing a flag describing that it's meant to only dry-run.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)