Details
-
Story
-
Status: Open
-
Trivial
-
Resolution: Unresolved
-
None
-
None
-
None
-
None
Description
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.
Attachments
Issue Links
- relates to
-
-
- Open
-