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
The Lacework API is now returning vulnerability reports that contain
0 vulnerabilities, we need to make the Go API and the CLI to understand
those payloads and display a message to the user that explains that the
report has no vulnerabilities, if we visualize a report with 0 vulnerabilities
today, the output looks like this:
$ lacework vulnerability report sha256:d8a573f7ba9ea2c196f13b6e71ba0aeefe715f69bf8291c155ff7dfe9bc2ec2f --image_id
CONTAINER IMAGE DETAILS | VULNERABILITIES
--------------------------+---------------------------------
ID | SEVERITY COUNT FIXABLE
Digest | -----------+-------+----------
Registry | Critical 0 0
Repository | High 0 0
Size 0 B | Medium 0 0
Created At | Low 0 0
Tags | Info 0 0
|
Try using '--details' to increase details shown about the vulnerability report.
The proposal output to show to the end-user is:
$ lacework vulnerability report sha256:d8a573f7ba9ea2c196f13b6e71ba0aeefe715f69bf8291c155ff7dfe9bc2ec2f --image_id
Great news! This container image has no vulnerabilities.
afiune
changed the title
feat: make the CLI understand vuln reports with 0 vulnerabilities
feat: understand vuln reports with 0 vulnerabilities
May 29, 2020
Make the Go API and the CLI to understand new payloads from the vuln
reports API endpoints that displays reports with 0 vulnerabilities,
we are now displaying a message to the user that explains that the
report has no vulnerabilities
The output shown to the end-user is for reports with 0 vulnerabilities:
```
$ lacework vul report sha256:32c5a42735581453d1e9ea664604fa81f4b635459dc88799ee1f8c373dca4819
Great news! This container image has no vulnerabilities.
```
And for the JSON format:
```
$ lacework vul report sha256:32c5a42735581453d1e9ea664604fa81f4b635459dc88799ee1f8c373dca4819 --json
{
"critical_vulnerabilities": 0,
"fixable_vulnerabilities": 0,
"high_vulnerabilities": 0,
"info_vulnerabilities": 0,
"low_vulnerabilities": 0,
"medium_vulnerabilities": 0,
"scan_status": "Success",
"total_vulnerabilities": 0
}
```
Closes#123
Signed-off-by: Salim Afiune Maya <afiune@lacework.net>
Make the Go API and the CLI to understand new payloads from the vuln
reports API endpoints that displays reports with 0 vulnerabilities,
we are now displaying a message to the user that explains that the
report has no vulnerabilities
The output shown to the end-user is for reports with 0 vulnerabilities:
```
$ lacework vul report sha256:32c5a42735581453d1e9ea664604fa81f4b635459dc88799ee1f8c373dca4819
Great news! This container image has no vulnerabilities.
```
And for the JSON format:
```
$ lacework vul report sha256:32c5a42735581453d1e9ea664604fa81f4b635459dc88799ee1f8c373dca4819 --json
{
"critical_vulnerabilities": 0,
"fixable_vulnerabilities": 0,
"high_vulnerabilities": 0,
"info_vulnerabilities": 0,
"low_vulnerabilities": 0,
"medium_vulnerabilities": 0,
"scan_status": "Success",
"total_vulnerabilities": 0
}
```
Closes#123
Signed-off-by: Salim Afiune Maya <afiune@lacework.net>
The Lacework API is now returning vulnerability reports that contain
0 vulnerabilities, we need to make the Go API and the CLI to understand
those payloads and display a message to the user that explains that the
report has no vulnerabilities, if we visualize a report with 0 vulnerabilities
today, the output looks like this:
The proposal output to show to the end-user is:
The JSON output should match the following:
The text was updated successfully, but these errors were encountered: