-
Notifications
You must be signed in to change notification settings - Fork 544
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
Allow CRD updates with multiple owners #902
Allow CRD updates with multiple owners #902
Conversation
8d70ee7
to
1b6816f
Compare
This looks good but waiting on #878 ! |
1b6816f
to
e733473
Compare
/retest |
e733473
to
7576f79
Compare
7576f79
to
3470dea
Compare
/retest |
/test e2e-aws-upgrade |
1 similar comment
/test e2e-aws-upgrade |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
this looks good but I think a follow up with a unit test would be nice 👍
Currently CRD updates aren't done for existing CRDs, so this enables that functionality in the cases of: - New CRD is a different non-existing version - New CRD is the same version without an openapi schema change
3470dea
to
b5fde62
Compare
/test unit |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
Looks great!
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: ecordell, jpeeler 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 |
/retest |
2 similar comments
/retest |
/retest |
The purpose of this PR is to allow CRD updates for existing CRDs, which isn't currently done. This enables that functionality in the cases of:
This is rebased on top of #878, so that should merge first.