467f60af09
* Made workflow execution creation idempotent. We can now pass an execution ID which is used when creating a new execution object. If the object with this ID doesn't exist, then a new execution is created and this ID is assigned to, and also the corresponding workflow gets started normally. If the object exists then the endpoint just returns properties of this object in JSON w/o starting the workflow. If an execution ID is not passed then the endpoint works as before, so it is backwards compatible with the previous version. * Added unit tests to check all possible logic branches depending on whether we passed an execution ID. * Had to add "wf_ex_id" paramter to the "start_workflow" method of the Engine API and fix all relevant calls. * Other minor style changes. Implements blueprint: mistral-idempotent-execution-create Change-Id: I1f650efbd23b00298a30e16893ca4f18d87c99b3 |
||
|---|---|---|
| .. | ||
| kombu | ||
| oslo | ||
| __init__.py | ||
| base.py | ||
| clients.py | ||