Whether a later change to an already-exported alert is delivered too, as a second
lakewatch.alert.updated event to the same webhook URL (a close is such an update, carrying a
terminal alert_state). Creation export is unaffected either way.
Opt-in, and unset means off: a webhook is an event transport rather than a system whose record
is edited in place, so an update is an extra event the receiving consumer has to correlate to
the alert it already handled. A destination configured before this event existed must not start
receiving more without its owner asking.
Optionalurl
url?:string
Webhook destination the server POSTs payloads to, in plaintext. Userinfo
(user:password@) is sent as HTTP Basic auth.
Whether a later change to an already-exported alert is delivered too, as a second
lakewatch.alert.updatedevent to the same webhook URL (a close is such an update, carrying a terminalalert_state). Creation export is unaffected either way.Opt-in, and unset means off: a webhook is an event transport rather than a system whose record is edited in place, so an update is an extra event the receiving consumer has to correlate to the alert it already handled. A destination configured before this event existed must not start receiving more without its owner asking.