Skip to content
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

Fixes to code generators #435

Merged

Conversation

adambkaplan
Copy link
Member

  • Moved boilerplate headers to external files
  • Update-codegen.sh improvements:
    • Add header argument to update-codegen.sh - required for k8s 1.18
    • Ensure GOPATH is set - required for k8s 1.18
    • Use script root instead of git root, make code-gen path relative to
      script root
  • generate-fakes improvements
    • Call counterfeiter from GOPATH
    • Add header text from boilerplate
  • Add generate Makefile target to create client, deepcopies, fakes, and
    copyright. Updated travis to install counterfeiter and verify generated
    code.
  • Update docs/development/testing.md to inform contributors of the verification
    step in Travis.
  • Run make generate to add fixed copyright.

I found these updates to be a prerequisite for bumping operator-sdk (#431) and k8s (#284 ).

- Moved boilerplate headers to external files
- Update-codegen.sh improvements:
  - Add header argument to update-codegen.sh - required for k8s 1.18
  - Ensure GOPATH is set - required for k8s 1.18
  - Use script root instead of git root, make code-gen path relative to
    script root
- generate-fakes improvements
  - Call counterfieter from GOPATH
  - Add header text from boilerplate
- Add generate Makefile target to create client, deepcopies, fakes, and
  copyright. Updated travis to install counterfeiter and verify generated
  code.
- Update docs/development/testing.md to inform contributors of the verification
  step in Travis.
Update generated code with corrected copyrights.
Copy link
Member

@SaschaSchwarze0 SaschaSchwarze0 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

Is fine I think, but a lot changes. So waiting for a second pair of eyes to take a look. @zhangtbj can you have a look ?

@openshift-ci-robot openshift-ci-robot added lgtm Indicates that a PR is ready to be merged. approved Indicates a PR has been approved by an approver from all required OWNERS files. labels Oct 10, 2020
@SaschaSchwarze0 SaschaSchwarze0 removed the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Oct 10, 2020
@SaschaSchwarze0
Copy link
Member

@adambkaplan can you please check the tagging automation? I only said that it looked fine. Somehow, the approved tag got also added which was imo incorrect. I manually removed it looking for a second review.

@adambkaplan
Copy link
Member Author

@SaschaSchwarze0 I can check. It might be because you are an approver in the OWNERS file, an lgtm implies approve with with the way we configured the prow plugin.

@qu1queee
Copy link
Contributor

@zhangtbj can u take a look on this later this week?

@zhangtbj
Copy link
Contributor

Document and script changes look good to me.

No code logic change. Approve to unblock the work. Thanks!

/approved

@zhangtbj
Copy link
Contributor

/approve

@openshift-ci-robot
Copy link

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: SaschaSchwarze0, zhangtbj

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:
  • OWNERS [SaschaSchwarze0,zhangtbj]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci-robot openshift-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Oct 15, 2020
@openshift-merge-robot openshift-merge-robot merged commit 5d89593 into shipwright-io:master Oct 15, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants