migrations(crons): Add is_muted to MonitorEnvironment (#62115)

First phase of allowing monitor environments to be individually muted

Author: rjo100

migrations_lockfile.txt

@@ -9,5 +9,5 @@ feedback: 0003_feedback_add_env
 hybridcloud: 0009_make_user_id_optional_for_slug_reservation_replica
 nodestore: 0002_nodestore_no_dictfield
 replays: 0003_add_size_to_recording_segment
-sentry: 0623_increase_regression_fingerprint_length
+sentry: 0624_add_is_muted_monitorenvironment
 social_auth: 0002_default_auto_field

src/sentry/migrations/0624_add_is_muted_monitorenvironment.py

@@ -0,0 +1,46 @@
+# Generated by Django 3.2.23 on 2023-12-20 19:54
+
+from django.db import migrations, models
+
+from sentry.new_migrations.migrations import CheckedMigration
+
+
+class Migration(CheckedMigration):
+    # This flag is used to mark that a migration shouldn't be automatically run in production. For
+    # the most part, this should only be used for operations where it's safe to run the migration
+    # after your code has deployed. So this should not be used for most operations that alter the
+    # schema of a table.
+    # Here are some things that make sense to mark as dangerous:
+    # - Large data migrations. Typically we want these to be run manually by ops so that they can
+    #   be monitored and not block the deploy for a long period of time while they run.
+    # - Adding indexes to large tables. Since this can take a long time, we'd generally prefer to
+    #   have ops run this and not block the deploy. Note that while adding an index is a schema
+    #   change, it's completely safe to run the operation after the code has deployed.
+    is_dangerous = False
+
+    dependencies = [
+        ("sentry", "0623_increase_regression_fingerprint_length"),
+    ]
+
+    operations = [
+        migrations.SeparateDatabaseAndState(
+            database_operations=[
+                migrations.RunSQL(
+                    """
+                    ALTER TABLE "sentry_monitorenvironment" ADD COLUMN "is_muted" boolean NOT NULL DEFAULT FALSE;
+                    """,
+                    reverse_sql="""
+                    ALTER TABLE "sentry_monitorenvironment" DROP COLUMN "is_muted";
+                    """,
+                    hints={"tables": ["sentry_monitorenvironment"]},
+                ),
+            ],
+            state_operations=[
+                migrations.AddField(
+                    model_name="monitorenvironment",
+                    name="is_muted",
+                    field=models.BooleanField(default=False),
+                ),
+            ],
+        )
+    ]

src/sentry/monitors/models.py

@@ -558,6 +558,12 @@ class MonitorEnvironment(Model):
     check-ins. It is denormalized for simplicity.
     """
 
+    is_muted = models.BooleanField(default=False)
+    """
+    Monitor environment is operating normally but will not produce incidents or produce
+    occurrences into the issues platform.
+    """
+
     next_checkin = models.DateTimeField(null=True)
     """
     The expected time that the next-checkin will occur