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

Validate CAP against the spec

Browse Source 
This gives us some extra confidence that there aren’t any problems with
the data we’re getting from the other service. It doesn’t address any
specific problems we’ve seen, rather it seems like a sensible precaution
to take.
This commit is contained in:
Chris Hill-Scott
2021-01-18 10:01:47 +00:00
parent 38f07db23e
commit 26871eeacc
6 changed files with 274 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

9
requirements.txt
View File

@@ -26,6 +26,7 @@ strict-rfc3339==0.7
rfc3987==1.3.8
cachetools==4.2.0
beautifulsoup4==4.9.3
lxml==4.6.2
notifications-python-client==5.7.1
@@ -39,18 +40,18 @@ prometheus-client==0.9.0
gds-metrics==0.2.4
## The following requirements were added by pip freeze:
alembic==1.4.3
alembic==1.5.0
amqp==1.4.9
anyjson==0.3.3
attrs==20.3.0
awscli==1.18.215
awscli==1.18.216
bcrypt==3.2.0
billiard==3.3.0.23
bleach==3.2.1
blinker==1.4
boto==2.49.0
boto3==1.16.55
botocore==1.19.55
boto3==1.16.56
botocore==1.19.56
certifi==2020.12.5
chardet==4.0.0
click==7.1.2