Istvan Imre 3f5092d7f4 Publish/output in case of task/workflow failure ... Currently it is not possible to provide any reasonable output in case of a task or workflow failure. Implementing this would greatly simplify error handling in workflows. This blueprint is a proposal to introduce two new attributes, publish-on-error for tasks and output-on-error for workflows for this purpose. Implements: blueprint mistral-publish-on-error Change-Id: Ib3a64971effb02390206dc6f993e772a51f8f237		2016-10-10 10:00:48 +02:00
..
__init__.py	Initial commit for the new engine	2014-08-06 16:24:26 +07:00
base.py	Remove environment data from task inbound context	2016-09-26 14:50:10 +03:00
commands.py	Towards non-locking model: adapt 'join' tasks to work w/o locks	2016-08-08 19:25:32 +07:00
data_flow.py	Publish/output in case of task/workflow failure	2016-10-10 10:00:48 +02:00
direct_workflow.py	Publish/output in case of task/workflow failure	2016-10-10 10:00:48 +02:00
lookup_utils.py	Publish/output in case of task/workflow failure	2016-10-10 10:00:48 +02:00
reverse_workflow.py	Publish/output in case of task/workflow failure	2016-10-10 10:00:48 +02:00
states.py	Add cancelled state to executions	2016-07-29 18:05:30 +00:00
utils.py	Optimize the logic that check if 'join' task is allowed to start	2016-09-15 14:27:25 +03:00
with_items.py	Towards non-locking model: make 'with-items' work w/o locks	2016-08-09 11:20:12 +07:00