readme: clarify "marked as read" notifications
This commit is contained in:
parent
d1e9a21e0e
commit
2140995a54
@ -560,6 +560,7 @@ Server: clair
|
|||||||
###### Description
|
###### Description
|
||||||
|
|
||||||
The delete route for the Notifications resource marks a Notification as read.
|
The delete route for the Notifications resource marks a Notification as read.
|
||||||
|
If a notification is not marked as read, Clair will continue to notify the provided endpoints.
|
||||||
The time at which this Notification was marked as read can be seen in the `Notified` property of the response GET route for Notification.
|
The time at which this Notification was marked as read can be seen in the `Notified` property of the response GET route for Notification.
|
||||||
|
|
||||||
###### Example Request
|
###### Example Request
|
||||||
|
@ -1,8 +1,9 @@
|
|||||||
# Notifications
|
# Notifications
|
||||||
|
|
||||||
Notifications are a way for Clair to inform an endpoint that changes to tracked vulnerabilities have occurred.
|
Notifications are a way for Clair to inform an endpoint that changes to tracked vulnerabilities have occurred.
|
||||||
Notifications should contain only the name of a notification.
|
Because notification data can require pagination, Clair should only send the name of a notification.
|
||||||
Because notification data can require pagination, it is expected that the receiving endpoint calls the Clair API for reading notifications and marking them as read after being notified.
|
It is expected that the receiving endpoint calls the Clair API for reading notifications and marking them as read after being notified.
|
||||||
|
If the notification is never marked as read, Clair will continue attempting to send the same notification to the endpoint indefinitely.
|
||||||
|
|
||||||
## Webhook
|
## Webhook
|
||||||
|
|
||||||
|
Loading…
Reference in New Issue
Block a user