Renat Akhmerov d9e734fa5b Remove environment data from task inbound context ... * It's redundant to keep environment data in task inbound context, it is immutable and we can always take it from workflow execution object which is more efficient from DB space consumption standpoint. The only case when it's allowed to modify data in a workflow environment is when we either resume or re-run a workflow and in this case we can change it for the whole workflow execution. Change-Id: I244c1768aaa306f8ad41084325107a40005d874c (cherry picked from commit bdf49b7193)		2016-09-29 05:03:49 +00:00
..
__init__.py	Added periodic events	2013-12-05 19:01:22 +04:00
action_manager.py	Merge "Add action context to all action executions"	2016-07-05 10:52:35 +00:00
actions.py	Fixed trivial issue in exception message	2016-07-29 16:44:52 +05:30
event_engine.py	Add event configuration for event trigger	2016-09-01 10:28:59 +12:00
expiration_policy.py	Avoid comparision between "None" type and "int" type.	2015-10-27 12:54:36 +05:30
periodic.py	Rename package mistral.engine.rpc to mistral.engine.rpc_backend	2016-07-14 15:15:50 +02:00
scheduler.py	Change execution mechanism for 'join' tasks	2016-09-07 13:18:18 +02:00
security.py	Fix for 'Cannot authenticate without an auth_url'	2016-08-30 04:23:48 -04:00
triggers.py	Add event trigger REST API	2016-09-13 22:39:36 +12:00
workbooks.py	Fix specification caching mechanism	2016-08-09 20:16:09 +07:00
workflows.py	Remove environment data from task inbound context	2016-09-29 05:03:49 +00:00