feat: move jaeger tests to a separate package #403
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.
❓ Why is this being changed
jaeger is included in the module graph of downstream clients as an indirect dependency because of usage in otlp package.
(go module pruning doesn't seem to distinguish test files vs regular files 😢 )
APM Server output:
Related to elastic/apm-server#14768
🧑💻 What is being changed
move jaeger usage to a separate package along with testdata files
✅ How to validate the change
go test ./...
to ensure tests are passinggo mod tidy in apm-server to validate the dependency is removed