feat(cells) Add date_updated to organizationmapping v2 (#103915)

Redo this change as it was reverted due to gaps in the control silo
deployment pipeline that didn't run migrations. This migration will have
run in development environment, and once the control silo migration
pipeline is fixed, I'll get a new migration number and use a
`SeparateDatabaseAndState` migration to handle this scenario.

Reapply "feat(cells) Add date_updated to organizationmapping (#103772)"

This reverts commit 94e744c.

Refs INFRENG-172

Author: markstory

migrations_lockfile.txt

@@ -31,7 +31,7 @@ releases: 0004_cleanup_failed_safe_deletes
 
 replays: 0006_add_bulk_delete_job
 
-sentry: 1008_loosen_unique_title_contraint
+sentry: 1009_add_date_updated_to_organizationmapping
 
 social_auth: 0003_social_auth_json_field
 

src/sentry/migrations/1009_add_date_updated_to_organizationmapping.py

@@ -0,0 +1,48 @@
+# Generated by Django 5.2.8 on 2025-11-20 21:13
+
+import django.db.models.functions
+from django.db import migrations, models
+
+from sentry.new_migrations.migrations import CheckedMigration
+from sentry.new_migrations.monkey.special import SafeRunSQL
+
+
+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", "1008_loosen_unique_title_contraint"),
+    ]
+
+    operations = [
+        # This migration had to be reverted after it was merged and ran in some environments.
+        # Clean up the previous attempt and try again
+        SafeRunSQL(
+            sql="""
+            ALTER TABLE "sentry_organizationmapping" DROP COLUMN IF EXISTS "date_updated";
+            """,
+            reverse_sql="",
+            hints={"tables": ["sentry_organizationmapping"]},
+        ),
+        migrations.AddField(
+            model_name="organizationmapping",
+            name="date_updated",
+            field=models.DateTimeField(
+                db_default=django.db.models.functions.Now(),
+                auto_now=True,
+                db_index=True,
+            ),
+        ),
+    ]

src/sentry/models/organizationmapping.py

@@ -3,6 +3,7 @@
 from typing import TYPE_CHECKING
 
 from django.db import models
+from django.db.models.functions import Now
 from django.utils import timezone
 
 from sentry import roles
@@ -53,6 +54,8 @@ class OrganizationMapping(Model):
     prevent_superuser_access = models.BooleanField(default=False, db_default=False)
     disable_member_invite = models.BooleanField(default=False, db_default=False)
 
+    date_updated = models.DateTimeField(db_default=Now(), auto_now=True, db_index=True)
+
     class Meta:
         app_label = "sentry"
         db_table = "sentry_organizationmapping"