-
Notifications
You must be signed in to change notification settings - Fork 23
Add QSS webhook notification section w/ anchor #61
base: gh-pages
Are you sure you want to change the base?
Conversation
Quay.io references `http://docs.quay.io/guides/notifications.html#webhook_vulnerability_found` on the page `https://quay.io/repository/will_garrison/repotest/create-notification`. However, this anchor and section do not yet exist. This PR is to add the relevant section with information on the form and use of Clair webhooks. Please revise as needed.
Forgot the http:// on the link, so it was referring to a non-existent page.
I think you may have conflated Clair's notification webhook and Quay's notification webhook for the security scanner. |
#### <i class="fa fa-lg fa-times-circle-o event-icon"></i>Vulnerability Found | ||
<a name="#vulnerability_found"></a> | ||
|
||
Clair has discovered a new vulnerability |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, this should be "Quay Security Scanner has discovered a new vulnerability or an existing vulnerability was updated to a higher severity"
|
||
<a name="#webhook_vulnerability_found"></a> | ||
|
||
Note: Clair webhook notifications report the UUID of the affected build. Use the <a href=http://docs.quay.io/api/swagger>API</a> to analyze notifications for the build. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Clair -> Quay
```json | ||
{ | ||
"Notification": { | ||
"Name": "6e4ad270-4957-4242-b5ad-dad851379573" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The JSON for the QSS notification has this format:
{
"tags": ["latest", "prod"],
"image": "the-image-id",
"vulnerability": {
"id": "CVE-1234-ID",
"description": "Heartbleed 2: Coronary Boogaloo",
"link": "http://link/to/vuln/info",
"priority": "Critical",
"has_fix": true
}
}
I was conflating Clair webhooks with Quay vulnerabilty webhoks. As per advice on this PR I have updated the subheading to reflect "Quay Security Scanner" and corrected the expected output.
I made the updates discussed, and dropped the "Note:" line / API link. |
@@ -221,16 +221,20 @@ A Dockerfile build has failed | |||
#### <i class="fa fa-lg fa-times-circle-o event-icon"></i>Vulnerability Found | |||
<a name="#vulnerability_found"></a> | |||
|
|||
Clair has discovered a new vulnerability | |||
Quay Security Scanner has discovered a new vulnerability or an existing vulnerability was updated to a higher severity |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Period at the end of the sentence
Notification descriptions beneath each heading were full sentences with no periods. Added periods to each of them, and a few sentences lacking periods in the "Notification Actions" section.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Quay.io references
http://docs.quay.io/guides/notifications.html#webhook_vulnerability_found
on the pagehttps://quay.io/repository/will_garrison/repotest/create-notification
. However, this anchor and section do not yet exist. This PR is to add the relevant section with information on the form and use of Clair webhooks. Please revise as needed.