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

Fix Channel Data plane spec #3361

Merged
merged 2 commits into from
Jun 23, 2020

Conversation

slinkydeveloper
Copy link
Contributor

  • Removed DTE specification to force the trace propagation. Reworked Distributed Tracing Extension cloudevents/spec#607 tl;dr there were changes in the CE spec lately, now in channels we use only the w3c tracecontext.
  • Specified that the channel internally may use the mechanism it wants to propagate trace from sender to receiver, as soon the output receiver then sends it using w3c tracecontext.
  • Added knativehistory extension
  • Specified that the channel may change the http message mode from sender to subscribers

Signed-off-by: Francesco Guardiani francescoguard@gmail.com

Added knativehistory thing

Signed-off-by: Francesco Guardiani <francescoguard@gmail.com>
@googlebot googlebot added the cla: yes Indicates the PR's author has signed the CLA. label Jun 22, 2020
@knative-prow-robot knative-prow-robot added the size/M Denotes a PR that changes 30-99 lines, ignoring generated files. label Jun 22, 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 Jun 22, 2020
The Channel SHOULD sample and write traces to the location specified in
The Channel MUST recognize and pass through all tracing information from sender
to subscribers using [W3C Tracecontext](https://w3c.github.io/trace-context/),
although internally It MAY use another mechanism(s) to propagate the tracing
Copy link
Member

@lberk lberk Jun 22, 2020

Choose a reason for hiding this comment

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

... internally It MAY ...

lower case 'i' in it

Signed-off-by: Francesco Guardiani <francescoguard@gmail.com>
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

thanks for updating this @slinkydeveloper

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

[APPROVALNOTIFIER] This PR is APPROVED

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

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:
  • OWNERS [matzew,slinkydeveloper]

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 e1e5e1a into knative:master Jun 23, 2020
lberk pushed a commit to lberk/eventing that referenced this pull request Jun 26, 2020
* Removed DTE spec
Added knativehistory thing

Signed-off-by: Francesco Guardiani <francescoguard@gmail.com>

* nit

Signed-off-by: Francesco Guardiani <francescoguard@gmail.com>
@lberk lberk mentioned this pull request Sep 1, 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.

5 participants