Ivan A. Melnikov 2fb146a994 Storage: restore injected data on resumption ...

In storage we now use single task for injector (we look it up by name)
and we restore result mapping for that task in constructor if there
is one in flow detail we are given. This has visible effect
of injected data staying in storage after resumption.

Closes-bug: #1240931
Change-Id: I2e8fb2c4b5cca769d36f578a934119db4a530f5c

2013-10-18 10:50:24 +04:00

..

engines

Remove task_action state checks

2013-10-16 20:05:17 -07:00

examples

Remove incorrect comment

2013-10-17 08:43:50 -07:00

jobs

Move toward python 3/2 compatible metaclass

2013-10-09 17:39:05 -07:00

listeners

Move toward python 3/2 compatible metaclass

2013-10-09 17:39:05 -07:00

openstack

Update oslo and bring py3kcompat in

2013-10-17 11:44:33 +04:00

patterns

Remove uuid from taskflow.flow.Flow

2013-10-15 10:52:05 +04:00

persistence

Use py3kcompat.urlutils from oslo instead of six.urllib_parse

2013-10-17 11:44:36 +04:00

tests

Storage: restore injected data on resumption

2013-10-18 10:50:24 +04:00

utils

Add debug logging showing what is flattened

2013-10-17 11:11:54 -07:00

__init__.py

Continue on getting ready for the memory impl. to be useful.

2013-05-12 14:45:24 -07:00

exceptions.py

Validate each flow state change

2013-10-07 16:46:02 +04:00

flow.py

Remove uuid from taskflow.flow.Flow

2013-10-15 10:52:05 +04:00

states.py

Remove task_action state checks

2013-10-16 20:05:17 -07:00

storage.py

Storage: restore injected data on resumption

2013-10-18 10:50:24 +04:00

task.py

Add more comments to flow/task

2013-10-12 22:47:35 -07:00

test.py

Add a flow flattening util

2013-09-20 12:41:57 +04:00