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

🤖 Triggering CI on branch 'release-next' after synching to upstream/main #514

Merged
merged 1 commit into from
Dec 29, 2021

Conversation

serverless-qe
Copy link
Collaborator

No description provided.

@openshift-ci
Copy link

openshift-ci bot commented Dec 29, 2021

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: serverless-qe
To complete the pull request process, please assign matzew after the PR has been reviewed.
You can assign the PR to them by writing /assign @matzew in a comment when ready.

The full list of commands accepted by this bot can be found 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

@serverless-qe
Copy link
Collaborator Author

OCF Webhook is merging this PR

@serverless-qe serverless-qe merged commit 63714ec into release-next Dec 29, 2021
ReToCode pushed a commit to ReToCode/eventing-kafka that referenced this pull request Jan 3, 2023
…nshift-knative#514)

* Do a rolling deployment of Kafka dispatcher when configmap is changed

* Adjust tests, add nil check for annotations map

* Rename annotation key

* Extract test configmaphash value into a constant

* Fix Kafka channel tests

* Fix wrong annotation on dispatcher deployment

* Add unit tests

* Address comments

* Unit tests for configmap checksum

* Fix test case name

* goimports
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant