update-codegen.sh doesn't work outside GOPATH

[ian-mi]

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

1. Move repo outside of GOPATH.
2. Make a change to the injection generators.
3. Run ./hack/update-codegen.sh
4. Observe no change to generated code.

[antoineco]

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 {{output-base}}/{{output-package}}/.

Technically, it does work outside of the GOPATH, but your repo needs to be cloned inside a directory matching -output-package exactly. For example, if your code is inside ~/my-knative-eventing and you set -output-base to ../../, all generated files will be written to

~/knative.dev/eventing/pkg/client/...

instead of

~/my-knative-eventing/pkg/client/...

because -output-package is set to knative.dev/eventing.

[Cynocracy]

/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.

[mattmoor]

cc @n3wscott @imjasonh

[n3wscott]

This is a bug in gengo upstream in Kubernetes.

[github-actions]

This issue is stale because it has been open for 90 days with no
activity. It will automatically close after 30 more days of
inactivity. Reopen the issue with /reopen. Mark the issue as
fresh by adding the comment /remove-lifecycle stale.