Allow env update on task re-run

Registered by Winson Chan on 2015-12-11

This is regarding the use case where a workflow execution failed because of environment related issues (i.e. endpoint unavailable, etc.). Endpoints and credentials can be passed on workflow invocation under the env param and then accessed by workflow tasks using the env() function. It is possible that the endpoint is replaced (i.e. different host/ip) as part of resolving the environment related issues or that the token passed as credential has expired. In these cases, the user will need to be able to update the env variables prior to re-run.

Blueprint information

Status:
Complete
Approver:
Renat Akhmerov
Priority:
Medium
Drafter:
Winson Chan
Direction:
Approved
Assignee:
Winson Chan
Definition:
Approved
Series goal:
Accepted for mitaka
Implementation:
Implemented
Milestone target:
milestone icon 2.0.0
Started by
Nikolay Makhotkin on 2015-12-16
Completed by
Renat Akhmerov on 2016-02-05

Related branches

Sprints

Whiteboard

Gerrit topic: https://review.openstack.org/#q,topic:mistral-rerun-update-env,n,z

Addressed by: https://review.openstack.org/256886
    Allow env update on task re-run

Gerrit topic: https://review.openstack.org/#q,topic:bp/mistral-rerun-update-env,n,z

Addressed by: https://review.openstack.org/259275
    Allow env update on resume and rerun workflows

Addressed by: https://review.openstack.org/259276
    Update REST API to support env update

Addressed by: https://review.openstack.org/260289
    Add options to update env for executions and tasks

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.