Skip to content
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

project: kubebuilder layout v3 -> v4 #1160

Merged
merged 1 commit into from
Jan 27, 2025

Conversation

ffromani
Copy link
Member

@ffromani ffromani commented Jan 23, 2025

We have no good reason to get stuck on layout v3 and make our time harder when consuming upcoming changes and fixes.

Most of the changes here stem from the fact we change the path of the API package.
We also consume as much as possible from the new Makefile features.

Done using https://book.kubebuilder.io/migration/migration_guide_gov3_to_gov4

@openshift-ci openshift-ci bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Jan 23, 2025
@ffromani
Copy link
Member Author

expected to fail in multiple lanes

@openshift-ci openshift-ci bot requested review from mrniranjan and shajmakh January 23, 2025 13:03
@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jan 23, 2025
@ffromani ffromani force-pushed the project-migrate-v3-to-v4 branch 2 times, most recently from 118b628 to 120a3b5 Compare January 23, 2025 14:28
@ffromani
Copy link
Member Author

should not be horribly broken anymore

@ffromani ffromani force-pushed the project-migrate-v3-to-v4 branch 6 times, most recently from 43aae27 to d206124 Compare January 24, 2025 14:41
@ffromani
Copy link
Member Author

/retest-required

@ffromani ffromani force-pushed the project-migrate-v3-to-v4 branch 3 times, most recently from d2255a1 to 0ffa6aa Compare January 27, 2025 08:01
We have no good reason to get stuck on layout v3 and
make our time harder when consuming upcoming changes and fixes.

Most of the changes here stem from the fact we change
the path of the API package.
We also consume as much as possible from the new Makefile features.

done using https://book.kubebuilder.io/migration/migration_guide_gov3_to_gov4

Signed-off-by: Francesco Romani <[email protected]>
@ffromani ffromani force-pushed the project-migrate-v3-to-v4 branch from 0ffa6aa to 643c760 Compare January 27, 2025 13:10
@ffromani ffromani changed the title WIP: project: kubebuilder layout v3 -> v4 project: kubebuilder layout v3 -> v4 Jan 27, 2025
@openshift-ci openshift-ci bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Jan 27, 2025
@ffromani
Copy link
Member Author

/cc @Tal-or

@openshift-ci openshift-ci bot requested a review from Tal-or January 27, 2025 13:10
Copy link
Collaborator

@Tal-or Tal-or left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jan 27, 2025
Copy link
Contributor

openshift-ci bot commented Jan 27, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ffromani, Tal-or

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:

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

@openshift-merge-bot openshift-merge-bot bot merged commit e89fc3e into main Jan 27, 2025
15 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants