From 421c93c4c8bca7aab9cc809e6c8ae60198b99346 Mon Sep 17 00:00:00 2001 From: Eric Radman Date: Fri, 18 Oct 2024 11:55:26 -0400 Subject: [PATCH] Add migration to set default alert selector In commits fc1e1f7a and e44fcdb a new Selector option was added to alerts, which may be "first", "min" or "max". This migration sets the default to "first" for existing alerts. --- .../1655999df5e3_default_alert_selector.py | 26 +++++++++++++++++++ 1 file changed, 26 insertions(+) create mode 100644 migrations/versions/1655999df5e3_default_alert_selector.py diff --git a/migrations/versions/1655999df5e3_default_alert_selector.py b/migrations/versions/1655999df5e3_default_alert_selector.py new file mode 100644 index 0000000000..28ca44abdc --- /dev/null +++ b/migrations/versions/1655999df5e3_default_alert_selector.py @@ -0,0 +1,26 @@ +"""set default alert selector + +Revision ID: 1655999df5e3 +Revises: 7205816877ec +Create Date: 2024-10-18 11:24:49 + +""" + +from alembic import op + +# revision identifiers, used by Alembic. +revision = '1655999df5e3' +down_revision = '7205816877ec' +branch_labels = None +depends_on = None + + +def upgrade(): + op.execute(""" + UPDATE alerts + SET options = jsonb_set(options, '{selector}', '"first"') + WHERE options->>'selector' IS NULL; + """) + +def downgrade(): + pass