re-add migration

migrations_lockfile.txt

@@ -10,7 +10,7 @@ hybridcloud: 0016_add_control_cacheversion
 nodestore: 0002_nodestore_no_dictfield
 remote_subscriptions: 0003_drop_remote_subscription
 replays: 0004_index_together
-sentry: 0789_add_unique_constraint_to_rollbackorganization
+sentry: 0790_delete_dashboard_perms_col
 social_auth: 0002_default_auto_field
 uptime: 0017_unique_on_timeout
 workflow_engine: 0012_data_source_type_change

src/sentry/migrations/0790_delete_dashboard_perms_col.py

@@ -0,0 +1,42 @@
+# Generated by Django 5.1.1 on 2024-11-14 16:45
+
+from django.db import migrations
+
+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.
+    # 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 post deployment:
+    # - Large data migrations. Typically we want these to be run manually 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
+    #   run this outside deployments so that we don't block them. Note that while adding an index
+    #   is a schema change, it's completely safe to run the operation after the code has deployed.
+    # Once deployed, run these manually via: https://develop.sentry.dev/database-migrations/#migration-deployment
+
+    is_post_deployment = False
+
+    dependencies = [
+        ("sentry", "0789_add_unique_constraint_to_rollbackorganization"),
+    ]
+
+    operations = [
+        migrations.SeparateDatabaseAndState(
+            database_operations=[
+                migrations.RunSQL(
+                    """
+                    ALTER TABLE "sentry_dashboardpermissions" DROP COLUMN "is_creator_only_editable";
+                    """,
+                    reverse_sql="""
+                    ALTER TABLE "sentry_dashboardpermissions" ADD COLUMN "is_creator_only_editable" bool NULL;
+                    """,
+                    hints={"tables": ["sentry_dashboardpermissions"]},
+                )
+            ],
+            state_operations=[],
+        )
+    ]