-
Notifications
You must be signed in to change notification settings - Fork 206
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
feat: webhook to set agent injection env var with odigos additions #2107
feat: webhook to set agent injection env var with odigos additions #2107
Conversation
instrumentor/internal/webhook_env_injector/webhook_env_injector.go
Outdated
Show resolved
Hide resolved
instrumentor/internal/webhook_env_injector/webhook_env_injector.go
Outdated
Show resolved
Hide resolved
instrumentor/internal/webhook_env_injector/webhook_env_injector.go
Outdated
Show resolved
Hide resolved
instrumentor/internal/webhook_env_injector/webhook_env_injector.go
Outdated
Show resolved
Hide resolved
instrumentor/internal/webhook_env_injector/webhook_env_injector.go
Outdated
Show resolved
Hide resolved
instrumentor/internal/webhook_env_injector/webhook_env_injector.go
Outdated
Show resolved
Hide resolved
instrumentor/internal/webhook_env_injector/webhook_env_injector.go
Outdated
Show resolved
Hide resolved
67512da
to
d5924cc
Compare
instrumentor/internal/webhook_env_injector/webhook_env_injector.go
Outdated
Show resolved
Hide resolved
Would you please update the test cases re:reported-name like I did in 8b60b1d ? You can probably just cherry pick that commit |
594b83a
to
b01a9dc
Compare
|
The original test used the same resource names for 2 runs of traffic generation. So the first time it would generate 13 spans and then 13 more. But now the test updates the reported-name after the first set is generated, so the new set of spans is just 13 entirely new resources. |
5770291
to
f67f0ba
Compare
Done, the requested commit has been cherry-picked. |
This is the initial phase of enabling the webhook to set agent injection-related environment variables (e.g., PYTHONPATH). The plan is to merge this after the migration and the new runtime inspection have been running for a while.
Once enough time has passed, I will merge this change to handle simpler cases where the envOverwriter is not involved. After this phase runs for a sufficient period, we can fully remove the envOverwriter and rely solely on this logic.
Finally, we can clean up the remaining code related to the envOverwriter.