mirror of
https://github.com/coder/coder.git
synced 2026-09-24 15:04:27 +08:00
George K
6af0f4d698
This models restart as durable orchestration of existing stop and start workspace builds instead of adding a new restart transition. Keeping restart as two existing transitions preserves the current build/provisioner model. The child start build is created only after the parent stop build succeeds, rather than being inserted immediately in a pending state. That keeps `workspace_builds` aligned with actual provisioner-ready work and avoids introducing a second pending-build lifecycle that the provisioner and build acquisition paths would need to understand. Refs: https://linear.app/codercom/issue/PLAT-143
11 lines
391 B
SQL
11 lines
391 B
SQL
-- Enum additions to api_key_scope are intentionally not reversed
|
|
-- because Postgres cannot drop enum values safely.
|
|
|
|
DROP TABLE IF EXISTS workspace_build_orchestrations;
|
|
|
|
ALTER TABLE template_version_presets
|
|
DROP CONSTRAINT IF EXISTS template_version_presets_id_template_version_id_key;
|
|
|
|
ALTER TABLE workspace_builds
|
|
DROP CONSTRAINT IF EXISTS workspace_builds_id_workspace_id_key;
|