-
Notifications
You must be signed in to change notification settings - Fork 148
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
use kubebuilder go/v4 template #830
Conversation
c68d726
to
3d0c797
Compare
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.
In this commit message, you say as follows:
And since this project does not use custom
resources, generate-api is not generated either. Therefore, the
related codes are removed.
However, TopoLVM uses LogicalVolume custom resource. Is that OK to remove generate-api
target?
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.
Other than what @peng225 pointed out, there seems to be no problem.
aa9edb1
to
04859b3
Compare
Signed-off-by: Yuji Ito <llamerada.jp@gmail.com>
Signed-off-by: Yuji Ito <llamerada.jp@gmail.com>
- Since there is a mix of markers with and without space at the head of the comment, it was unified without. Signed-off-by: Yuji Ito <llamerada.jp@gmail.com>
Remove manifests below config, since those are neither used nor maintained. Signed-off-by: Yuji Ito <llamerada.jp@gmail.com>
- Install and run golangci-lint since kubebuilder uses it. - Some rules have been disabled because conflicts with other PRs will occur if all the points currently made are addressed. - The staticcheck built into golangci-lint does not allow to exclude single lines and specific rules, so we disable it and run the existing staticcheck. Signed-off-by: Yuji Ito <llamerada.jp@gmail.com>
04859b3
to
3cff5a1
Compare
Update kubebuilder template to go/v4 from go/v3. However, no code is moved to the cmd, internal, and test directories. This would be done in a different PR to avoid conflicts with other PRs. And the resolutions to lint's point will be addressed after the directory move is complete.
a part of: #760