222a8ac5e9
Since we're moving all policy into code and documenting it there we should generate those docs automatically, so they are less likely to be out-of-date. Also add releasenote for ops to aware that Heat is now using policies in code and their Orchestration service needs to avoid depends on policy.json file if file not exist, since there is no such file by default after this patch. Partially-Implements: bp policy-in-code Change-Id: I25fc5a110b1fe515918e042f220c23ac9a7e811f
16 lines
688 B
YAML
16 lines
688 B
YAML
---
|
|
features:
|
|
- |
|
|
Heat now support policy in code, which means if you didn't modify any of
|
|
policy rules, you won't need to add rules in the `policy.yaml` or
|
|
`policy.json` file. Because from now, heat keeps all default policies under
|
|
`heat/policies`. You can still generate and modify a `policy.yaml` file
|
|
which will override policy rules in code if those rules appear in the
|
|
`policy.yaml` file.
|
|
upgrade:
|
|
- |
|
|
Default policy.json file is now removed as we now generate the default
|
|
policies in code. Please be aware that when using that file in your
|
|
environment. You still can generate a `policy.yaml` file if that's required
|
|
in your environment.
|