-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
[chore] Update Jaeger model import paths to use jaeger-idl v1 #37782
[chore] Update Jaeger model import paths to use jaeger-idl v1 #37782
Conversation
Signed-off-by: nabil salah <[email protected]>
@yurishkuro |
Yes |
Signed-off-by: nabil salah <[email protected]>
@yurishkuro |
Hello @Nabil-Salah, thanks for your contribution! To be able to move this PR forward, please sign the CLA. 👍 |
hello @crobert-1 i signed it now :D |
Signed-off-by: nabil salah <[email protected]>
can you run the workflow once again :D @yurishkuro @crobert-1 |
@Nabil-Salah while waiting for the merge, can you analyze what the remaining dependencies on /jaeger/ there are? I've seen while doing a review some remaining direct dependencies and curiously some indirect ones. |
@yurishkuro I came up with this report https://docs.google.com/document/d/11ITBz59augUHL40jzgPKzEULUEPKCUwChRDERt7zQAk/edit?usp=sharing |
thanks. I left a bunch of comments, seems like it still needs a decent amount of clean-up. Breaking dependency on the agent code would be the largest impact (Jaeger no longer uses agent code, we only kept it because of this dependency). |
🎉 🎉 🎉 |
Description
Link to tracking issue
jaegertracing/jaeger#6494
Testing
go test
Documentation