You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm finding two permutations of DD_PROPAGATION_STYLE_INJECT string being used throughout the documentation and the code:
A. DD_PROPAGATION_STYLE_INJECT
B. DD_PROPAGATION_INJECT_STYLE
From the Ruby documentation, I expected this library to parse the environment variable in permutation A. However, this library uses permutation B.
Our documentation is definitely mismatched with our implementation. I believe the correct course of action is to move Ruby to move to DD_PROPAGATION_STYLE_INJECT instead.
I'll double check with our team to find out what the desired environment variable name is.
I'm finding two permutations of
DD_PROPAGATION_STYLE_INJECT
string being used throughout the documentation and the code:A.
DD_PROPAGATION_STYLE_INJECT
B.
DD_PROPAGATION_INJECT_STYLE
From the Ruby documentation, I expected this library to parse the environment variable in permutation A. However, this library uses permutation B.
Go documentation mentions the use of permutation A which is consistent with the
dd-trace-go
source codeWhat do you think about updating the code to use permutation A (that'll be consistent with the documentation and other languages)?
extraction env var uses the wrong ordering as well.
The text was updated successfully, but these errors were encountered: