Skip to content

hotfix: allow 'reaped' status in resources_status_check (migration 024) #67

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
mastermanas805 merged 1 commit into from
May 13, 2026
Merged

hotfix: allow 'reaped' status in resources_status_check (migration 024) #67

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 5 additions & 1 deletion internal/db/migrations/024_resources_paused_status.sql
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -20,10 +20,14 @@
-- production schemas (where it was implicit). After the drop the new
-- constraint is added that includes 'paused' as a permitted value.

-- `reaped` is a legacy status produced by a prior worker cleanup job — ~220
-- rows in prod carry it. Keep it in the allowed set so this migration is
-- non-destructive; collapsing it into 'deleted' would erase the historical
-- distinction between worker-reaped and user-deleted resources.
ALTER TABLE resources DROP CONSTRAINT IF EXISTS resources_status_check;
ALTER TABLE resources
ADD CONSTRAINT resources_status_check
CHECK (status IN ('active', 'paused', 'expired', 'deleted'));
CHECK (status IN ('active', 'paused', 'expired', 'deleted', 'reaped'));

ALTER TABLE resources ADD COLUMN IF NOT EXISTS paused_at TIMESTAMPTZ;

Expand Down