/actions v2 endpoint doesn't provide property 'is_system'
Bug #1373748 reported by
Renat Akhmerov
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Mistral |
Fix Released
|
Medium
|
Renat Akhmerov | ||
Bug Description
Currently there's no way to distinguish between system and ad-hoc actions looking at JSON provided by /actions endpoint.
| Changed in mistral: | |
| assignee: | nobody → Renat Akhmerov (rakhmerov) |
| Changed in mistral: | |
| importance: | Undecided → Medium |
| status: | New → Confirmed |
| Changed in mistral: | |
| milestone: | none → 0.1.1 |
| status: | Confirmed → In Progress |
| Changed in mistral: | |
| status: | In Progress → Fix Committed |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix merged to python-mistralclient (master) | #1 |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix merged to mistral (master) | #2 |
| Changed in mistral: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
Reviewed: https:/
Committed: https:/
Submitter: Jenkins
Branch: master
commit 12d334a34b3b436
Author: Nikolay Mahotkin <email address hidden>
Date: Thu Sep 25 15:44:05 2014 +0400
Fix 'is_system' property in action commands
Fixes-bug: #1373748
Change-Id: Ie699c5be0ace08