| 1 |
--- |
| 2 |
upgrade: |
| 3 |
- | |
| 4 |
The default value of ``[oslo_policy] policy_file`` config option has |
| 5 |
been changed from ``policy.json`` to ``policy.yaml``. |
| 6 |
Operators who are utilizing customized or previously generated |
| 7 |
static policy JSON files (which are not needed by default), should |
| 8 |
generate new policy files or convert them in YAML format. Use the |
| 9 |
`oslopolicy-convert-json-to-yaml |
| 10 |
<https://docs.openstack.org/oslo.policy/latest/cli/oslopolicy-convert-json-to-yaml.html>`_ |
| 11 |
tool to convert a JSON to YAML formatted policy file in |
| 12 |
backward compatible way. |
| 13 |
deprecations: |
| 14 |
- | |
| 15 |
Use of JSON policy files was deprecated by the ``oslo.policy`` library |
| 16 |
during the Victoria development cycle. As a result, this deprecation is |
| 17 |
being noted in the Wallaby cycle with an anticipated future removal of support |
| 18 |
by ``oslo.policy``. As such operators will need to convert to YAML policy |
| 19 |
files. Please see the upgrade notes for details on migration of any |
| 20 |
custom policy files. |