6f87111a92
This commit makes keystone tests for oslo policy warning to check policy name explicitly. oslo policy 3.10 modified the warning text to include the policy name as well as the check-str so new warning message verified in keystone test will not work on old oslo policy (<3.10), so bumping the oslo.policy in requirements.txt Change-Id: I14132dfced48ddc93c29ce2b4c20ed2cabc1dbd6
39 lines
1.2 KiB
Plaintext
39 lines
1.2 KiB
Plaintext
# 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.10.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
|
|
msgpack>=0.5.0 # Apache-2.0
|
|
osprofiler>=1.4.0 # Apache-2.0
|
|
pytz>=2013.6 # MIT
|