keystone/requirements.txt

39 lines
1.2 KiB
Plaintext
Raw Normal View History

# The order of packages is significant, because pip processes them in the order
# of appearance. Changing the order has an impact on the overall integration
# process, which may cause wedges in the gate later.
pbr!=2.1.0,>=2.0.0 # Apache-2.0
WebOb>=1.7.1 # MIT
Flask!=0.11,>=1.0.2 # BSD
Flask-RESTful>=0.3.5 # BSD
cryptography>=2.7 # BSD/Apache-2.0
SQLAlchemy>=1.3.0 # MIT
sqlalchemy-migrate>=0.13.0 # Apache-2.0
stevedore>=1.20.0 # Apache-2.0
passlib>=1.7.0 # BSD
python-keystoneclient>=3.8.0 # Apache-2.0
keystonemiddleware>=7.0.0 # Apache-2.0
bcrypt>=3.1.3 # Apache-2.0
scrypt>=0.8.0 # BSD
oslo.cache>=1.26.0 # Apache-2.0
oslo.config>=6.8.0 # Apache-2.0
oslo.context>=2.22.0 # Apache-2.0
oslo.messaging>=5.29.0 # Apache-2.0
oslo.db>=6.0.0 # Apache-2.0
oslo.i18n>=3.15.3 # Apache-2.0
oslo.log>=3.44.0 # Apache-2.0
oslo.middleware>=3.31.0 # Apache-2.0
oslo.policy>=3.6.0 # Apache-2.0
oslo.serialization!=2.19.1,>=2.18.0 # Apache-2.0
oslo.upgradecheck>=1.3.0 # Apache-2.0
oslo.utils>=3.33.0 # Apache-2.0
oauthlib>=0.6.2 # BSD
pysaml2>=5.0.0
PyJWT>=1.6.1 # MIT
dogpile.cache>=1.0.2 # BSD
jsonschema>=3.2.0 # MIT
pycadf!=2.0.0,>=1.1.0 # Apache-2.0
Move use of constraints out of install_cmd If you have a -c in the install_cmd it gets used with all the deps supplied this means that the lower-constraints job actually install from upper-constraints :( You can see what I mean in [1] Note both lower-constraints.txt and upper-constraints.txt are used ; and --- Collecting oslo.log===3.39.0 (from -c /home/zuul/src/git.openstack.org/openstack/requirements/upper-constraints.txt (line 247)) --- With this fixed we find a few minimums that needs to be bumped: * oslo.policy >= 1.33.0 keystone uses the scope_types[2] kwarg to RuleDefault which was introduced in 52c82ff9ab04dd78ff7045cb30d2f5de535dd7da which is contained in 1.32.0 ; also we need the 'policy-in-code' feature which is in 1.33.0 * oslo.log >= 0.38.0 keystone used the ROCKY[3] constant for deprecations which was introduced in d68a895ee8e61b5c9d4ef368e7f04252e84649e9 which is contained in 3.38.0 * msgpack >= 0.5.0 the 0.4.x versions have been removed from pypi so we have to bump the minimum :( * SQLAlchemy >= 1.0.13 identity_provider_id in token payload is byte in python3 which triggers a sqlalchemy bug[4]. The bug has been fixed in 1.0.13 * keystonemiddleware >= 5.1.0 unified limit feature uses system scope feature which is supported in keystonemiddleware after 5.1.0 We also add correct some errors in bindep.txt related to use on Fedora [1] http://logs.openstack.org/47/599447/2/check/openstack-tox-lower-constraints/bbc912b/tox/lower-constraints-1.log [2] http://git.openstack.org/cgit/openstack/keystone/tree/keystone/common/policies/access_token.py#n24 [3] http://git.openstack.org/cgit/openstack/keystone/tree/keystone/conf/default.py#n50 [4] http://docs.sqlalchemy.org/en/latest/changelog/changelog_10.html#change-a14dd2e73d889d065acc07a77b1ee7cb Change-Id: Ic0de6799fddd86a70abae2c87c92d565072ebdb9
2018-09-10 05:55:40 +00:00
msgpack>=0.5.0 # Apache-2.0
osprofiler>=1.4.0 # Apache-2.0
pytz>=2013.6 # MIT