Validate content length on broadcast API

The maximum content count of a broadcast varies depending on its
encoding, so we can’t simply validate it against a schema. This commit
moves to using the validation from `notifications-utils`, and raising a
custom error response.
This commit is contained in:
Chris Hill-Scott
2021-02-12 17:36:25 +00:00
parent fed0d4c40e
commit 0bb671df45
6 changed files with 91 additions and 7 deletions

View File

@@ -35,7 +35,7 @@ notifications-python-client==5.7.1
# PaaS
awscli-cwlogs==1.4.6
git+https://github.com/alphagov/notifications-utils.git@43.8.3#egg=notifications-utils==43.8.3
git+https://github.com/alphagov/notifications-utils.git@43.9.0#egg=notifications-utils==43.9.0
# gds-metrics requires prometheseus 0.2.0, override that requirement as 0.7.1 brings significant performance gains
prometheus-client==0.9.0
@@ -46,14 +46,14 @@ alembic==1.5.4
amqp==1.4.9
anyjson==0.3.3
attrs==20.3.0
awscli==1.19.5
awscli==1.19.8
bcrypt==3.2.0
billiard==3.3.0.23
bleach==3.3.0
blinker==1.4
boto==2.49.0
boto3==1.17.5
botocore==1.20.5
boto3==1.17.8
botocore==1.20.8
certifi==2020.12.5
chardet==4.0.0
click==7.1.2