trigger: consider name in trigger _is_equal()`
authorFrancis Deslauriers <francis.deslauriers@efficios.com>
Mon, 8 Mar 2021 21:11:37 +0000 (16:11 -0500)
committerJérémie Galarneau <jeremie.galarneau@efficios.com>
Fri, 2 Apr 2021 19:38:59 +0000 (15:38 -0400)
commit1ca78886afb53f45d5ee76dfb48f08dd9991e4e2
treed7f8d0d25222c427ef6be5cf3c70caa449516e57
parent091fa780af74dc1a93eaeff50d8c0baf1de8c41f
trigger: consider name in trigger _is_equal()`

For the moment, this is a breaking change since, before 2.13, users
could not register two identical triggers.

Triggers were previously unnamed, but a name is now generated
automatically. This means that a pre-2.13 user that could expect
a TRIGGER_ALREADY_EXISTS reply when registering a trigger that already
existed will now get "OK".

However, since it doesn't know about trigger names, it could now fail
to unregister a trigger (if the instance used to register the trigger
was not kept around).

Signed-off-by: Francis Deslauriers <francis.deslauriers@efficios.com>
Signed-off-by: Jérémie Galarneau <jeremie.galarneau@efficios.com>
Change-Id: I9549980677e2387a7cc0f275233a3b5717fb915e
src/common/trigger.c
This page took 0.032569 seconds and 4 git commands to generate.