-
Notifications
You must be signed in to change notification settings - Fork 370
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(guided remediation): non-interactive JSON output format #1437
base: main
Are you sure you want to change the base?
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #1437 +/- ##
==========================================
- Coverage 69.58% 67.17% -2.42%
==========================================
Files 186 193 +7
Lines 18354 18287 -67
==========================================
- Hits 12772 12284 -488
- Misses 4890 5348 +458
+ Partials 692 655 -37 ☔ View full report in Codecov by Sentry. |
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!
cmd/osv-scanner/fix/output.go
Outdated
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.
can you add documentation to these newly defined structs?
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.
documentation added
Closes #1213
Adds
--format
flag toosv-scanner fix --non-interactive
to choose between oldtext
and newjson
format, which provides a more machine-readable description of the changes made by guided remediation. Thetext
format should remain unchanged.Also, renamed the
relock
strategy torelax
(though maintained backwards-compatibility) to be a bit less ambiguous.There are a few things that'll need to change with osv-scanner v2. In particular, the way the reporter interface is being used. I'll need to revisit this when those are refactored.