Martyn Inglis 0f37824b0c Ensure updates on a research mode service or test key don't touch the history table ...

- note this is an unexpectedly big change.
- When we create a service we pass the service id to the persist method. This means that we don't have the service available to check if in research mode.
- All calling methods (expecting the one where we use the notify service) have the service available. So rather than reload it I changed the method signature to pass the service, not the ID to persist.
- Touches a few places.

Note this means that the update or create methods will fall over on a null service. But this seems correct.

Goes back to the story which we need to play to make the service available as the API user so that the need to load and pass around services is minimised.

2016-12-19 16:45:18 +00: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

process_client_response.py

…

process_notifications.py

Ensure updates on a research mode service or test key don't touch the history table

2016-12-19 16:45:18 +00:00

rest.py

Ensure updates on a research mode service or test key don't touch the history table

2016-12-19 16:45:18 +00:00

validators.py

Makes the app use the redis and statsd clients from utils

2016-12-01 17:20:05 +00:00