Skip to content

Run development tools rather than install them #4172

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

Draft
wants to merge 3 commits into
base: main
Choose a base branch
from

Conversation

cbandy
Copy link
Member

@cbandy cbandy commented May 7, 2025

Checklist:

  • Have you added an explanation of what your changes do and why you'd like them to be included?
  • Have you updated or added documentation for the change, as applicable?
  • Have you tested your changes on all related environments with successful results, as applicable?
    • Have you added automated tests?

Type of Changes:

  • Testing enhancement

What is the current behavior (link to any open issues here)?

Some Make targets download tools to hack/tools while others expect them to be installed already.

What is the new behavior (if this is a feature change)?

Run the tools for contributing code using go run and go tool. This reduces clutter in the project directory and lets Go cache and share these tools effectively across projects.

cbandy added 3 commits May 7, 2025 09:46
The "tool" directive of Go 1.24 ensures that tools use dependencies
compatible with other packages in the same module. This is perfect for
generated code and CRDs based on Go structs.

This also bumps controller-gen to v0.17.3.
This makes it slightly easier to clone the project and immediately run tests.
One may continue to use pre-installed tools by calling Make targets with
the ENVTEST and KUTTL variables.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant