Mistral

Deprecate requires keyword in DSL

Registered by Dmitri Zimine on 2014-06-04

We learned that using direct workflow defintion with on-success/on-error/on-finish is more natural than using dependancy-based definition with 'requires'. We also learned that mixing the two in the same worklfow is a disaster. Thus decided to drop support for 'dependency-based' workflows.
https://etherpad.openstack.org/p/mistral-post-POC-questions

in June: Desided to support various classes of workflows, but never mix the two classes in one. Marking as Superseeded by mistral-workflow-types

Blueprint information

Status:: Complete

Approver:: None

Priority:: Medium

Drafter:: Dmitri Zimine

Direction:: Needs approval

Assignee:: None

Definition:: Superseded

Series goal:: Accepted for juno

Implementation:: Blocked

Milestone target:: None

Started by: Renat Akhmerov on 2014-06-24

Completed by: Dmitri Zimine on 2014-08-14

Related branches

Related bugs

Sprints

Whiteboard

Gerrit topic: https://review.openstack.org/#q,topic:bp/deprecate-requires-in-dsl,n,z

Addressed by: https://review.openstack.org/98276
Refactor test_engine to not rely on start_task

Gerrit topic: https://review.openstack.org/#q,topic:mistral-workflow-start-task,n,z

(?)

Work Items

This blueprint contains Public information

Everyone can see this information.

Subscribers

No subscribers.