Get rid of TaskResultProxy class that provides access to task result

Registered by Renat Akhmerov

In order to access task result we now can use syntax:

my_task:
  publish:
    my_var: $.my_task

But as of Mitaka this syntax has been deprecated and we now should get rid of all internal machinery that implements it because it creates a number of barriers for overall architectural improvements.

The recommended way to use task result (and other properties of task) is using "task" YAQL function. Example:

my_task:
  publish:
    my_var: task(my_task).result

Blueprint information

Status:
Complete
Approver:
Renat Akhmerov
Priority:
Medium
Drafter:
Renat Akhmerov
Direction:
Approved
Assignee:
Renat Akhmerov
Definition:
Approved
Series goal:
Accepted for newton
Implementation:
Implemented
Milestone target:
milestone icon newton-1
Started by
Renat Akhmerov
Completed by
Renat Akhmerov

Related branches

Sprints

Whiteboard

Gerrit topic: https://review.openstack.org/#q,topic:bp/mistral-remove-task-result-proxies,n,z

Addressed by: https://review.openstack.org/301538
    Getting rid of task result proxies in workflow context

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.