ref: make organizationmemberteam is_active db default true (#92064)

This field is never set to False. In production i've checked, and we
have 0 rows where `is_active` is False
[here](https://redash.getsentry.net/queries/8899/source). i'd like to
remove this field, and as a first step we're going to make it
`db_default=True` in the database. following

https://develop.sentry.dev/backend/application-domains/database-migrations/#deleting-columns

Author: JoshFerge

migrations_lockfile.txt

@@ -21,7 +21,7 @@ nodestore: 0001_squashed_0002_nodestore_no_dictfield
 
 replays: 0001_squashed_0005_drop_replay_index
 
-sentry: 0909_django_array_field_not_release
+sentry: 0910_make_organizationmemberteam_is_active_default
 
 social_auth: 0001_squashed_0002_default_auto_field
 

src/sentry/migrations/0910_make_organizationmemberteam_is_active_default.py

@@ -0,0 +1,33 @@
+# Generated by Django 5.2.1 on 2025-05-21 20:55
+
+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", "0909_django_array_field_not_release"),
+    ]
+
+    operations = [
+        migrations.AlterField(
+            model_name="organizationmemberteam",
+            name="is_active",
+            field=models.BooleanField(db_default=True),
+        ),
+    ]

src/sentry/models/organizationmemberteam.py

@@ -31,7 +31,7 @@ class OrganizationMemberTeam(ReplicatedRegionModel):
     organizationmember = FlexibleForeignKey("sentry.OrganizationMember")
     # an inactive membership simply removes the team from the default list
     # but still allows them to re-join without request
-    is_active = models.BooleanField(default=True)
+    is_active = models.BooleanField(db_default=True)
     role = models.CharField(max_length=32, null=True, blank=True)
 
     class Meta: