From f36ad18cecc4ffb834961cf66818fb434f96a597 Mon Sep 17 00:00:00 2001 From: Katie Byers Date: Thu, 15 Aug 2024 15:38:23 -0700 Subject: [PATCH] add migration --- migrations_lockfile.txt | 2 +- ...data_use_one_to_one_field_for_grouphash.py | 38 +++++++++++++++++++ 2 files changed, 39 insertions(+), 1 deletion(-) create mode 100644 src/sentry/migrations/0751_grouphashmetadata_use_one_to_one_field_for_grouphash.py diff --git a/migrations_lockfile.txt b/migrations_lockfile.txt index 85379a6d31ac7..41c365a26bae2 100644 --- a/migrations_lockfile.txt +++ b/migrations_lockfile.txt @@ -10,6 +10,6 @@ hybridcloud: 0016_add_control_cacheversion nodestore: 0002_nodestore_no_dictfield remote_subscriptions: 0003_drop_remote_subscription replays: 0004_index_together -sentry: 0750_disable_member_invite_in_hybrid_cloud +sentry: 0751_grouphashmetadata_use_one_to_one_field_for_grouphash social_auth: 0002_default_auto_field uptime: 0007_update_detected_subscription_interval diff --git a/src/sentry/migrations/0751_grouphashmetadata_use_one_to_one_field_for_grouphash.py b/src/sentry/migrations/0751_grouphashmetadata_use_one_to_one_field_for_grouphash.py new file mode 100644 index 0000000000000..b00f2c0930810 --- /dev/null +++ b/src/sentry/migrations/0751_grouphashmetadata_use_one_to_one_field_for_grouphash.py @@ -0,0 +1,38 @@ +# Generated by Django 5.0.8 on 2024-08-15 22:46 + +import django.db.models.deletion +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. + # 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", "0750_disable_member_invite_in_hybrid_cloud"), + ] + + operations = [ + migrations.AlterField( + model_name="grouphashmetadata", + name="grouphash", + field=models.OneToOneField( + on_delete=django.db.models.deletion.CASCADE, + related_name="_metadata", + to="sentry.grouphash", + ), + ), + ]