🐛 Allow 'kubebuilder alpha generate' rescaffolds work with no longer supported/available plugins ( go/v3 and go/v2 )

[sarthaksarthak9]

Fixes: #4433

• Fixed issue where 'kubebuilder alpha generate' failed if PROJECT contained go.kubebuilder.io/v3.
• Automatically updates outdated plugin references (v2, v3 → v4) to support scaffolding.
• Added a warning to notify users before modifying the PROJECT file.
• Added test to validate changes automatically

[k8s-ci-robot]

Hi @sarthaksarthak9. 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-sigs/prow repository.

[camilamacedo86]

Really great job 🥇 🎉
I added some comments, and I think we need to add a test for this case.
Otherwise, it is all amazing !!!

[sarthaksarthak9]

@camilamacedo86 I noticed that updating the plugin list in getInitArgs() automatically updates the PROJECT file, even though I don’t explicitly see a save function. How is this happening? Could you help me confirm where the file update is triggered?. Also, is there still a need for updateProjectFileForAlphaGenerate() in this case?

[camilamacedo86]

Hi @sarthaksarthak9

@camilamacedo86 could you pls review the changes ?

Thank you a lot for your contribution, but it's still not working.
Did you try test it locally? See my comment with the steps at: #4572 (comment)

Following my latest test (done today):

 $ make install
go build -ldflags " -X sigs.k8s.io/kubebuilder/v4/cmd.kubeBuilderVersion=v4.5.0-75-g7dc69ec18 -X sigs.k8s.io/kubebuilder/v4/cmd.goos=darwin -X sigs.k8s.io/kubebuilder/v4/cmd.goarch=arm64 -X sigs.k8s.io/kubebuilder/v4/cmd.gitCommit=7dc69ec1870460375e2d28f28aeeeb3854cfa59f -X sigs.k8s.io/kubebuilder/v4/cmd.buildDate=2025-03-13T16:30:31Z " -o bin/kubebuilder
rm -f /Users/camilam/go/bin/kubebuilder
cp ./bin/kubebuilder /Users/camilam/go/bin/kubebuilder

cd testdata/project-v4
$ vim PROJECT (I edit to be v3)

$ kubebuilder alpha generate
Error: no plugin could be resolved with key "go.kubebuilder.io/v3" for project version "3"
Usage:
  kubebuilder [flags]

Examples:
The first step is to initialize your project:
    kubebuilder init [--plugins=<PLUGIN KEYS> [--project-version=<PROJECT VERSION>]]

<PLUGIN KEYS> is a comma-separated list of plugin keys from the following table
and <PROJECT VERSION> a supported project version for these plugins.

                             Plugin keys | Supported project versions
-----------------------------------------+----------------------------
               base.go.kubebuilder.io/v4 |                          3
 deploy-image.go.kubebuilder.io/v1-alpha |                          3
                    go.kubebuilder.io/v4 |                          3
         grafana.kubebuilder.io/v1-alpha |                          3
            helm.kubebuilder.io/v1-alpha |                          3
      kustomize.common.kubebuilder.io/v2 |                          3

For more specific help for the init command of a certain plugins and project version
configuration please run:
    kubebuilder init --help --plugins=<PLUGIN KEYS> [--project-version=<PROJECT VERSION>]

Default plugin keys: "go.kubebuilder.io/v4"
Default project version: "3"


Flags:
  -h, --help                     help for kubebuilder
      --plugins strings          plugin keys to be used for this subcommand execution
      --project-version string   project version (default "3")

FATA no plugin could be resolved with key "go.kubebuilder.io/v3" for project version "3" 

Did you push all your changes?

[sarthaksarthak9]

@camilamacedo86 Apologies for the oversight! I only had updated the description with the output earlier but forgot to push the changes. Changes are working I tested it locally.

[camilamacedo86]

Hi @sarthaksarthak9,

Thank you so much for your contribution! I think something might be missing from your previous work because, when I tested your changes locally, it still didn’t work as expected.

What do you think about adding tests to ensure this scenario is automatically validated? See: #4572 (comment)

Looking forward to your thoughts!

[camilamacedo86]

Hi @sarthaksarthak9,

Thank you so much for working on this fix!
The test will help us validate that everything is working correctly.

Also, I hope you don’t mind, but I updated the title because we use the emoji and description to generate the release notes. Since it’s a bug, I just tried to clarify it a bit better.

Thanks again!

[camilamacedo86]

/lgtm
/approve
/ok-to-test

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

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

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-30-8