"trust_id" must be attached to execution or trigger objects
Bug #1413124 reported by
Renat Akhmerov
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Mistral |
Fix Released
|
High
|
Nikolay Makhotkin | ||
Bug Description
Now "trust_id" is attached to workflow object. This is wrong because, for example, if Mistral needs to upload standard workflows (provided out of the box) it doesn't have any user auth info to build a trust. If we use Mistral admin credentials from config this is wrong as well because users will be able to run workflows with those credentials (for example, if I run "create_instance" workflow directly).
The suggestion is remove trust_id from workflow model and attach it to execution and trigger object. In case if execution is created by trigger its "trust_id" must be reused when creating execution object.
| Changed in mistral: | |
| status: | New → Confirmed |
| importance: | Undecided → High |
| assignee: | nobody → Nikolay Makhotkin (nmakhotkin) |
| milestone: | none → kilo-2 |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix proposed to mistral (master) | #1 |
| Changed in mistral: | |
| status: | Confirmed → In Progress |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix merged to mistral (master) | #2 |
| Changed in mistral: | |
| status: | In Progress → Fix Committed |
| Changed in mistral: | |
| status: | Fix Committed → Fix Released |
| Changed in mistral: | |
| milestone: | kilo-2 → 2015.1 |
To post a comment you must log in.
Fix proposed to branch: master
Review: https:/