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

Propose retry channel behavior #1617

Merged

Conversation

lionelvillard
Copy link
Member

@lionelvillard lionelvillard commented Aug 1, 2019

Proposed Changes

  • Channel retry recommendation

@matzew @Harwayne @alanconway @aslom comments?

@googlebot googlebot added the cla: yes Indicates the PR's author has signed the CLA. label Aug 1, 2019
@knative-prow-robot knative-prow-robot added the size/S Denotes a PR that changes 10-29 lines, ignoring generated files. label Aug 1, 2019

Channels SHOULD retry resending CloudEvents when they fail to either connect or send CloudEvents to subscribers.

Channels SHOULD support various retry configuration parameters, including, but not limiting to:
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
Channels SHOULD support various retry configuration parameters, including, but not limiting to:
Channels SHOULD support various retry configuration parameters, including, but not limited to:

Copy link
Member Author

Choose a reason for hiding this comment

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

fixed. (didn't see the commit suggestion button. Next time!)

Copy link
Contributor

Choose a reason for hiding this comment

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

Probably for the best, I think the CLA bot doesn't like it when you accept the suggestions (as they are attributed to the suggester).

Copy link
Contributor

@Harwayne Harwayne 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 Aug 1, 2019
@knative-prow-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: Harwayne, lionelvillard

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 Aug 1, 2019
@knative-prow-robot knative-prow-robot merged commit 4da4938 into knative:master Aug 1, 2019
@lionelvillard lionelvillard deleted the propose-channel-retry branch January 20, 2020 14:59
@lionelvillard lionelvillard restored the propose-channel-retry branch September 3, 2020 15:41
@lionelvillard lionelvillard deleted the propose-channel-retry branch September 3, 2020 15:41
aliok pushed a commit to aliok/eventing that referenced this pull request Feb 15, 2022
Signed-off-by: Pierangelo Di Pilato <pierdipi@redhat.com>

Co-authored-by: Pierangelo Di Pilato <pierdipi@redhat.com>
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. size/S Denotes a PR that changes 10-29 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants