Skip to content

clean envs used in fake GOPATH hack #477

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

Merged
merged 2 commits into from
May 6, 2025
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 0 additions & 11 deletions make/generate.mk
Original file line number Diff line number Diff line change
Expand Up @@ -10,17 +10,6 @@ MEMBER_CLUSTER_CRDS:=useraccounts nstemplatesets memberstatuses idlers toolchain
PATH_TO_CRD_BASES=config/crd/bases

PROJECT_DIR := $(shell pwd)
# openapi-gen requires the GOPATH env var be set and the codebase be present within it.
# Let's not require $GOPATH be set up in the user's environment and the checkout be
# placed in it.
# Instead, fake it locally.
FAKE_GOPATH=$(PROJECT_DIR)/.fake-gopath
# The root of all codeready-toolchain repos in the GOPATH
CRT_IN_GOPATH=$(FAKE_GOPATH)/src/github.com/codeready-toolchain
# This gives the GOPATH as understood by the go compiler even if the env var is not explicitly set.
# We use this to find the packages that are already downloaded locally to save on the network traffic
# when persuading openapi-gen that our codebase is checked out under the GOPATH.
LOCAL_GOPATH=`$(GO) env GOPATH`

.PHONY: generate
## Generate deepcopy, openapi and CRD files after the API was modified
Expand Down
Loading