-
Notifications
You must be signed in to change notification settings - Fork 888
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
Update the header name for otel baggage, and version date #981
Conversation
@bogdandrutu Are you sure this Fixes #879? The issue is about adopting the standard header name |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please add a changelog entry and a spec compliance matrix entry to keep track of implementations adopting the change.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
Signed-off-by: Bogdan Drutu <bogdandrutu@gmail.com>
db89781
to
3a5309a
Compare
@arminru "compliance matrix entry" no entries for baggage. I will add them in a separate PR |
@bogdandrutu I thought that the plan was to use 'baggage' rather than 'otelbaggage'? |
I was under the same impression @mtwo. |
Bah, missed that - sorry! Thanks @carlosalberto and @bogdandrutu ! |
…etry#981) Signed-off-by: Bogdan Drutu <bogdandrutu@gmail.com>
Signed-off-by: Bogdan Drutu bogdandrutu@gmail.com
Updates #879
Changes
For the moment still use a different name to protect against may possible breaking changes to the w3c baggage header.