Difference between revisions of "Mistral/Blueprints/ActionsDesign"
< Mistral | Blueprints
(Created page with "=== Mistral Actions === NOT FINISHED") |
(→Mistral Actions) |
||
| Line 1: | Line 1: | ||
=== Mistral Actions === | === Mistral Actions === | ||
| + | |||
| + | This BP describes the main requirements to how actions should be designed in Mistral in order to address flexibility and clarity of their usage. | ||
| + | |||
| + | The questions to answer are: | ||
| + | * 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? | ||
| + | |||
| + | |||
| + | |||
NOT FINISHED | NOT FINISHED | ||
Revision as of 07:19, 11 March 2014
Mistral Actions
This BP describes the main requirements to how actions should be designed in Mistral in order to address flexibility and clarity of their usage.
The questions to answer are:
- 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?
NOT FINISHED
