fix: undo drop of playbook_run_status

[yashmehrotra]

Error on aws

{"time":"2024-10-16T04:15:52.308735642Z","level":"ERROR+1","msg":"failed to apply schema migrations: applied 6 changes and then failed: drop enum type \"playbook_run_status\": pq: cannot drop type playbook_run_status because other objects depend on it"}

Seems like migration does not update column types ? we dont use that type anywhere but getting this from db

mission_control=# SELECT                                                                                     
    table_schema,
    table_name,
    column_name
FROM
    information_schema.columns
WHERE
    column_default LIKE '%playbook_run_status%';

-[ RECORD 1 ]+---------------------
table_schema | public
table_name   | playbook_run_actions
column_name  | status

Also, we should update the tool's version ? we are on a year old release and a new stable release was dropped 2 weeks ago, they added trigger support and function support as well

[adityathebe]

@yashmehrotra the original default for playbook_run_actions.status was the enum playbook_run_status but that was later removed.

We should probably alter the default in migration instead

ALTER TABLE playbook_run_actions
ALTER COLUMN status SET DEFAULT 'running';

[yashmehrotra]

@adityathebe I think we should try fixing it with tool version bump first and use alter command if that fails ?