Previously, if an alarm had multiple trust+ actions then we would create
a new trust ID for each one. We would also create new trusts for them
all each time the alarm was updated (even for actions that hadn't
changed).
With this change, we will only use a single trust ID for each alarm that
contains one or more trust+ actions.
Reviewed: https:/ /review. openstack. org/413321 /git.openstack. org/cgit/ openstack/ aodh/commit/ ?id=2d157539244 193ab7cedd89046 0689ccb170df55
Committed: https:/
Submitter: Jenkins
Branch: master
commit 2d157539244193a b7cedd890460689 ccb170df55
Author: Zane Bitter <email address hidden>
Date: Tue Dec 20 19:24:34 2016 -0500
Don't create multiple trust IDs per alarm
Previously, if an alarm had multiple trust+ actions then we would create
a new trust ID for each one. We would also create new trusts for them
all each time the alarm was updated (even for actions that hadn't
changed).
With this change, we will only use a single trust ID for each alarm that
contains one or more trust+ actions.
Change-Id: Ib556ed3248221d 6efb36f2117991c 47e665ce336
Partial-Bug: #1575113