fix(crons): Remove db constraint from historical migrations for monit…

…or environment (#66265) These constraints are causing migrations to fail in getsentry, where we've set up the router to move these tables to a separate database.
getsentry · Mar 4, 2024 · 04dba78 · 04dba78
1 parent c6f37f5
commit 04dba78
Show file tree

Hide file tree

Showing 2 changed files with 6 additions and 2 deletions.
diff --git a/src/sentry/migrations/0001_squashed_0484_break_org_member_user_fk.py b/src/sentry/migrations/0001_squashed_0484_break_org_member_user_fk.py
@@ -9158,7 +9158,9 @@ class Migration(CheckedMigration):
                 (
                     "environment",
                     sentry.db.models.fields.foreignkey.FlexibleForeignKey(
-                        on_delete=django.db.models.deletion.CASCADE, to="sentry.Environment"
+                        on_delete=django.db.models.deletion.CASCADE,
+                        to="sentry.Environment",
+                        db_constraint=False,
                     ),
                 ),
                 (

diff --git a/src/sentry/migrations/0361_monitor_environment.py b/src/sentry/migrations/0361_monitor_environment.py
@@ -43,7 +43,9 @@ class Migration(CheckedMigration):
                 (
                     "environment",
                     sentry.db.models.fields.foreignkey.FlexibleForeignKey(
-                        on_delete=django.db.models.deletion.CASCADE, to="sentry.Environment"
+                        on_delete=django.db.models.deletion.CASCADE,
+                        to="sentry.Environment",
+                        db_constraint=False,
                     ),
                 ),
                 (