60d1627650
This commit adds docs and reno for migrating policies into code [1]. Like oslo.config, with oslo.policy, we can define all of default rules in code base and only change some rules via policy file. Another thing that we should use yaml format instead of json format. [1] https://governance.openstack.org/tc/goals/queens/policy-in-code.html Co-authored-By: Dai Dang-Van <daidv@vn.fujitsu.com> Change-Id: I67984292022e2a92306b268a40861cff625c22c9
15 lines
635 B
YAML
15 lines
635 B
YAML
---
|
|
features:
|
|
- |
|
|
Mistral now support policy in code, which means if users didn't modify
|
|
any of policy rules, they can leave policy file (in `json` or `yaml`
|
|
format) empty or just remove it all together. Because from now, Mistral
|
|
keeps all default policies under `mistral/policies` module. Users can
|
|
still modify/generate `policy.yaml` file which will override policy
|
|
rules in code if those rules show in `policy.yaml` file.
|
|
other:
|
|
- |
|
|
Default `policy.json` file is now removed as Mistral now generate the
|
|
default policies in code. Please be aware that when using that file in your
|
|
environment.
|