mistral/mistral/tests/resources
Renat Akhmerov 4a88302f49 Getting rid of task result proxies in workflow context
* Task result proxies were needed to be able to access
  task result as $.task_name. But this was deprecated in Mitaka
  in favor of using task() YAQL function. So it's time to get
  rid of complicated internal machinery before making further
  improvements

Change-Id: I9b8c1c9ac6e9561c6aa66151011ae2f7d906179a
Implements: blueprint mistral-remove-task-result-proxies
2016-04-05 17:47:47 +07:00
..
openstack Getting rid of task result proxies in workflow context 2016-04-05 17:47:47 +07:00
workbook/v2 Add semantics validation of direct workflow 'join' tasks 2015-09-18 13:10:37 +03:00
action_v2.yaml Changing YAQL syntax delimeters 2015-02-20 15:40:24 +03:00
wb_v1.yaml Removing left v1 related stuff (resources, DSL specs) 2015-04-08 17:10:22 +06:00
wb_v2.yaml Getting rid of task result proxies in workflow context 2016-04-05 17:47:47 +07:00
wf_action_ex_concurrency.yaml Fix concurrency issues by using READ_COMMITTED 2015-12-09 08:01:38 +00:00
wf_task_ex_concurrency.yaml Fix concurrency issues by using READ_COMMITTED 2015-12-09 08:01:38 +00:00
wf_v2.yaml Getting rid of task result proxies in workflow context 2016-04-05 17:47:47 +07:00