Allow policy.json resource vs constant check
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
openstack-manuals |
Invalid
|
Medium
|
Unassigned |
Bug Description
https:/
Dear documentation bug triager. This bug was created here because we did not know how to map the project name "openstack/
commit 0da5de6b548d343
Author: Florent Flament <email address hidden>
Date: Tue Jan 21 17:03:19 2014 +0000
Allow policy.json resource vs constant check
Adds the ability to check any resource's field against a constant
(literal, or string) in the policy.json file.
For instance, I can ensure that only users with field `enabled` set to
False can be deleted with the following rule:
"identity:
Or that only the `Member` role can be granted:
"identity:
Change-Id: I99688fd88c229b
Implements: blueprint policy-
DocImpact
Changed in openstack-manuals: | |
status: | New → Confirmed |
importance: | Undecided → Medium |
milestone: | none → icehouse |
we don't doc policy.json to this level of detail