openstack
/
mistral
Code Issues Proposed changes
mistral/mistral/workflow
History
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 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-29 05:03:49 +00: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 Avoid storing workflow input in task inbound context 2016-09-26 09:28:27 +00:00
direct_workflow.py Avoid storing workflow input in task inbound context 2016-09-26 09:28:27 +00:00
lookup_utils.py Optimize the logic that check if 'join' task is allowed to start 2016-09-15 14:27:25 +03:00
reverse_workflow.py Optimize the logic that check if 'join' task is allowed to start 2016-09-15 14:27:25 +03: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