d3b647a000
We have signaled many times the use of API extensions to change the API
has been deprecated, including:
04f8612aa9
This patch ensures we no longer check any of the discoverable rules when
compiling the list of extensions to list in the API. This stops users
from being able to use policy to hide certain API extensions. This was
never that useful, but now you can't turn any extensions off and we
report the API version number, it is basically useless.
Note the change in the policy cmd unit test is to ensure now there are
no rules that use the ANY rule, we correctly check we return an empty
list of rules that match.
blueprint remove-discoverable-policy-rules
Change-Id: I61d8063708731133177534888ba7f5f05a6bd901
11 lines
460 B
YAML
11 lines
460 B
YAML
---
|
|
upgrade:
|
|
- |
|
|
All policy rules with the following naming scheme have been
|
|
removed: ``os_compute_api:{extension_alias}:discoverable``
|
|
These policy rules were used to hide an enabled extension from the
|
|
list active API extensions API. Given it is no longer possible to
|
|
disable any API extensions, it makes no sense to have the option
|
|
to hide the fact an API extension is active. As such, all these policy
|
|
rules have been removed.
|