🐛 (go/v4): Scaffold when no boilerplate file

[yyy1000]

Description

This pull request addresses issue #3373, which prevented kubebuilder from creating an API when no boilerplate file was present.
I have tested the changes locally with the following steps:

1. Rebuilt the Kubebuilder binary with updated code
2. Used Kubebuilder to initialize a new project
3. Deleted the 'boilerplate' file
4. Modified the 'generate' target in the Makefile as follows:

.PHONY: generate
generate: controller-gen ## Generate code containing DeepCopy, DeepCopyInto, and DeepCopyObject method implementations.
	$(CONTROLLER_GEN) object paths="./..."

5. Executed the 'create api' command.

Additionally, I tried to make some changes that enable the 'create api' command to modify the 'Makefile' when there's no boilerplate file and let the user skip step 4 altogether, making it possible to successfully run 'post-scaffold'(make generate). It seems not a little change, but I'm glad to do that if it is worth doing. :)

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: yyy1000 / name: Junhao Liu (8d67388)

[k8s-ci-robot]

Welcome @yyy1000!

It looks like this is your first PR to kubernetes-sigs/kubebuilder 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes-sigs/kubebuilder has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

[k8s-ci-robot]

Hi @yyy1000. Thanks for your PR.

I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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.

[varshaprasad96]

could we specifyically check for fileNotFound error and skip with errors.Is(err, afero.ErrFileNotFound). In case its something else (like permission issue), we can return the error.

[camilamacedo86]

+1 in in the above suggestion.

We need only to use an empty string when we know the file does not exist.

[yyy1000]

Thank you! It's very helpful. 😀 I made changes on this.

[camilamacedo86]

/ok-to-test

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: camilamacedo86, yyy1000

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [camilamacedo86]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[camilamacedo86]

//test pull-kubebuilder-e2e-k8s-1-24-7

[camilamacedo86]

Also,

/lgtm

Since address the Varsha suggestions either.

[camilamacedo86]

/pull-kubebuilder-e2e-k8s-1-24-7

[camilamacedo86]

/test pull-kubebuilder-e2e-k8s-1-24-7

[yyy1000]

/retest

[yyy1000]

/retest