infra: refactor govulncheck target and hack script. - #434
Conversation
The govulncheck script now uses the same mechanism for the other tools in hack/tools/bin.
✅ Deploy Preview for node-readiness-controller ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: vitorfloriano The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
|
|
|
Thanks for looking into this, @vitorfloriano !
I think it's one of those things that doesn't fit a presubmit best. Ideally for a vulnerability detector, we should move this into a periodic, that fails separately and can alert us. Potentially even having an "exemption" list so that we can 'silent' some failures if we need to. And our release process to check this periodic for green and address any patches if needed. |
Agreed. So, in this case, I guess I should pivot the PR to:
In a follow-up:
WDYT @ajaysundark? |
Sgtm. @Priyankasaggu11929 do you have any thoughts on tying this with periodics than presubmits? |
|
i think running as a periodics is good for our required signal right now |
Description
This PR refactors how the
govulnchecktool is resolved.The
verify-govulncheckscript now uses the same mechanism as the other tools inhack/tools/bin.Related Issue
Fixes #433
Type of Change
/kind bug
/kind cleanup
/kind failing-test
Testing
Running
verify-govulncheck.shlocally resolves and buildsgovulncheck, then runs the check:Open question
Should it fail if/when vulnerabilities are found?