-
Notifications
You must be signed in to change notification settings - Fork 332
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
update-codegen.sh doesn't work outside GOPATH #1287
Comments
I'd love to see this happen too. Unfortunately this has to be tackled in the Kubernetes generators directly. The issue is that those generators always output to Technically, it does work outside of the GOPATH, but your repo needs to be cloned inside a directory matching
instead of
because |
/assign Cynocracy I didn't see this before hitting the corner case myself :) I have a hacky attempt at a fix in knative.dev/networking, if it works I can upstream it into library. |
This is a bug in gengo upstream in Kubernetes. |
This issue is stale because it has been open for 90 days with no |
/lifecycle frozen I believe there's a hack @scothis had that created a temporary GOPATH in cc @Cynocracy |
I first saw this pattern in kpack. It basically involves setting up a fake GOPATH for gengo |
Does this still repro with the new k8s library versions? I was really hoping it did not :( Fake GOPATH sounds good, we've done similar things internally when we anger the great and powerful Go Mod. |
Expected Behavior
hack/update-codegen.sh should work outside of GOPATH
Actual Behavior
update-codegen either does nothing or uses an incorrect pkg version.
Steps to Reproduce the Problem
The text was updated successfully, but these errors were encountered: