code-generator

code-generator copied to clipboard

I predefine a type and exec generate-groups.sh to generate but just get clientset file, lister and informer not auto generated. why?

my project under $GOPATH/srcfile using go mod to manage dependency and looked like blow:

[root@centos72-k8s k8s_customize_controller]# tree
.
├── go.mod
├── go.sum
└── pkg
    └── apis
        └── bolingcavalry
            ├── register.go
            └── v1
                ├── doc.go
                ├── register.go
                └── types.go

4 directories, 6 files

i use command ./generate-groups.sh all k8s_customize_controller/pkg/client k8s_customize_controller/pkg/apis "bolingcavalry:v1" -v 10 to generate code. output blow:

Generating deepcopy funcs
I0122 01:19:34.004795   91884 parse.go:383] importPackage k8s_customize_controller/pkg/apis/bolingcavalry/v1
I0122 01:19:34.004866   91884 parse.go:330] addDir k8s_customize_controller/pkg/apis/bolingcavalry/v1
I0122 01:19:34.881754   91884 parse.go:404] unable to import "k8s_customize_controller/pkg/apis/bolingcavalry/v1": package k8s_customize_controller/pkg/apis/bolingcavalry/v1 is not in GOROOT (/usr/local/go/src/k8s_customize_controller/pkg/apis/bolingcavalry/v1)
I0122 01:19:34.881926   91884 main.go:82] Completed successfully.
Generating clientset for bolingcavalry:v1 at k8s_customize_controller/pkg/client/clientset
I0122 01:19:34.962776   91933 parse.go:383] importPackage k8s_customize_controller/pkg/apis/bolingcavalry/v1
I0122 01:19:34.962990   91933 parse.go:330] addDir k8s_customize_controller/pkg/apis/bolingcavalry/v1
I0122 01:19:35.010336   91933 parse.go:404] unable to import "k8s_customize_controller/pkg/apis/bolingcavalry/v1": package k8s_customize_controller/pkg/apis/bolingcavalry/v1 is not in GOROOT (/usr/local/go/src/k8s_customize_controller/pkg/apis/bolingcavalry/v1)
I0122 01:19:35.011372   91933 execute.go:232] Processing package "versioned", disk location "/usr/local/gopath/src/k8s_customize_controller/pkg/client/clientset/versioned"
I0122 01:19:35.011461   91933 execute.go:67] Assembling file "/usr/local/gopath/src/k8s_customize_controller/pkg/client/clientset/versioned/doc.go"
I0122 01:19:35.012521   91933 execute.go:67] Assembling file "/usr/local/gopath/src/k8s_customize_controller/pkg/client/clientset/versioned/clientset.go"
I0122 01:19:35.013109   91933 execute.go:232] Processing package "scheme", disk location "/usr/local/gopath/src/k8s_customize_controller/pkg/client/clientset/versioned/scheme"
I0122 01:19:35.013200   91933 execute.go:67] Assembling file "/usr/local/gopath/src/k8s_customize_controller/pkg/client/clientset/versioned/scheme/doc.go"
I0122 01:19:35.014022   91933 execute.go:67] Assembling file "/usr/local/gopath/src/k8s_customize_controller/pkg/client/clientset/versioned/scheme/register.go"
I0122 01:19:35.014325   91933 execute.go:232] Processing package "fake", disk location "/usr/local/gopath/src/k8s_customize_controller/pkg/client/clientset/versioned/fake"
I0122 01:19:35.014398   91933 execute.go:67] Assembling file "/usr/local/gopath/src/k8s_customize_controller/pkg/client/clientset/versioned/fake/doc.go"
I0122 01:19:35.014695   91933 execute.go:67] Assembling file "/usr/local/gopath/src/k8s_customize_controller/pkg/client/clientset/versioned/fake/clientset_generated.go"
I0122 01:19:35.014972   91933 execute.go:67] Assembling file "/usr/local/gopath/src/k8s_customize_controller/pkg/client/clientset/versioned/fake/register.go"
I0122 01:19:35.015263   91933 execute.go:232] Processing package "v1", disk location "/usr/local/gopath/src/k8s_customize_controller/pkg/client/clientset/versioned/typed/bolingcavalry/v1"
I0122 01:19:35.015395   91933 execute.go:67] Assembling file "/usr/local/gopath/src/k8s_customize_controller/pkg/client/clientset/versioned/typed/bolingcavalry/v1/doc.go"
I0122 01:19:35.016373   91933 execute.go:67] Assembling file "/usr/local/gopath/src/k8s_customize_controller/pkg/client/clientset/versioned/typed/bolingcavalry/v1/bolingcavalry_client.go"
I0122 01:19:35.016793   91933 execute.go:67] Assembling file "/usr/local/gopath/src/k8s_customize_controller/pkg/client/clientset/versioned/typed/bolingcavalry/v1/generated_expansion.go"
I0122 01:19:35.017044   91933 execute.go:232] Processing package "fake", disk location "/usr/local/gopath/src/k8s_customize_controller/pkg/client/clientset/versioned/typed/bolingcavalry/v1/fake"
I0122 01:19:35.017152   91933 execute.go:67] Assembling file "/usr/local/gopath/src/k8s_customize_controller/pkg/client/clientset/versioned/typed/bolingcavalry/v1/fake/doc.go"
I0122 01:19:35.017411   91933 execute.go:67] Assembling file "/usr/local/gopath/src/k8s_customize_controller/pkg/client/clientset/versioned/typed/bolingcavalry/v1/fake/fake_bolingcavalry_client.go"
Generating listers for bolingcavalry:v1 at k8s_customize_controller/pkg/client/listers
I0122 01:19:35.215918   91974 parse.go:383] importPackage k8s_customize_controller/pkg/apis/bolingcavalry/v1
I0122 01:19:35.215989   91974 parse.go:330] addDir k8s_customize_controller/pkg/apis/bolingcavalry/v1
I0122 01:19:35.266243   91974 parse.go:404] unable to import "k8s_customize_controller/pkg/apis/bolingcavalry/v1": package k8s_customize_controller/pkg/apis/bolingcavalry/v1 is not in GOROOT (/usr/local/go/src/k8s_customize_controller/pkg/apis/bolingcavalry/v1)
I0122 01:19:35.266328   91974 main.go:57] Completed successfully.
Generating informers for bolingcavalry:v1 at k8s_customize_controller/pkg/client/informers
I0122 01:19:35.368903   92007 parse.go:383] importPackage k8s_customize_controller/pkg/apis/bolingcavalry/v1
I0122 01:19:35.368969   92007 parse.go:330] addDir k8s_customize_controller/pkg/apis/bolingcavalry/v1
I0122 01:19:35.430186   92007 parse.go:404] unable to import "k8s_customize_controller/pkg/apis/bolingcavalry/v1": package k8s_customize_controller/pkg/apis/bolingcavalry/v1 is not in GOROOT (/usr/local/go/src/k8s_customize_controller/pkg/apis/bolingcavalry/v1)
I0122 01:19:35.430284   92007 main.go:60] Completed successfully.

there are one output unable to import "k8s_customize_controller/pkg/apis/bolingcavalry/v1": package k8s_customize_controller/pkg/apis/bolingcavalry/v1 is not in GOROOT (/usr/local/go/src/k8s_customize_controller/pkg/apis/bolingcavalry/v1) when create deepcopy file.

how to resolve this problem?

Hello. How do you predefine a type? You write them by yourself or use some generation tools?

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

/remove-lifecycle stale

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to this:

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.