Repository navigation
chore: tasks: refactor existing API endpoints to use new data model #976
Description
Blocked by #948
Update existing tasks-related API endpoints to insert data into the new tables:
-
GET /api/experimental/tasks/feat(coderd): use task data model for list coder#20394 -
POST /api/experimental/tasks/feat(coderd): use task data model when creating a new task coder#20275 -
GET /api/experimental/tasks/{id}feat(coderd): use task data model when fetching a task coder#20380 -
DELETE /api/experimental/tasks/{id}feat(coderd): use new data model for task delete coder#20334 -
GET|POST /api/experimental/tasks/{send,logs}feat(coderd): use task data model for send/logs coder#20381 - Add a migration to update existing tasks to the new format chore(coderd/database/migrations): migrate tasks to new data model coder#20434
Activity
johnstcn commentedon Sep 25, 2025
Due to time constraints, we may not have the time to perform a migration.
Suggested approach:
EDIT: less finger-crossing necessary, as migration turned out to be feasible
61 remaining items
feat(coderd): use new data model for task delete (#20334)
feat(coderd): use task data model when fetching a task
feat(coderd): use task data model when fetching a task (#20380)
feat(coderd): use task data model for send/logs
feat(coderd): use task data model for send/logs (#20381)
feat(coderd): use task data model for list
feat(coderd): use task data model for list (#20394)
chore(codersdk): document TaskStatus and TaskState (#20441)
mafredri commentedon Oct 24, 2025
Backend is done, final frontend piece of the puzzle is almost done: coder/coder#20431
feat(site): use new task data model and endpoints (#20431)