darkhelm/notifications-api
1
0
Fork 0
mirror of https://github.com/GSA/notifications-api.git synced 2026-08-25 16:53:42 -04:00
Code Issues Packages Projects Releases Wiki Activity

Delete unused code

Browse Source 
* The `_should_record_notification_in_history_table` function stopped being
used in this commit: c23ae15f32
* `NOTIFICATIONS_ALERT` stopped being used in this commit: 5aa37f09b6
This commit is contained in:
Katie Smith
2019-07-12 11:23:45 +01:00
parent 1671221642
commit cec87a9de0
2 changed files with 0 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files

1
app/config.py
View File

@@ -293,7 +293,6 @@ class Config(object):
} }
CELERY_QUEUES = [] CELERY_QUEUES = []
NOTIFICATIONS_ALERT = 5 # five mins
FROM_NUMBER = 'development' FROM_NUMBER = 'development'
STATSD_HOST = os.getenv('STATSD_HOST') STATSD_HOST = os.getenv('STATSD_HOST')

8
app/dao/notifications_dao.py
View File

@@ -79,14 +79,6 @@ def dao_create_notification(notification):
db.session.add(notification) db.session.add(notification)
def _should_record_notification_in_history_table(notification):
if notification.api_key_id and notification.key_type == KEY_TYPE_TEST:
return False
if notification.service.research_mode:
return False
return True
def _decide_permanent_temporary_failure(current_status, status): def _decide_permanent_temporary_failure(current_status, status):
# Firetext will send pending, then send either succes or fail. # Firetext will send pending, then send either succes or fail.
# If we go from pending to delivered we need to set failure type as temporary-failure # If we go from pending to delivered we need to set failure type as temporary-failure