| 1 |
--- |
| 2 |
features: |
| 3 |
- | |
| 4 |
Masakari now support policy in code, which means if operators doesn't need to |
| 5 |
modify any of the default policy rules, they do not need a policy file. |
| 6 |
Operators can modify/generate a ``policy.yaml.sample`` file which will override |
| 7 |
specific policy rules from their defaults. |
| 8 |
|
| 9 |
Masakari is now configured to work with two oslo.policy CLI scripts that |
| 10 |
have been added: |
| 11 |
|
| 12 |
- The first of these can be called like |
| 13 |
``oslopolicy-list-redundant --namespace masakari`` and will output a list of |
| 14 |
policy rules in policy.[json|yaml] that match the project defaults. These |
| 15 |
rules can be removed from the policy file as they have no effect there. |
| 16 |
- The second script can be called like |
| 17 |
``oslopolicy-policy-generator --namespace masakari --output-file policy-merged.yaml`` |
| 18 |
and will populate the policy-merged.yaml file with the effective policy. |
| 19 |
This is the merged results of project defaults and config file overrides. |
| 20 |
|
| 21 |
NOTE: Default `policy.json` file is now removed as Masakari now uses default |
| 22 |
policies. A policy file is only needed if overriding one of the defaults. |