API-1835: make operator generations behave as a map list type#2029
Conversation
|
Hello @deads2k! Some important instructions when contributing to openshift/api: |
|
@deads2k: This pull request references API-1835 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the epic to target the "4.18.0" version, but no target version was set. DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository. |
|
/retest |
|
/hold need all PRs associated with #2030 to merge first. |
|
/hold cancel manually tested for storage operator. Most library-go operators now direct from api repo. /test all |
f0baae9 to
8abc53a
Compare
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: bertinatto, deads2k The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
@deads2k: all tests passed! Full PR test history. Your PR dashboard. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
|
[ART PR BUILD NOTIFIER] Distgit: ose-cluster-config-api |
|
as changing the type changes the merge strategy /lgtm |
This will allow coordination between different observers watching the various generations. For instance, what if you want to track different deployments.
Need to vendor into storage, auth, and openshift-apiserver to prove it works ok.
/assign @bertinatto @p0lyn0mial