Changing publishing mechanism to allow referencing context variables
* All previously published variables can be now access using '$.'
as in other places. E.g., if we had variable 'var1' in the context
we can use '$.var1' to access it in 'publish'.
* Action/workflow result can be referenced using "$.taskName.".
E.g, if task name is 'task0' and its action/workflow returned {x: y}
then 'x' can be referenced using '$.task0.x' in 'publish'.
* Fixed a lot of unit tests
* Fixed with-items implementation (part related to task output)
Reviewed: https:/ /review. openstack. org/149623 /git.openstack. org/cgit/ stackforge/ mistral/ commit/ ?id=93a33c169df d39c7c0449a82c9 9c88dc451aeb7f
Committed: https:/
Submitter: Jenkins
Branch: master
commit 93a33c169dfd39c 7c0449a82c99c88 dc451aeb7f
Author: Renat Akhmerov <email address hidden>
Date: Fri Jan 23 19:36:31 2015 +0600
Changing publishing mechanism to allow referencing context variables
* All previously published variables can be now access using '$.'
as in other places. E.g., if we had variable 'var1' in the context
we can use '$.var1' to access it in 'publish'.
* Action/workflow result can be referenced using "$.taskName.".
E.g, if task name is 'task0' and its action/workflow returned {x: y}
then 'x' can be referenced using '$.task0.x' in 'publish'.
* Fixed a lot of unit tests
* Fixed with-items implementation (part related to task output)
Change-Id: Ib7532572dd677b 517efd40a812cd3 633b5de756f
Closes-Bug: #1412635