Skip to content

Conversation

perdasilva
Copy link
Contributor

Description

This PR updates the CatalogSource spec.grpcPodConfig.priorityClassName to be a *string. The main motivation being that empty string has meaning for this attribute so we need to distinguish whether it was set by the user or not.

@perdasilva
Copy link
Contributor Author

/assign @estroz

@timflannagan
Copy link
Member

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Dec 10, 2021
@openshift-ci openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label Dec 10, 2021
@estroz
Copy link
Member

estroz commented Dec 10, 2021

What's the difference between "" and unset?

Overall I think this is fine because most consumers define their CatalogSource's via yaml configs, so this doesn't affect most people.

@perdasilva
Copy link
Contributor Author

if they leave it unset it, nothing will happen. If they set it to "", then we'll set it to "" in the pod, basically. I'll fix the protobuf tags!!

Signed-off-by: Per G. da Silva <perdasilva@redhat.com>
@estroz
Copy link
Member

estroz commented Dec 10, 2021

Sounds good. Lets see if I can get prow to override go-apidiff

/override Go/go-apidiff
/approve
/lgtm

@openshift-ci
Copy link

openshift-ci bot commented Dec 10, 2021

@estroz: /override requires a failed status context or a job name to operate on.
The following unknown contexts were given:

  • Go/go-apidiff

Only the following contexts were expected:

  • Build
  • tide
  • verify

In response to this:

Sounds good. Lets see if I can get prow to override go-apidiff

/override Go/go-apidiff
/approve
/lgtm

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 kubernetes/test-infra repository.

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Dec 10, 2021
@openshift-ci
Copy link

openshift-ci bot commented Dec 10, 2021

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: estroz, perdasilva

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-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Dec 10, 2021
@estroz
Copy link
Member

estroz commented Dec 10, 2021

/override tide

@openshift-ci
Copy link

openshift-ci bot commented Dec 10, 2021

@estroz: Overrode contexts on behalf of estroz: tide

In response to this:

/override tide

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 kubernetes/test-infra repository.

@estroz
Copy link
Member

estroz commented Dec 10, 2021

/override go-apidiff

@openshift-ci
Copy link

openshift-ci bot commented Dec 10, 2021

@estroz: /override requires a failed status context or a job name to operate on.
The following unknown contexts were given:

  • go-apidiff

Only the following contexts were expected:

  • Build
  • tide
  • verify

In response to this:

/override go-apidiff

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 kubernetes/test-infra repository.

@estroz
Copy link
Member

estroz commented Dec 10, 2021

Merging by hand

@estroz estroz merged commit 6897e9a into operator-framework:master Dec 10, 2021
corev1 "k8s.io/api/core/v1"
metav1 "k8s.io/apimachinery/pkg/apis/meta/v1"
"k8s.io/apimachinery/pkg/types"
"time"
Copy link
Member

Choose a reason for hiding this comment

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

Interesting - I'm surprised the format check didn't complain about this but I guess gofmt might no care about import ordering/chunking/etc.?

Copy link
Member

Choose a reason for hiding this comment

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

It doesn't have an opinion about std vs. external module chunking, just sorts within chunks. goimports does care i think.

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.

3 participants