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

feat(make): adds generate to default targets #1176

Merged

Conversation

bartoszmajsak
Copy link
Contributor

@bartoszmajsak bartoszmajsak commented Aug 13, 2024

Description

The current list of default targets includes manifests which generates CRDs based on API code changes. Still, it does not invoke generate which is responsible for generating additional code (namely DeepCopy funcs).

This can result in incomplete implementation where CRDs reflect the latest changes in the API, but internally it might not be possible to use due to missing copy methods or even outdated implementations of those that already exist.

This change adds it to the list of default targets so that each code change can be committed with the complete set of changes for controller-runtime.

How Has This Been Tested?

Screenshot or short clip

Merge criteria

  • You have read the contributors guide.
  • Commit messages are meaningful - have a clear and concise summary and detailed explanation of what was changed and why.
  • Pull Request contains a description of the solution, a link to the JIRA issue, and to any dependent or related Pull Request.
  • Testing instructions have been added in the PR body (for PRs involving changes that are not immediately obvious).
  • The developer has manually tested the changes and verified that the changes work

Current list of default targets include `manifests` which generates
CRDs based on API code changes, but does not invoke `generate` which is
responsible for generating additional code (namely `DeepCopy` funcs).

This can result in incomplete implemetation where CRDs reflect latest
changes in the API, but internally it might not be possible to use due
to missing copy methods or even outdated implementations of those that
already exist.

This change adds it to the list of default targets so that each code
change can be committed with complete set of changes for controller-runtime.
@openshift-ci openshift-ci bot requested review from grdryn and ykaliuta August 13, 2024 15:54
@bartoszmajsak
Copy link
Contributor Author

Alternatively we can combine both to one generate target.

Copy link

openshift-ci bot commented Aug 13, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: zdtsw

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 4a51dfd into opendatahub-io:incubation Aug 13, 2024
8 checks passed
zdtsw pushed a commit to zdtsw-forking/rhods-operator that referenced this pull request Aug 15, 2024
Current list of default targets include `manifests` which generates
CRDs based on API code changes, but does not invoke `generate` which is
responsible for generating additional code (namely `DeepCopy` funcs).

This can result in incomplete implemetation where CRDs reflect latest
changes in the API, but internally it might not be possible to use due
to missing copy methods or even outdated implementations of those that
already exist.

This change adds it to the list of default targets so that each code
change can be committed with complete set of changes for controller-runtime.

(cherry picked from commit 4a51dfd)
openshift-merge-bot bot pushed a commit to red-hat-data-services/rhods-operator that referenced this pull request Aug 16, 2024
Current list of default targets include `manifests` which generates
CRDs based on API code changes, but does not invoke `generate` which is
responsible for generating additional code (namely `DeepCopy` funcs).

This can result in incomplete implemetation where CRDs reflect latest
changes in the API, but internally it might not be possible to use due
to missing copy methods or even outdated implementations of those that
already exist.

This change adds it to the list of default targets so that each code
change can be committed with complete set of changes for controller-runtime.

(cherry picked from commit 4a51dfd)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

2 participants