|
@@ -0,0 +1,36 @@
|
|
|
+# Generated by Django 5.0.2 on 2024-03-18 23:08
|
|
|
+
|
|
|
+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 = True
|
|
|
+
|
|
|
+ dependencies = [
|
|
|
+ ("sentry", "0675_dashboard_widget_query_rename_priority_sort_to_trends"),
|
|
|
+ ]
|
|
|
+
|
|
|
+ operations = [
|
|
|
+ migrations.AlterField(
|
|
|
+ model_name="apitoken",
|
|
|
+ name="hashed_refresh_token",
|
|
|
+ field=models.CharField(max_length=128, null=True, unique=True),
|
|
|
+ ),
|
|
|
+ migrations.AlterField(
|
|
|
+ model_name="apitoken",
|
|
|
+ name="hashed_token",
|
|
|
+ field=models.CharField(max_length=128, null=True, unique=True),
|
|
|
+ ),
|
|
|
+ ]
|