e938c49628
This commit introduces some tests that explicitly show how project users are expected to behave with the limits API. A subsequent patch will clean up the now obsolete policies in the policy.v3cloudsample.json policy file. Related-Bug: 1805880 Closes-Bug: 1818736 Change-Id: I12d1200d8a11cadcc4f7b2604d51d8e5c73ea4b7
18 lines
835 B
YAML
18 lines
835 B
YAML
---
|
|
features:
|
|
- |
|
|
[`bug 1818736 <https://bugs.launchpad.net/keystone/+bug/1818736>`_]
|
|
The ``identity:get_limit``, ``identity:list_limits`` and
|
|
``identity:get_limit_model`` policies now support domain scope, so domain
|
|
users are now able to get limit information on their own domains as well as
|
|
see the limit model in effect.
|
|
upgrade:
|
|
- |
|
|
[`bug 1818736 <https://bugs.launchpad.net/keystone/+bug/1818736>`_]
|
|
The ``identity:get_limit`` policy default check string has been changed to
|
|
support domain scope. This policy are not being formally deprecated because
|
|
the unified limits API is still considered experimental. These
|
|
new default automatically account for domain scope in addition to system
|
|
scope. Please consider these new defaults if your deployment overrides the
|
|
limit policies.
|