Browse Source

feat(workflow): FeatureAdoption migration (#18685)

* Generating feature migration
Chris Fuller 4 years ago
parent
commit
af3861465c
2 changed files with 38 additions and 1 deletions
  1. 1 1
      migrations_lockfile.txt
  2. 37 0
      src/sentry/migrations/0074_add_metric_alert_feature.py

+ 1 - 1
migrations_lockfile.txt

@@ -10,7 +10,7 @@ auth: 0008_alter_user_username_max_length
 contenttypes: 0002_remove_content_type_name
 jira_ac: 0001_initial
 nodestore: 0001_initial
-sentry: 0072_alert_rules_query_changes
+sentry: 0074_add_metric_alert_feature
 sessions: 0001_initial
 sites: 0002_alter_domain_unique
 social_auth: 0001_initial

+ 37 - 0
src/sentry/migrations/0074_add_metric_alert_feature.py

@@ -0,0 +1,37 @@
+# -*- coding: utf-8 -*-
+# Generated by Django 1.11.29 on 2020-05-07 22:15
+from __future__ import unicode_literals
+
+from django.db import migrations, models
+
+
+class Migration(migrations.Migration):
+    # This flag is used to mark that a migration shouldn't be automatically run in
+    # production. We set this to True for operations that we think are risky and want
+    # someone from ops to run manually and monitor.
+    # General advice is that if in doubt, mark your migration as `is_dangerous`.
+    # Some things you should always mark as dangerous:
+    # - Large data migrations. Typically we want these to be run manually by ops so that
+    #   they can be monitored. Since data migrations will now hold a transaction open
+    #   this is even more important.
+    # - Adding columns to highly active tables, even ones that are NULL.
+    is_dangerous = False
+
+    # This flag is used to decide whether to run this migration in a transaction or not.
+    # By default we prefer to run in a transaction, but for migrations where you want
+    # to `CREATE INDEX CONCURRENTLY` this needs to be set to False. Typically you'll
+    # want to create an index concurrently when adding one to an existing table.
+    atomic = True
+
+
+    dependencies = [
+        ('sentry', '0073_migrate_alert_query_model'),
+    ]
+
+    operations = [
+        migrations.AlterField(
+            model_name='featureadoption',
+            name='feature_id',
+            field=models.PositiveIntegerField(choices=[(0, b'Python'), (1, b'JavaScript'), (2, b'Node.js'), (3, b'Ruby'), (4, b'Java'), (5, b'Cocoa'), (6, b'Objective-C'), (7, b'PHP'), (8, b'Go'), (9, b'C#'), (10, b'Perl'), (11, b'Elixir'), (12, b'CFML'), (13, b'Groovy'), (14, b'CSP Reports'), (20, b'Flask'), (21, b'Django'), (22, b'Celery'), (23, b'Bottle'), (24, b'Pylons'), (25, b'Tornado'), (26, b'web.py'), (27, b'Zope'), (40, b'First Event'), (41, b'Release Tracking'), (42, b'Environment Tracking'), (43, b'User Tracking'), (44, b'Custom Tags'), (45, b'Source Maps'), (46, b'User Feedback'), (48, b'Breadcrumbs'), (49, b'Resolve with Commit'), (60, b'First Project'), (61, b'Invite Team'), (62, b'Assign Issue'), (63, b'Resolve in Next Release'), (64, b'Advanced Search'), (65, b'Saved Search'), (66, b'Inbound Filters'), (67, b'Alert Rules'), (68, b'Issue Tracker Integration'), (69, b'Notification Integration'), (70, b'Delete and Discard Future Events'), (71, b'Link a Repository'), (72, b'Ownership Rules'), (73, b'Ignore Issue'), (80, b'SSO'), (81, b'Data Scrubbers'), (90, b'Create Release Using API'), (91, b'Create Deploy Using API'), (92, b'Metric Alert Rules')]),
+        ),
+    ]