Andras Kovi c08e44f17b Allow engine commands as task name ... A change for disabling some task names has introduced a massively backward incompatible behavior. E.g. even though there is a 'noop' engine command, the usual way of handling noop is in many cases is to create a task called the same. The other commands are not used that often but noop is massively present in currently deployed workflows and it is not possible to mitigate the error if the workflows are coming from 3rd parties. This change re-enables the usage of the engine commands as task names and adds documentation on why this is a useful feature. Change-Id: If90ee5f787e4587a25c156d12c7750407081bf0d Related-Change: https://review.openstack.org/#/c/535297		2018-07-19 14:23:18 +00:00
..
__init__.py	Initial commit for the new engine	2014-08-06 16:24:26 +07:00
base.py	Add a hacking rule for string interpolation at logging	2017-07-26 11:13:15 +00:00
commands.py	Allow engine commands as task name	2018-07-19 14:23:18 +00:00
data_flow.py	Do not copy workflow environment into subworkflows	2018-04-27 20:08:56 +07:00
direct_workflow.py	Allow engine commands as task name	2018-07-19 14:23:18 +00:00
lookup_utils.py	Optimize final workflow context evaluation with a batch request	2018-04-19 18:39:25 +07:00
reverse_workflow.py	Make "triggered_by" work in case of "join" tasks	2017-06-05 15:36:30 +00:00
states.py	add docs for states.	2018-07-12 08:50:52 +00:00
utils.py	Add more use of mistral-lib in mistral	2017-06-20 15:23:18 +00:00