Mistral actions design
This BP is an attempt to get together the most important design ideas regarding Mistral actions. The questions that it answers:
- How do we distinguish synchronous and asynchronous actions? What's the formal criteria?
- How does action obtain its result?
- In what form does action return a result?
- Does action need to have revert() method along with run() method?
- Does action need to have dry_run() method?
- How does action expose errors occurring during it's work?
- How would a complete Action interface look like?
- How do we treat action input parameters?
Please follow specification url for more complete information.
Blueprint information
- Status:
- Complete
- Approver:
- Renat Akhmerov
- Priority:
- High
- Drafter:
- Renat Akhmerov
- Direction:
- Approved
- Assignee:
- Renat Akhmerov
- Definition:
- Approved
- Series goal:
- None
- Implementation:
-
Implemented
- Milestone target:
- None
- Started by
- Renat Akhmerov
- Completed by
- Renat Akhmerov
Related branches
Related bugs
Sprints
Whiteboard
Gerrit topic: https:/
Addressed by: https:/
Working on 'mistral-
Addressed by: https:/
Working on "mistral-
Gerrit topic: https:/
Gerrit topic: https:/
Addressed by: https:/
Working on 'mistral-
Gerrit topic: https:/
Addressed by: https:/
Working on 'mistral-
Gerrit topic: https:/
Addressed by: https:/
Working on 'mistral-
Addressed by: https:/
Working on 'mistral-
Addressed by: https:/
BP mistral-
Addressed by: https:/
BP mistral-
Addressed by: https:/
BP mistral-
Addressed by: https:/
BP mistral-
