Add action context to saved/asynchronous action executions
Bug #1596430 reported by
Xavier Hardy
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Mistral |
Fix Released
|
Medium
|
Xavier Hardy | ||
Bug Description
The action context is useful to send logs from an action execution to a user. It makes little sense to have the action context only present when the action execution is part of a task/workflow.
The action context must be at least present for asynchronous action executions and saved action executions.
| Changed in mistral: | |
| assignee: | nobody → Xavier Hardy (xavier-hardy) |
| Changed in mistral: | |
| milestone: | none → newton-2 |
| importance: | Undecided → Medium |
| status: | New → Confirmed |
| Changed in mistral: | |
| status: | Confirmed → In Progress |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix merged to mistral (master) | #1 |
| Changed in mistral: | |
| status: | In Progress → Fix Released |
Revision history for this message
| Doug Hellmann (doug-hellmann) wrote Fix included in openstack/mistral 3.0.0.0b2 | #2 |
To post a comment you must log in.
Reviewed: https:/
Committed: https:/
Submitter: Jenkins
Branch: master
commit 37a828bc62ae3d6
Author: Xavier Hardy <email address hidden>
Date: Wed Jun 29 12:09:20 2016 +0200
Add action context to all action executions
Saved and asynchronous action executions have a partial context
with only callback URL and the action execution ID, and other
fields set to None. Non-saved synchronous action executions have
a context with all fields set to None.
Closes-Bug: #1596430
Change-Id: I88c572ddc665e9