Use a explicit state machine when running workflows
The current action engine runner uses an implicit state machine, this makes it difficult to read and understand. It would benefit from a explicit state machine with well defined transitions. This also is a good starting point to introduce a state machine type that can be used more extensively in taskflow (and elsewhere) as the concept/code gets flushed out (we have to start somewhere to get somewhere else, so this baby step seems like a good starting point, and one that is key to how taskflow runs workflows).
Blueprint information
- Status:
- Complete
- Approver:
- None
- Priority:
- Medium
- Drafter:
- Joshua Harlow
- Direction:
- Approved
- Assignee:
- Joshua Harlow
- Definition:
- Approved
- Series goal:
- Accepted for 0.4
- Implementation:
- Implemented
- Milestone target:
- None
- Started by
- Joshua Harlow
- Completed by
- Joshua Harlow
Related branches
Related bugs
Sprints
Whiteboard
Gerrit topic: https:/
Addressed by: https:/
Translate engine runner into a well defined state-machine
Gerrit topic: https:/
Addressed by: https:/
Ensure state machine can be frozen
Addressed by: https:/
Tweak engine iteration 'close-up shop' runtime path
Addressed by: https:/
Move parts of action engine tests to a subdirectory