-
Notifications
You must be signed in to change notification settings - Fork 436
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
Move propagators and ID generators #244
Conversation
Looks good but let's wait for the discussion in open-telemetry/opentelemetry-specification#1047 to settle before we go either way |
O whoops. Didn't realize it was still an open discussion... |
@awiede actually it does seem likely that b3 for example should be moved. Think we should just merge this and potentially move some of them back if that is the decision? |
That works. If we do have to move them back I'd like to nest them under a trace mod and export like in #255. |
@awiede looks good, just have to update the imports 😬 |
017b616
to
56068cc
Compare
Move default W3 propagator implementation to SDK. Create a propagator and id_generator sub mod.
Move AWS X-Ray ID Generator from contrib to the SDK.
Move third party propagators from contrib to SDK.
56068cc
to
0eae9da
Compare
Fix rebase.
0eae9da
to
6670d6b
Compare
Yikes! That was a nasty rebase. I think I got it all fixed now. |
Resolves #235
trace_context_propagator
implementation tosdk
contrib
tosdk
id_generator
fromcontrbi
tosdk