Skip to content

Add Broker conformance spec#2598

Merged
knative-prow-robot merged 1 commit into
knative:masterfrom
grantr:broker-conformance-spec
Mar 3, 2020
Merged

Add Broker conformance spec#2598
knative-prow-robot merged 1 commit into
knative:masterfrom
grantr:broker-conformance-spec

Conversation

@grantr
Copy link
Copy Markdown
Contributor

@grantr grantr commented Feb 19, 2020

Add the Broker conformance spec to docs/spec. This is copied from the working document https://docs.google.com/document/d/1zjkaO_Nu6Zt4OmzBEmCMTBPj2JtGCSyYgGG5pVyLlBU.

Fixes #2306.

Proposed Changes

  • Add Broker conformance spec.

Release Note

Not a user-visible change.

@googlebot googlebot added the cla: yes Indicates the PR's author has signed the CLA. label Feb 19, 2020
@knative-prow-robot knative-prow-robot added the size/M Denotes a PR that changes 30-99 lines, ignoring generated files. label Feb 19, 2020
@knative-prow-robot knative-prow-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Feb 19, 2020
@akashrv akashrv added this to the v0.13.0 milestone Feb 19, 2020
Copy link
Copy Markdown
Contributor

@aslom aslom left a comment

Choose a reason for hiding this comment

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

We assume that the data plane characteristics are shared between Channels and Brokers?

Comment thread docs/spec/broker.md
Other versions MAY be rejected. The usage of CloudEvents version 1.0 is RECOMMENDED.

The Broker SHOULD NOT perform an upgrade of the produced event's CloudEvents version. It SHOULD support both Binary Content Mode and Structured Content Mode of the HTTP Protocol Binding for CloudEvents.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Comment thread docs/spec/broker.md
Delivered events must conform to the CloudEvents specification. All CloudEvent attributes set by the producer, including the data and specversion attributes, SHOULD be received at the subscriber identical to how they were received by the Broker.

The Broker SHOULD support delivering events via Binary Content Mode or Structured Content Mode of the HTTP Protocol Binding for CloudEvents.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

The same question as above about batched content mode support.

Comment thread docs/spec/broker.md
Events contained in delivery responses SHOULD be published to the Broker ingress and processed as if the event had been produced to the Broker's addressable endpoint.

The subscriber MAY receive a confirmation that a reply event was accepted by the Broker. If the reply event was not accepted, the initial event SHOULD be redelivered to the subscriber.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Copy link
Copy Markdown
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

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

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: grantr, matzew

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details 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 merged commit 135a805 into knative:master Mar 3, 2020
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/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.

Define Broker conformance

6 participants