85c957c503
Because we have policy in code, we should be able to use the oslo.policy CLI scripts to produce sample policy files and render complete policies based on overrides on disk. This was broken because keystone wasn't removing unexpected commandline arguments before passing them to oslo.config to parse. This prevented people from generating complete policy files like they would for horizon. This commit exposes a get_enforcer() that substitutes an empty list in place of arguments passed in through the system. This makes it so that oslo.config doesn't choke when processing configuration values. Change-Id: I22583258eac5b3a64208355d18ccfa62dba1871d Closes-Bug: 1740951
9 lines
338 B
YAML
9 lines
338 B
YAML
---
|
|
fixes:
|
|
- |
|
|
[`bug 1740951 <https://bugs.launchpad.net/keystone/+bug/1740951>`_]
|
|
A new method was added that made it so oslo.policy sample generation
|
|
scripts can be used with keystone. The ``oslopolicy-policy-generator``
|
|
script will now generate a policy file containing overrides and defaults
|
|
registered in code.
|