Decouple Task definitions from TaskViews
This is a big job, and it entails building new models and structures to represent what a Task is, and how it is processed.
We need to remove the Task definition from the TaskViews, and have the taskviews as a means of building a view around a single task. We should then introduce more generic views which are not built around tasks (just return query data), and views which can use multiple tasks as part of their logic.
Potentially even moving this into its own versioned sub module like actions:
adjutant.actions.v1
adjutant.tasks.v1
This will further help as we try and move the whole workflow task layer into an async system.
Blueprint information
- Status:
- Not started
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- Adrian Turjak
- Direction:
- Needs approval
- Assignee:
- None
- Definition:
- New
- Series goal:
- None
- Implementation:
-
Unknown
- Milestone target:
- None
- Started by
- Completed by
Related branches
Related bugs
Sprints
Whiteboard
This should probably also include a 'str' definition of the task, which lets the API respond with a nice and easy representation of the task as a str to use in the GUI.
