feat: add w3c headers#46
Conversation
|
this repo is using changesets, I thought? PR might need a changeset file |
|
The changeset bot was removed from the repo for some reason. I've enabled it as of now. I'll request rebase to check if it runs. UPDATE: Changeset bot was run on rebase and posted comment below |
…aceparent, getTracestate, and getBaggage methods covering the happy path, undefined when absent, and protection against modification of the new protected keys.
6e85292 to
e6024e5
Compare
🦋 Changeset detectedLatest commit: a7c6e9d The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
trivikr
left a comment
There was a problem hiding this comment.
This needs a changeset file. This should be a minor bump since new APIs are being added.
… documentation for getTraceparent, getTracestate, and getBaggage. Update the global singleton spec to verify w3c fields are accessible through the existing instance mock pattern.
Added the changeset and some more tests. |
Description of changes:
Add W3C distributed tracing support to
aws-lambda-invoke-store. This introduces three new protected context fields and their corresponding read-only accessors:getTraceparent()— W3C Trace ContexttraceparentheadergetTracestate()— W3C Trace ContexttracestateheadergetBaggage()— W3C Baggage headerThese fields follow the same immutability contract as the existing
REQUEST_IDandX_RAY_TRACE_IDkeys: they are set once viarun()and cannot be modified by user code afterwards.Testing:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.