darkhelm/notifications-api
1
0
Fork 0
mirror of https://github.com/GSA/notifications-api.git synced 2026-01-21 10:01:59 -05:00
Code Issues Packages Projects Releases Wiki Activity
Files
25c8f71f2cb3802efd326da4e0bea5f5cc34dfd2
notifications-api/requirements.txt

35 lines
706 B
Plaintext
Raw Normal View History

A little bit of clean up. - Remove the deploy to staging | live links in the README - Update most of the outdated requirements. Left Flask update out for now.
2016-09-05 16:45:54 +01:00
apispec==0.14.0
Initial version of the notify-notifications-api
2015-11-18 17:02:25 +00:00
Flask==0.10.1
Implement a JWT header into base client - adds a base client - adds a notifications client These do not proxy onto genuine methods. This pull request is the basic implication of the API Client. Still needs a few things before is ready, notably proper logging and actual API endpoints to hook into. Basic premise is to deliver the JWT tokens required for Notify API authentication so we can discuss the implementation/premise.
2015-12-11 16:57:00 +00:00
Flask-Script==2.0.5
Initial code added for models and services not functional yet. Bootstrap and migrations added for db.
2016-01-07 17:31:17 +00:00
Flask-Migrate==1.3.1
Flask-SQLAlchemy==2.0
A little bit of clean up. - Remove the deploy to staging | live links in the README - Update most of the outdated requirements. Left Flask update out for now.
2016-09-05 16:45:54 +01:00
psycopg2==2.6.2
SQLAlchemy==1.0.15
SQLAlchemy-Utils==0.32.9
PyJWT==1.4.2
Work in progress, skeleton of the api created and testing started. Need to fix authentication tests.
2016-01-08 17:51:46 +00:00
marshmallow==2.4.2
marshmallow-sqlalchemy==0.8.0
Service and User API added, working with tests. Still need to polish the edges and add more tests.
2016-01-11 15:07:13 +00:00
flask-marshmallow==0.6.2
Add rest of user model fields to api. First step to moving user interactions to api.
2016-01-19 11:38:29 +00:00
Flask-Bcrypt==0.6.2
Added AWS files to - upgrade database - use credstash for secret overrides
2016-01-19 14:50:42 +00:00
credstash==1.8.0
Update boto3
2017-02-23 17:21:15 +00:00
boto3==1.4.4
Update celery requirement
2016-09-05 17:00:16 +01:00
celery==3.1.23
A little bit of clean up. - Remove the deploy to staging | live links in the README - Update most of the outdated requirements. Left Flask update out for now.
2016-09-05 16:45:54 +01:00
monotonic==1.2
Added statsd integration into the API - new client for statsd, follows conventions used elsewhere for configuration - client wraps underlying library so we can use a config property to send/not send statsd Added statsd metrics for: - count of API successful calls SMS/Email - count of successful task execution for SMS/Email - count of errors from Client libraries - timing of API calls to third party clients - timing of how long messages live on the SQS queue
2016-05-13 17:15:39 +01:00
statsd==3.2.1
Move jsonschema to requirements.txt to missing dependency
2016-11-02 14:02:06 +00:00
jsonschema==2.5.1
Run API on Paas
2016-12-08 12:12:45 +00:00
gunicorn==19.6.0
Add a stop celery script into the scripts folder. Stopping celery via upstart issues a TERM signal to the whole process group, which immediately kills the worker threads. This can lead to inconsistentcy in the state of a notification as an API call, for example, can take several seconds consequently the likelihood of the call being lost due to a restart is relatively high. We need to ensure that we stop cleanly to ensure code deploys and autoscale events do not cause issues. this script is called as part of a pre-stop hook in upstart, which passes a pid file location to the script. The script will then issues the TERM signal to only the master celery process. which will cleanly shut down the workers and exit. the script will loop based on the existence of a /proc/{pid} for the celery master process. Once the file is gone the script will exit. Upstart blocks on this script before issuing kill on whatever processes may be left hanging around. the length of the loop is a maximum 15 minutes - which is the tested max time a task may take. In reality it will exit much quicker.
2017-02-08 16:17:50 +00:00
docopt==0.6.2
Update requirements.txt pin version of six to resolve deployment issues
2017-03-27 11:12:39 +01:00
six==1.10.0
Add iso8601 to requirements
2017-05-25 16:13:33 +01:00
iso8601==0.1.11
Added python client to dependencies
2015-12-14 12:58:49 +00:00
update python-client version also unpin the patch version, since it shouldn't matter what patch we're on provided that the function signatures are the same
2016-12-22 13:53:27 +00:00
# pin to minor version 3.1.x
notifications-python-client>=3.1,<3.2
Use the new version of the notifications-python-client. This version no longer adds the req and pay to the claims of the jwt. The change is backward compatible so an older client that sends a jwt with the extra claims will pass authentication. Once all the clients have been updated to not include the extra claims some updates to exclude them from the method signatures will happen as well.
2016-04-14 18:12:33 +01:00
Add awslogs logging for PaaS
2017-02-13 18:04:08 +00:00
# PaaS
awscli>=1.11,<1.12
awscli-cwlogs>=1.4,<1.5
Output contact blocks with placeholders replaced Brings in: - [ ] https://github.com/alphagov/notifications-utils/pull/161 Also brings in: https://github.com/alphagov/notifications-utils/compare/16.1.3...17.0.2
2017-05-11 16:50:36 +01:00
git+https://github.com/alphagov/notifications-utils.git@17.1.0#egg=notifications-utils==17.1.0
Refactor s3upload s3upload function has been moved to notifications-utils. https://github.com/alphagov/notifications-utils/pull/138 must be merge first.
2017-04-06 10:27:13 +01:00
Bump boto version to 2.43.0-patch3
2016-11-02 17:59:09 +00:00
git+https://github.com/alphagov/boto.git@2.43.0-patch3#egg=boto==2.43.0-patch3
Reference in New Issue Copy Permalink