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: Ie6e22b0b47c5148290f7b76c95967cd9a343343c
34 lines
1.1 KiB
Plaintext
34 lines
1.1 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.
|
|
|
|
debtcollector>=1.2.0 # Apache-2.0
|
|
tenacity>=3.1.0 # Apache-2.0
|
|
keystonemiddleware>=5.1.0 # Apache-2.0
|
|
lxml>=2.3 # BSD
|
|
oslo.db>=4.1.0 # Apache-2.0
|
|
oslo.config>=6.8.0 # Apache-2.0
|
|
oslo.context>=2.22.0 # Apache-2.0
|
|
oslo.i18n>=2.1.0 # Apache-2.0
|
|
oslo.log>=4.3.0 # Apache-2.0
|
|
oslo.policy>=3.6.0 # Apache-2.0
|
|
oslo.reports>=0.6.0 # Apache-2.0
|
|
Paste
|
|
PasteDeploy>=1.5.0 # MIT
|
|
pbr>=2.0.0 # Apache-2.0
|
|
pecan>=1.0.0 # BSD
|
|
oslo.middleware>=3.10.0 # Apache-2.0
|
|
oslo.serialization>=2.25.0 # Apache-2.0
|
|
oslo.utils>=3.5.0 # Apache-2.0
|
|
PyYAML>=5.1.0 # MIT
|
|
SQLAlchemy!=1.1.5,!=1.1.6,!=1.1.7,!=1.1.8,>=1.0.10 # MIT
|
|
stevedore>=1.9.0 # Apache-2.0
|
|
WebOb>=1.2.3 # MIT
|
|
WSME>=0.8 # MIT
|
|
alembic>=0.7.6,!=0.8.1,!=0.9.0
|
|
# NOTE(jd) We do not import it directly, but WSME datetime string parsing
|
|
# behaviour changes when this library is installed
|
|
python-dateutil>=2.4.2 # BSD
|
|
pymongo!=3.1 # Apache-2.0
|
|
elasticsearch<3.0.0 # Apache-2.0
|