Reviewed: https://review.opendev.org/621025
Committed:
https://git.openstack.org/cgit/openstack/keystone/commit/?id=5b995cc8fbf0bb654ed0f6a88091c48548f53f6e
Submitter: Zuul
Branch: master
commit 5b995cc8fbf0bb654ed0f6a88091c48548f53f6e
Author: Lance Bragstad <lbrags...@gmail.com>
Date: Thu Nov 29 21:30:06 2018 +0000
Remove limit policies from policy.v3cloudsample.json
By incorporating system-scope and default roles, we've effectively
made these policies obsolete. We can simplify what we maintain and
provide a more consistent, unified view of default limit
behavior by removing them.
Change-Id: Ie0f333a9e8b60154711a24ba7d9ade531217eb71
Closes-Bug: 1805880
** Changed in: keystone
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Identity (keystone).
https://bugs.launchpad.net/bugs/1805880
Title:
Remove obsolete limit and registered limit policies from
policy.v3cloudsample.json
Status in OpenStack Identity (keystone):
Fix Released
Bug description:
Once support for scope types landed in the limit and registered limit
API policies, the policies in policy.v3cloudsample.json became
obsolete [0].
We should add formal protection for the policies with enforce_scope =
True in keystone.tests.unit.protection.v3 and remove the old policies
from the v3 sample policy file.
This will reduce confusion by having a true default policy for limits
and registered limits.
[0]
http://git.openstack.org/cgit/openstack/keystone/tree/etc/policy.v3cloudsample.json?id=fb73912d87b61c419a86c0a9415ebdcf1e186927#n31
To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1805880/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
