Revocation event pruning should only occur on new revocations. This
will limit the volume of churn to the DB/KVS store for revocation
events (and impact to performance).
Change-Id: I1ad7491c54023915c74610287a5095589f12d5c1
Closes-Bug: #1287757
(cherry picked from commit d7e529911c496c71effa1d51e1ecf2399ef359f1)
Reviewed: https:/ /review. openstack. org/203104 /git.openstack. org/cgit/ openstack/ keystone/ commit/ ?id=0fe2b70d495 563892bfd645958 8bd6d0ac694ee7
Committed: https:/
Submitter: Jenkins
Branch: stable/kilo
commit 0fe2b70d4955638 92bfd6459588bd6 d0ac694ee7
Author: Morgan Fainberg <email address hidden>
Date: Fri Jul 17 08:28:30 2015 -0700
Do not remove expired revocation events on "get"
Revocation event pruning should only occur on new revocations. This
will limit the volume of churn to the DB/KVS store for revocation
events (and impact to performance).
Change-Id: I1ad7491c540239 15c74610287a509 5589f12d5c1 1effa1d51e1ecf2 399ef359f1)
Closes-Bug: #1287757
(cherry picked from commit d7e529911c496c7