Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Avoid leaking admin-ness into threshold-oriented alarms
Fixes bug 1237567 Previously when an admin created a threshold-oriented alarm on behalf of an non-admin identity, this had the effect of leaking visibility onto statistics for resources that would not normally be visible to the non-admin tenant. Now we ensure that an additional implicit threshold rule query constraint is added on the project ID of the non-admin indentity that will ultimately own the alarm. This is acheived by splitting the query validation from the construction of the kwargs from the query. The addition of the implicit query constraint to the threshold rule can then be delayed to a later point in the dispatch path where the full context of the alarm is known (so that we can check for the case where the alarm is created by an admin on behalf of another tenant). Change-Id: I1adae8c899112e7c3eb4e94f3f68262c84a98574
- Loading branch information
Eoghan Glynn
committed
Oct 10, 2013
1 parent
c024dcf
commit 7ee6f6d
Showing
3 changed files
with
144 additions
and
57 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters