Introduce a Go workspace #18409
Labels
area/tooling
backport/v3.5
priority/important-longterm
Important over the long term, but may not be staffed and/or may need multiple releases to complete.
type/feature
What would you like to be added?
After discussing this in last week's community meeting and based on feedback from the Go team (golang/go#68254) due to the vulnerability (GHSA-5x4g-q5rc-36jp / golang/vulndb#2952), there are several benefits to introducing a Go workspace in the project, and one of the biggest motivations is to simplify the test scripts.
I have a branch with the
go.workspace
(diff). It requires changes in the build scripts and the test libraries. It still doesn't work, but there's some progress.I mostly based it on how kubernetes/kubernetes defines the Go workspace. However, from golang/go#68254 and the motivation to have
govulncheck
spot vulnerabilities within our modules, their suggestion is to removereplaces
pointing to local code ingo.mod
s, but k/k still has these replaces.I wanted to open up the discussion to get feedback and/or implementation ideas.
Why is this needed?
To improve the code quality and to spot vulnerabilities in our code firsthand.
The text was updated successfully, but these errors were encountered: