Determine revert args independently of execute args

Registered by Greg Hill on 2015-10-30

Taskflow uses the 'execute' method on each task to decide the argument mapping to send to both the 'execute' and 'revert' methods. This means that the 'revert' method cannot use arguments that are available in the engine 'storage' layer unless the 'execute' method also requires them. We have several use cases where we want to use a base task revert method that takes arguments from the storage layer, but most of our 'execute' methods do not need those arguments. We could just as easily store a separate argument mapping using the same logic for the revert method and use that to pass in the arguments to revert.

Blueprint information

Status:
Not started
Approver:
None
Priority:
Undefined
Drafter:
Greg Hill
Direction:
Needs approval
Assignee:
Greg Hill
Definition:
New
Series goal:
None
Implementation:
Unknown
Milestone target:
None

Related branches

Sprints

Whiteboard

Gerrit topic: https://review.openstack.org/#q,topic:bp/separate-revert-args,n,z

Addressed by: https://review.openstack.org/267188
    Separate execute and revert arg mapping (WIP)

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.