Martyn Inglis ac445114c7 When using a priority template put the notification in the priority queue. ...

- there is now a dedicated worker to handle priority queues. We don't now bundle this in the default worker.

2017-04-04 13:44:11 +01:00

..

__init__.py

Now that we have discovered that the catch all Exception handler doesn't work, I've created a custom exception (SendNotificationQueueError) that handles this case and an error handler for it.

2016-11-21 15:11:19 +00:00

notifications_ses_callback.py

Added a test to ensure that all blueprints have a registered before_request method.

2017-03-17 16:21:41 +00:00

notifications_sms_callback.py

Added a test to ensure that all blueprints have a registered before_request method.

2017-03-17 16:21:41 +00:00

process_client_response.py

Update info log to waring.

2017-01-27 12:20:54 +00:00

process_notifications.py

The redis cache for daily limits and template usage was being updated for notifications with a test api key.

2017-03-30 13:43:44 +01:00

receive_notifications.py

Register a before_request event for all blueprints, that defines the authentication requirement.

2017-03-16 18:15:49 +00:00

rest.py

When using a priority template put the notification in the priority queue.

2017-04-04 13:44:11 +01:00

validators.py

- Refactor v2 post_notification to use a single method for sms and email.

2017-01-17 12:08:24 +00:00