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

Enhance DLQ CloudEvents with destination #5727

Conversation

travis-minke-sap
Copy link
Contributor

@travis-minke-sap travis-minke-sap commented Sep 13, 2021

Fixes #5726

Proposed Changes

  • 🎁 Enhance DLQ CloudEvents with destination or reply URL in new knativeerrordest extension attribute.

Pre-review Checklist

  • At least 80% unit test coverage
  • E2E tests for any new behavior (N/A)
  • Docs PR for any user-facing impact
  • Spec PR for any new API feature. (N/A)
  • Conformance test for any change to the spec (N/A)

Release Note

Dead Letter Sink CloudEvents from certain Channels will include the "ce-knativeerrordest" extension attribute indicating the original destination URL of the failed event.

Docs

See documentation PR #4228

@google-cla google-cla bot added the cla: yes Indicates the PR's author has signed the CLA. label Sep 13, 2021
@knative-prow-robot knative-prow-robot added size/M Denotes a PR that changes 30-99 lines, ignoring generated files. needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Sep 13, 2021
@knative-prow-robot
Copy link
Contributor

Hi @travis-minke-sap. 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.

@codecov
Copy link

codecov bot commented Sep 13, 2021

Codecov Report

Merging #5727 (fa606a4) into main (7266621) will increase coverage by 0.01%.
The diff coverage is 75.00%.

Impacted file tree graph

@@            Coverage Diff             @@
##             main    #5727      +/-   ##
==========================================
+ Coverage   82.68%   82.69%   +0.01%     
==========================================
  Files         200      200              
  Lines        6261     6265       +4     
==========================================
+ Hits         5177     5181       +4     
  Misses        750      750              
  Partials      334      334              
Impacted Files Coverage Δ
pkg/channel/message_dispatcher.go 79.03% <66.66%> (+0.51%) ⬆️
pkg/channel/attributes/knative_error.go 100.00% <100.00%> (ø)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 7266621...fa606a4. Read the comment docs.

@lionelvillard
Copy link
Member

lionelvillard commented Sep 13, 2021

/ok-to-test

Can you also add this new extension to the doc: https://knative.dev/docs/developer/eventing/event-delivery/? Already done

@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 Sep 13, 2021
@matzew
Copy link
Member

matzew commented Sep 15, 2021

/lgtm

@knative-prow-robot knative-prow-robot added the lgtm Indicates that a PR is ready to be merged. label Sep 15, 2021
@knative-prow-robot knative-prow-robot removed the lgtm Indicates that a PR is ready to be merged. label Sep 15, 2021
@knative-metrics-robot
Copy link

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

File Old Coverage New Coverage Delta
pkg/channel/message_dispatcher.go 86.6% 87.0% 0.3

Copy link
Member

@matzew matzew left a comment

Choose a reason for hiding this comment

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

/lgtm
/approve

@knative-prow-robot knative-prow-robot added the lgtm Indicates that a PR is ready to be merged. label Sep 15, 2021
@knative-prow-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: matzew, travis-minke-sap

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 Sep 15, 2021
@knative-prow-robot knative-prow-robot merged commit 21155e9 into knative:main Sep 15, 2021
@travis-minke-sap travis-minke-sap deleted the enhance-dlq-cloudevents-with-dest branch September 15, 2021 21:55
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. 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/M Denotes a PR that changes 30-99 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Enhance DLQ Messages With Destination URL
5 participants