fa95ef8772
As per the community goal of migrating the policy file the format from JSON to YAML[1], we need to do two things: 1. Change the default value of '[oslo_policy] policy_file'' config option from 'policy.json' to 'policy.yaml' with upgrade checks. 2. Deprecate the JSON formatted policy file on the project side via warning in doc and releasenotes. Also replace policy.json to policy.yaml ref from doc and tests. [1]https://governance.openstack.org/tc/goals/selected/wallaby/migrate-policy-format-from-json-to-yaml.html Change-Id: Ia7365cc3ae09e2ff916ab9f9ff0ba4fef0dc446b
27 lines
1.0 KiB
Plaintext
27 lines
1.0 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>=3.1.1 # Apache-2.0
|
|
SQLAlchemy>=1.2.19 # MIT
|
|
keystonemiddleware>=4.18.0 # Apache-2.0
|
|
Routes>=2.3.1 # MIT
|
|
WebOb>=1.8.2 # MIT
|
|
jsonschema>=3.2.0 # MIT
|
|
requests>=2.25.0 # Apache-2.0
|
|
setuptools!=24.0.0,!=34.0.0,!=34.0.1,!=34.0.2,!=34.0.3,!=34.1.0,!=34.1.1,!=34.2.0,!=34.3.0,!=34.3.1,!=34.3.2,!=36.2.0,>=21.0.0 # PSF/ZPL
|
|
oslo.concurrency>=3.26.0 # Apache-2.0
|
|
oslo.config>=6.7.0 # Apache-2.0
|
|
oslo.context>=2.22.0 # Apache-2.0
|
|
oslo.log>=4.3.0 # Apache-2.0
|
|
oslo.serialization>=2.25.0 # Apache-2.0
|
|
oslo.utils>=4.5.0 # Apache-2.0
|
|
oslo.db>=4.40.0 # Apache-2.0
|
|
oslo.policy>=3.6.0 # Apache-2.0
|
|
oslo.middleware>=3.31.0 # Apache-2.0
|
|
oslo.upgradecheck>=1.3.0 # Apache-2.0
|
|
# NOTE(efried): Sync lower-constraints.txt for os-traits & os-resource-classes.
|
|
os-resource-classes>=0.5.0 # Apache-2.0
|
|
os-traits>=2.4.0 # Apache-2.0
|
|
microversion-parse>=0.2.1 # Apache-2.0
|