requirements.txt

boto3==1.4.7
celery==3.1.25 # pyup: <4
docopt==0.6.2
# ignore flask-bcrypt - when upgrading, it installs an invalid version of bcrypt that isn't removed when a different
# branch runs, so can cause other PR builds to fail on jenkins.
# TODO: Upgrade flask-bcrypt in a safe way
Flask-Bcrypt==0.6.2 # pyup: ignore
Flask-Marshmallow==0.8.0
Flask-Migrate==2.1.1
Flask-Script==2.0.5
Flask-SQLAlchemy==2.2
Flask==0.12.2
gunicorn==19.7.1
iso8601==0.1.12
jsonschema==2.6.0
marshmallow-sqlalchemy==0.13.1
marshmallow==2.13.6
monotonic==1.3
psycopg2==2.7.3.1
PyJWT==1.5.2
six==1.10.0
SQLAlchemy-Utils==0.32.14
SQLAlchemy==1.1.13
statsd==3.2.1

notifications-python-client==4.3.1

# PaaS
awscli>=1.11,<1.12
awscli-cwlogs>=1.4,<1.5

git+https://github.com/alphagov/notifications-utils.git@20.0.0#egg=notifications-utils==20.0.0

git+https://github.com/alphagov/boto.git@2.43.0-patch3#egg=boto==2.43.0-patch3
Update boto3 from 1.4.6 to 1.4.7 2017-08-29 21:31:56 +01:00			`boto3==1.4.7`
update dependencies 2017-08-18 15:39:39 +01:00			`celery==3.1.25 # pyup: <4`
			`docopt==0.6.2`
make pyup ignore flask-bcrypt pyup is trying to upgrade flask-bcrypt, which causes errors in all subsequent PR builds for #reasons. Lets make pyup ignore flask-bcrypt until we figure out why the upgrade doesn't work 2017-08-24 11:16:21 +01:00			`# ignore flask-bcrypt - when upgrading, it installs an invalid version of bcrypt that isn't removed when a different`
			`# branch runs, so can cause other PR builds to fail on jenkins.`
			`# TODO: Upgrade flask-bcrypt in a safe way`
			`Flask-Bcrypt==0.6.2 # pyup: ignore`
re-introduce flask-marshmallow 2017-08-22 16:04:15 +01:00			`Flask-Marshmallow==0.8.0`
Update flask-migrate from 2.1.0 to 2.1.1 2017-08-28 23:18:03 +01:00			`Flask-Migrate==2.1.1`
update dependencies 2017-08-18 15:39:39 +01:00			`Flask-Script==2.0.5`
			`Flask-SQLAlchemy==2.2`
			`Flask==0.12.2`
			`gunicorn==19.7.1`
			`iso8601==0.1.12`
			`jsonschema==2.6.0`
Update marshmallow-sqlalchemy from 0.8.0 to 0.13.1 2017-07-24 17:54:32 +01:00			`marshmallow-sqlalchemy==0.13.1`
update dependencies 2017-08-18 15:39:39 +01:00			`marshmallow==2.13.6`
Update monotonic from 1.2 to 1.3 2017-07-24 17:54:50 +01:00			`monotonic==1.3`
Update psycopg2 from 2.7.3 to 2.7.3.1 2017-08-26 14:56:56 +01:00			`psycopg2==2.7.3.1`
update dependencies 2017-08-18 15:39:39 +01:00			`PyJWT==1.5.2`
Update requirements.txt pin version of six to resolve deployment issues 2017-03-27 11:12:39 +01:00			`six==1.10.0`
update dependencies 2017-08-18 15:39:39 +01:00			`SQLAlchemy-Utils==0.32.14`
			`SQLAlchemy==1.1.13`
			`statsd==3.2.1`
Added python client to dependencies 2015-12-14 12:58:49 +00:00
Pin notifications-python-client to latest version 4.3.1 2017-07-24 17:55:00 +01:00			`notifications-python-client==4.3.1`
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`

update utils to v20 - log from multiple app.log*.json files the rotating file handler puts the date on the end, so those old files won't be pushed 2017-08-25 14:38:04 +01:00			`git+https://github.com/alphagov/notifications-utils.git@20.0.0#egg=notifications-utils==20.0.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`