Case-insensitive propagation style configuration #3299
Merged
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.
2.0 Upgrade Guide notes
The the values for the environment variables
DD_TRACE_PROPAGATION_STYLE
,DD_TRACE_PROPAGATION_STYLE_INJECT
, andDD_TRACE_PROPAGATION_STYLE_EXTRACT
are now considered case-insensitive.The major impact of this change is that, previously,
B3
would configure Tracing with the B3 Multiple Headers propagator. NowB3
will configure it with the B3 Single Header propagator.Motivation:
This change aligns the Ruby tracer with all other Datadog Tracers.
Additional Notes:
How to test the change?
For Datadog employees:
credentials of any kind, I've requested a review from
@DataDog/security-design-and-guidance
.Unsure? Have a question? Request a review!