No-op task

Registered by Renat Akhmerov

We should be able not to specify either 'action' or 'workflow' for a task. In this case the task, in fact, will be just a decision making point. For example, once we get 'join' done we can have multiple inbound tasks joined on another tasks where we don't need to call any actions/workflow but rather just need to understand what to do next.

Suggested syntax:

...
tasks:
  my_no_op_task:
    on-complete:
      - my_next_task: $.my_ctx_var = 10

Blueprint information

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

Related branches

Sprints

Whiteboard

Gerrit topic: https://review.openstack.org/#q,topic:bp/mistral-direct-workflow-join-control,n,z

Addressed by: https://review.openstack.org/138975
    Adding "std.noop" action (can be useful for testing)

Gerrit topic: https://review.openstack.org/#q,topic:bp/mistral-no-op-task,n,z

Addressed by: https://review.openstack.org/143666
    Implementing "no-op" task

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.