ali 20c3408692 Add namespaces to Ad-Hoc actions ... added namespace for the actions, actions can have the same name if they are not in the same namespace, when executing an action, if an action with that name is not found in the workflow namespace or given namespace mistral will look for that action in the default namespace. * action base can only be in the same namespace,or in the default namespace. * Namespaces are not part of the mistral DSL. * The default namespace is an empty string ''. * all actions will be in a namespace, if not specified, they will be under default namespace Depends-On: I61acaed1658d291798e10229e81136259fcdb627 Change-Id: I07862e30adf28404ec70a473571a9213e53d8a08 Partially-Implements: blueprint create-and-run-workflows-within-a-namespace Signed-off-by: ali <ali.abdelal@nokia.com>		2020-01-07 08:10:53 +00:00
..
__init__.py	Add option to run actions locally on the engine	2017-04-27 20:02:27 +00:00
base.py	Migrate mistral to using the serialization code in mistral-lib	2018-07-23 12:55:41 +01:00
default_executor.py	Add namespaces to Ad-Hoc actions	2020-01-07 08:10:53 +00:00
executor_server.py	Make action heartbeats work for all executor types	2019-11-15 16:44:40 +07:00
remote_executor.py	Optimize sending result to parent workflow	2017-10-09 01:38:33 +00:00