commit 852a5186b8bcbd64fe274ed5b05d72f5809c254f
Author: Richard Avelar <email address hidden>
Date: Thu Nov 3 16:32:36 2016 +0000
Remove unused statements in matches
With recent changes [1], in list_events in the sql backend there is no
longer a need to use repetitive statements. list_events already prunes
out rows based off user_id, project_id, audit_id and issued_at so we
can remove these subsequent statements in matches.
In order to test this, the _assertToken methods needed to call the
list_events method directly. The old implementation ignores
list_events and instead makes a list where it can "add_event" and
"remove_event" which bypasses testing the actual changes made in
list_events since the tests assume list_events would have just sent
back the entire list anyway rather than what it does now which is
filter events based off the token
Reviewed: https:/ /review. openstack. org/393399 /git.openstack. org/cgit/ openstack/ keystone/ commit/ ?id=852a5186b8b cbd64fe274ed5b0 5d72f5809c254f
Committed: https:/
Submitter: Jenkins
Branch: master
commit 852a5186b8bcbd6 4fe274ed5b05d72 f5809c254f
Author: Richard Avelar <email address hidden>
Date: Thu Nov 3 16:32:36 2016 +0000
Remove unused statements in matches
With recent changes [1], in list_events in the sql backend there is no
longer a need to use repetitive statements. list_events already prunes
out rows based off user_id, project_id, audit_id and issued_at so we
can remove these subsequent statements in matches.
In order to test this, the _assertToken methods needed to call the
list_events method directly. The old implementation ignores
list_events and instead makes a list where it can "add_event" and
"remove_event" which bypasses testing the actual changes made in
list_events since the tests assume list_events would have just sent
back the entire list anyway rather than what it does now which is
filter events based off the token
[1] 9e8437146183188 0ce5736e9888c7d 9648e3a77b 6df7aabf70359cc 849a70f914b
Related-Bug: 1524030
Change-Id: I8cb111df733f82