Skip to content

Commit

Permalink
readme: clarify "marked as read" notifications
Browse files Browse the repository at this point in the history
  • Loading branch information
jzelinskie committed Feb 25, 2016
1 parent d1e9a21 commit 2140995
Show file tree
Hide file tree
Showing 2 changed files with 4 additions and 2 deletions.
1 change: 1 addition & 0 deletions api/v1/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -560,6 +560,7 @@ Server: clair
###### Description

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.

###### Example Request
Expand Down
5 changes: 3 additions & 2 deletions notifier/README.md
Original file line number Diff line number Diff line change
@@ -1,8 +1,9 @@
# Notifications

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, it is expected that the receiving endpoint calls the Clair API for reading notifications and marking them as read after being notified.
Because notification data can require pagination, Clair should only send the name of a notification.
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

Expand Down

0 comments on commit 2140995

Please sign in to comment.