fix(instrumentation-aws-sdk): Add traceparent to AWS SDK unsignableHeaders #1813
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Which problem is this PR solving?
This is an attempt to address the issue of a signature mismatch when a request fails and is retried. This happens because the instrumentation adds the
traceparent
header to outgoing headers. When a request fails, the value of the header changes, but the signature does not; and this results in an error.Fixes #1609 and open-telemetry/opentelemetry-js#3922
Short description of the changes
This change adds the
traceparent
header to the list of unsignable headers, so that it is excluded from creating the signature.