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
..
rpc_backend	Using sys.exit(main()) instead of main()	2016-09-26 10:52:42 +07:00
__init__.py	Renaming "engine1" to "engine"	2015-04-09 17:47:36 +06:00
action_handler.py	Using count() instead of all() for getting incompleted tasks	2016-09-13 12:44:25 +03:00
actions.py	Merge "Change execution mechanism for 'join' tasks"	2016-09-08 10:10:32 +00:00
base.py	Merge "Avoid storing workflow input in task inbound context"	2016-09-22 04:36:17 +00:00
default_engine.py	Add a way to save action executions that run synchronously	2016-10-05 11:26:25 +00:00
default_executor.py	Executor fails actions if they are redelivered	2016-07-21 15:30:15 +02:00
dispatcher.py	Change execution mechanism for 'join' tasks	2016-09-07 13:18:18 +02:00
policies.py	Avoid storing workflow input in task inbound context	2016-09-21 13:32:44 +03:00
task_handler.py	Delete all necessary delayed calls on WF stop	2016-09-25 11:40:39 +03:00
tasks.py	Remove environment data from task inbound context	2016-09-26 14:50:10 +03:00
utils.py	Refactoring workflow handler	2016-06-07 18:38:38 +07:00
workflow_handler.py	Delete all necessary delayed calls on WF stop	2016-09-25 11:40:39 +03:00
workflows.py	Publish/output in case of task/workflow failure	2016-10-10 10:00:48 +02:00