When there are multiple constraints set for a policy, if the first constraint evaluates to false, then the other constraints are evaluated.
| Comment | File | Size | Author |
|---|---|---|---|
| #2 | evaluation-update-3160939-2.patch | 649 bytes | rahul.shinde |
When there are multiple constraints set for a policy, if the first constraint evaluates to false, then the other constraints are evaluated.
| Comment | File | Size | Author |
|---|---|---|---|
| #2 | evaluation-update-3160939-2.patch | 649 bytes | rahul.shinde |
Comments
Comment #2
rahul.shindeComment #3
vbouchetHi Rahul,
Sorry for the (very) late reply.
I am not sure to understand your point. For a policy to apply, all the constraints must match.
For example, if I want to set the memory_limit to 1G for admin/structure for the "webmaster" role only, I would have 2 constraints. The policy applies if both constraints match. With your change, the memory_limit will be set to 1G as soon as we are on admin/structure, whatever the role is as it would not be evaluated. It would also apply as soon as the user has the "webmaster" role, whatever the page he is visiting.
Does it make sense?
I am closing to keep the issue queue clean but if you disagree my point and still think there is something to fix, feel free to reopen.