Split (helm) generate-crds target

[erikgb]

This is the first step towards moving the CRD generation out of the helm module. Instead of using a temporary directory, I propose using the crds_dir directory directly. I wish there were a way to avoid recreating the directory each time.

[cert-manager-prow]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign erikgb for approval. For more information see the Code Review Process.

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

Details

Needs approval from an approver in each of these files:

• OWNERS

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

[erikgb]

/cc @inteon

[Copilot]

Pull request overview

This PR refactors the CRD generation process in the helm module by splitting the monolithic generate-crds target into two separate targets: generate-crds for basic CRD generation and generate-helm-crds for Helm-templated CRDs. This change removes the dependency on a temporary directory and generates CRDs directly to the final crds_dir location, simplifying the workflow and making it easier to move CRD generation out of the helm module in the future.

Changes:

• Split generate-crds into two targets: generate-crds (basic CRD generation) and generate-helm-crds (Helm-templated CRDs)
• Generate CRDs directly to crds_dir instead of using a temporary scratch directory
• Move the $(NEEDS_YQ) dependency from generate-crds to generate-helm-crds since YQ is only needed for Helm templating
• Update shared_generate_targets to register generate-helm-crds instead of generate-crds to maintain backward compatibility

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.