-
Notifications
You must be signed in to change notification settings - Fork 109
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
Re-run make generate and generate-crds #786
Conversation
@imjasonh btw, I think CI is not calling our |
Yes - our go code needs to be the source of truth. Any PR that changes our API godoc needs to ensure that the generated CRDs include those changes, otherwise we'll never update our API on the cluster. |
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.
Merging as this is currently blocking our v0.5.0, we will take the concerns on crds with new lines or not offline.
/lgtm
/approve
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: qu1queee The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Good catch! |
Changes
It seems like the repo has gotten out of sync with generated code, which led to some unnecessary diffs in some changes I was working on. Mostly just copyright headers and diffs from controller-gen
v0.4.1
->v0.5.0
.Should we have a CI check that tries to check that codegen is up-to-date?
Also git-ignore binaries generated by
go build ./cmd/...
./kind cleanup
Submitter Checklist
See the contributor guide
for details on coding conventions, github and prow interactions, and the code review process.
Release Notes