You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
When creating a notification instance of type retriggered, you can define the retrigger_time which is the interval the notification instance must wait before sending two consecutive notifications.
One of the use cases we use notifications for in the context of systemsp requires this time to be zero.
However both the Fledge backend and the Fledge GUI does not allow a value of zero for the retrigger_time parameter.
Describe the solution you'd like
Allow a value of 0 for retrigger_time when defining or editing a notification instance.
Describe alternatives you've considered
Currently we are using the following workaround which initializes the notification service with retrigger_time=1 and then edit that configuration with retrigger_time=-1:
# Create Notification plugins
curl -sX POST http://localhost:8081/fledge/notification -d '{"name":"'$notif_name_1'","description":"'$notif_name_1' notification instance","rule":"'$notif_plugin_1'","channel":"'$notif_plugin_2'","notification_type":"retriggered","enabled":true,"retrigger_time":"1","rule_config":{},"delivery_config":{}}'# Workaround for delay between notifications (we want 0 but Fledge does not allow it, and -1 is rejected at notification instance creation)
curl -X PUT --data '{"retrigger_time":"-1"}' http://localhost:8081/fledge/category/$notif_name_1
This is a pretty ugly solution which is subject to break if the Fledge API gets updated and also starts to refuse negative values.
Additional context
Existing repositories that would benefit from this features:
Is your feature request related to a problem? Please describe.
When creating a notification instance of type
retriggered
, you can define theretrigger_time
which is the interval the notification instance must wait before sending two consecutive notifications.One of the use cases we use notifications for in the context of systemsp requires this time to be zero.
However both the Fledge backend and the Fledge GUI does not allow a value of zero for the
retrigger_time
parameter.Describe the solution you'd like
Allow a value of 0 for
retrigger_time
when defining or editing a notification instance.Describe alternatives you've considered
Currently we are using the following workaround which initializes the notification service with
retrigger_time=1
and then edit that configuration withretrigger_time=-1
:This is a pretty ugly solution which is subject to break if the Fledge API gets updated and also starts to refuse negative values.
Additional context
Existing repositories that would benefit from this features:
The text was updated successfully, but these errors were encountered: