This is the first deploy in series of deploys to give certain templates priority in processing.

If the template is marked as priority the notification will be sent using the `notify` queue.
The `notify` queue is a low volume queue, messages here will not be queue behind a large job and should be delivered with in a more consistent time frame.

- Added templates.process_type and templates_history.process_type column.
- Added a template_process_type table to handle the enum for templates.process_type, initial values are normal and priority

https://www.pivotaltracker.com/story/show/135429147

tests/app/notifications/test_process_notification.py

@@ -12,7 +12,6 @@ from app.notifications import SendNotificationToQueueError
 from app.notifications.process_notifications import (create_content_for_notification,
                                                      persist_notification, send_notification_to_queue)
 from app.v2.errors import BadRequestError
-from tests.app.conftest import sample_notification, sample_template, sample_email_template
 
 
 def test_create_content_for_notification_passes(sample_email_template):

tests/conftest.py

@@ -70,7 +70,12 @@ def notify_db_session(notify_db):
 
     notify_db.session.remove()
     for tbl in reversed(notify_db.metadata.sorted_tables):
-        if tbl.name not in ["provider_details", "key_types", "branding_type", "job_status", "provider_details_history"]:
+        if tbl.name not in ["provider_details",
+                            "key_types",
+                            "branding_type",
+                            "job_status",
+                            "provider_details_history",
+                            "template_process_type"]:
             notify_db.engine.execute(tbl.delete())
     notify_db.session.commit()