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

Allow CRD updates with multiple owners #902

Merged

Conversation

jpeeler
Copy link

@jpeeler jpeeler commented Jun 11, 2019

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:

  • New CRD is a different non-existing version
  • CRD is the same version without an openapi schema change

This is rebased on top of #878, so that should merge first.

@openshift-ci-robot openshift-ci-robot added approved Indicates a PR has been approved by an approver from all required OWNERS files. size/XL Denotes a PR that changes 500-999 lines, ignoring generated files. labels Jun 11, 2019
@jpeeler jpeeler force-pushed the crd-schema-change branch from 8d70ee7 to 1b6816f Compare June 14, 2019 18:25
@ecordell
Copy link
Member

This looks good but waiting on #878 !

@openshift-ci-robot openshift-ci-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jun 17, 2019
@jpeeler jpeeler force-pushed the crd-schema-change branch from 1b6816f to e733473 Compare June 20, 2019 19:21
@openshift-ci-robot openshift-ci-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jun 20, 2019
@jpeeler
Copy link
Author

jpeeler commented Jun 20, 2019

/retest

test/e2e/installplan_e2e_test.go Outdated Show resolved Hide resolved
test/e2e/installplan_e2e_test.go Outdated Show resolved Hide resolved
@jpeeler jpeeler force-pushed the crd-schema-change branch from e733473 to 7576f79 Compare June 25, 2019 00:20
@openshift-ci-robot openshift-ci-robot added size/L Denotes a PR that changes 100-499 lines, ignoring generated files. and removed size/XL Denotes a PR that changes 500-999 lines, ignoring generated files. labels Jun 25, 2019
@jpeeler jpeeler force-pushed the crd-schema-change branch from 7576f79 to 3470dea Compare June 27, 2019 19:32
@jpeeler
Copy link
Author

jpeeler commented Jun 28, 2019

/retest

@jpeeler
Copy link
Author

jpeeler commented Jun 28, 2019

/test e2e-aws-upgrade

1 similar comment
@jpeeler
Copy link
Author

jpeeler commented Jun 29, 2019

/test e2e-aws-upgrade

Copy link
Member

@ecordell ecordell left a 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 👍

pkg/controller/operators/catalog/operator.go Show resolved Hide resolved
test/e2e/installplan_e2e_test.go Outdated Show resolved Hide resolved
test/e2e/installplan_e2e_test.go Outdated Show resolved Hide resolved
@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Jul 1, 2019
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
@jpeeler jpeeler force-pushed the crd-schema-change branch from 3470dea to b5fde62 Compare July 3, 2019 20:57
@openshift-ci-robot openshift-ci-robot removed the lgtm Indicates that a PR is ready to be merged. label Jul 3, 2019
@jpeeler
Copy link
Author

jpeeler commented Jul 3, 2019

/test unit

Copy link
Member

@ecordell ecordell left a comment

Choose a reason for hiding this comment

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

/lgtm

Looks great!

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Jul 8, 2019
@openshift-ci-robot
Copy link
Collaborator

[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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@jpeeler
Copy link
Author

jpeeler commented Jul 9, 2019

/retest

2 similar comments
@jpeeler
Copy link
Author

jpeeler commented Jul 9, 2019

/retest

@dinhxuanvu
Copy link
Member

/retest

@openshift-merge-robot openshift-merge-robot merged commit af9b90d into operator-framework:master Jul 10, 2019
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. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants