ref(integration-platform): Add ALERTS feature (#22614)

* ref(integration-platform): Add ALERTS feature

* the migration

Author: MeredithAnya

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: 0142_add_dashboard_tombstone
+sentry: 0143_add_alerts_integrationfeature
 sessions: 0001_initial
 sites: 0002_alter_domain_unique
 social_auth: 0001_initial

src/sentry/migrations/0143_add_alerts_integrationfeature.py

@@ -0,0 +1,38 @@
+# -*- coding: utf-8 -*-
+# Generated by Django 1.11.29 on 2020-12-10 23:55
+from __future__ import unicode_literals
+
+from django.db import migrations
+import sentry.db.models.fields.bounded
+
+
+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', '0142_add_dashboard_tombstone'),
+    ]
+
+    operations = [
+        migrations.AlterField(
+            model_name='integrationfeature',
+            name='feature',
+            field=sentry.db.models.fields.bounded.BoundedPositiveIntegerField(choices=[(0, 'integrations-api'), (1, 'integrations-issue-link'), (2, 'integrations-stacktrace-link'), (3, 'integrations-event-hooks'), (4, 'integrations-project-management'), (5, 'integrations-incident-management'), (6, 'integrations-feature-flag'), (7, 'integrations-alerts')], default=0),
+        ),
+    ]

src/sentry/models/integrationfeature.py

@@ -14,6 +14,7 @@ class Feature(object):
     PROJECT_MANAGEMENT = 4
     INCIDENT_MANAGEMENT = 5
     FEATURE_FLAG = 6
+    ALERTS = 7
 
     @classmethod
     def as_choices(cls):
@@ -25,6 +26,7 @@ def as_choices(cls):
             (cls.PROJECT_MANAGEMENT, u"integrations-project-management"),
             (cls.INCIDENT_MANAGEMENT, u"integrations-incident-management"),
             (cls.FEATURE_FLAG, u"integrations-feature-flag"),
+            (cls.ALERTS, u"integrations-alerts"),
         )
 
     @classmethod
@@ -41,6 +43,8 @@ def as_str(cls, feature):
             return "integrations-incident-management"
         if feature == cls.FEATURE_FLAG:
             return "integrations-feature-flag"
+        if feature == cls.ALERTS:
+            return "integrations-alerts"
         return "integrations-api"
 
     @classmethod
@@ -57,6 +61,8 @@ def description(cls, feature, name):
             return "Organizations can **open a line to Sentry's stack trace** in another service."
         if feature == cls.EVENT_HOOKS:
             return "%s allows organizations to **forward events to another service**." % name
+        if feature == cls.ALERTS:
+            return "Configure Sentry alerts to trigger notifications in %s." % name
         # default
         return (
             "%s can **utilize the Sentry API** to pull data or update resources in Sentry (with permissions granted, of course)."