Skip to content
This repository has been archived by the owner on Jun 4, 2021. It is now read-only.

NatssChannel Dispatcher: prioritize finalizer removal #824

Merged

Conversation

nachtmaar
Copy link
Contributor

@nachtmaar nachtmaar commented Jan 13, 2020

Proposed Changes

  • Remove natsschannel finalizer as early as possible

  • Add simple test to validate that finalizer on natsschannel gets removed even though natss channel is not ready

  • Add NatssDispatcher interface

  • removed unreferenced toSubscriberStatus function

  • add typedef SubscriptionChannelMapping

  • Bumped code coverage to 83 % ( I din't see that code coverage job is optional :/ )

Release Note

Fix that natsschannel finalizer doesn't get removed

See also kyma-project/kyma#6792

@googlebot googlebot added the cla: yes Indicates the PR's author has signed the CLA. label Jan 13, 2020
@knative-prow-robot knative-prow-robot added the size/L Denotes a PR that changes 100-499 lines, ignoring generated files. label Jan 13, 2020
@knative-prow-robot
Copy link
Contributor

Hi @nachtmaar. Thanks for your PR.

I'm waiting for a knative member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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.

@knative-prow-robot knative-prow-robot added the needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. label Jan 13, 2020
@nachtmaar
Copy link
Contributor Author

/assign @Abd4llA

@googlebot
Copy link

We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for all the commit author(s) or Co-authors. If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login here to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google.
In order to pass this check, please resolve this problem and then comment @googlebot I fixed it.. If the bot doesn't comment, it means it doesn't think anything has changed.

ℹ️ Googlers: Go here for more info.

@googlebot googlebot added cla: no Indicates the PR's author has not signed the CLA. and removed cla: yes Indicates the PR's author has signed the CLA. labels Jan 13, 2020
@devguyio
Copy link
Contributor

/ok-to-test

@knative-prow-robot knative-prow-robot added ok-to-test Indicates a non-member PR verified by an org member that is safe to test. and removed needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Jan 13, 2020
@nachtmaar nachtmaar force-pushed the natss-prioritize-finalizer-removal branch from 7748a34 to c5df5ad Compare January 13, 2020 18:18
@googlebot
Copy link

All (the pull request submitter and all commit authors) CLAs are signed, but one or more commits were authored or co-authored by someone other than the pull request submitter.

We need to confirm that all authors are ok with their commits being contributed to this project. Please have them confirm that by leaving a comment that contains only @googlebot I consent. in this pull request.

Note to project maintainer: There may be cases where the author cannot leave a comment, or the comment is not properly detected as consent. In those cases, you can manually confirm consent of the commit author(s), and set the cla label to yes (if enabled on your project).

ℹ️ Googlers: Go here for more info.

@nachtmaar nachtmaar force-pushed the natss-prioritize-finalizer-removal branch from c5df5ad to 2ac81c6 Compare January 13, 2020 19:08
@googlebot
Copy link

CLAs look good, thanks!

ℹ️ Googlers: Go here for more info.

Copy link
Contributor

@antoineco antoineco left a comment

Choose a reason for hiding this comment

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

Only minor comments, good job!

natss/pkg/dispatcher/dispatcher.go Show resolved Hide resolved
natss/pkg/dispatcher/dispatcher.go Show resolved Hide resolved
natss/pkg/dispatcher/testing/testing.go Outdated Show resolved Hide resolved
natss/pkg/dispatcher/dispatcher.go Outdated Show resolved Hide resolved
natss/pkg/dispatcher/testing/testing.go Outdated Show resolved Hide resolved
natss/pkg/reconciler/dispatcher/natsschannel_test.go Outdated Show resolved Hide resolved
natss/pkg/reconciler/dispatcher/natsschannel_test.go Outdated Show resolved Hide resolved
natss/pkg/reconciler/dispatcher/natsschannel_test.go Outdated Show resolved Hide resolved
natss/pkg/reconciler/dispatcher/natsschannel.go Outdated Show resolved Hide resolved
@antoineco
Copy link
Contributor

/lgtm

@knative-prow-robot knative-prow-robot added the lgtm Indicates that a PR is ready to be merged. label Jan 16, 2020
@nachtmaar
Copy link
Contributor Author

/test pull-knative-eventing-contrib-integration-tests

@knative-prow-robot knative-prow-robot removed the lgtm Indicates that a PR is ready to be merged. label Jan 17, 2020
@k15r
Copy link

k15r commented Jan 20, 2020

/lgtm

@knative-prow-robot
Copy link
Contributor

@k15r: changing LGTM is restricted to collaborators

In response to this:

/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.

@knative-metrics-robot
Copy link

The following is the coverage report on the affected files.
Say /test pull-knative-eventing-contrib-go-coverage to re-run this coverage report

File Old Coverage New Coverage Delta
natss/pkg/reconciler/dispatcher/natsschannel.go Do not exist 83.3%

@nachtmaar
Copy link
Contributor Author

/test pull-knative-eventing-contrib-integration-tests

@k15r
Copy link

k15r commented Jan 20, 2020

/lgtm

@knative-prow-robot
Copy link
Contributor

@k15r: changing LGTM is restricted to collaborators

In response to this:

/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.

@antoineco
Copy link
Contributor

/lgtm

@knative-prow-robot knative-prow-robot added the lgtm Indicates that a PR is ready to be merged. label Jan 20, 2020
@devguyio
Copy link
Contributor

/approve

@knative-prow-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: Abd4llA, k15r, nachtmaar

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

@knative-prow-robot knative-prow-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jan 20, 2020
@knative-prow-robot knative-prow-robot merged commit b62e9b3 into knative:master Jan 20, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. cla: yes Indicates the PR's author has signed the CLA. lgtm Indicates that a PR is ready to be merged. ok-to-test Indicates a non-member PR verified by an org member that is safe to test. 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.

8 participants