[extension/headersetter] Add support for chaining with other auth extensions#44120
Conversation
|
Welcome, contributor! Thank you for your contribution to opentelemetry-collector-contrib. Important reminders:
A maintainer will review your pull request soon. Thank you for helping make OpenTelemetry better! |
1053dc1 to
6db40f9
Compare
|
cc: @eduardscaueru |
2d40009 to
0f31730
Compare
ac043ef to
fb99dab
Compare
|
@kushalShukla-web Can you run |
I ran make gotidy and also tried go mod tidy manually. No changes were produced, and the working tree is clean. Could you confirm if there’s any specific Go version or environment requirement? |
fbf0b36 to
4970186
Compare
Signed-off-by: Kushal Shukla <kushalshukla110@gmail.com>
4970186 to
8c5f705
Compare
Signed-off-by: Kushal Shukla <kushalshukla110@gmail.com>
f13c04a to
730b209
Compare
|
@VihasMakwana shall we merge this pr ? |
|
Thank you for your contribution @kushalShukla-web! 🎉 We would like to hear from you about your experience contributing to OpenTelemetry by taking a few minutes to fill out this survey. If you are getting started contributing, you can also join the CNCF Slack channel #opentelemetry-new-contributors to ask for guidance and get help. |
Description
This PR adds support for chaining the
headersetterextension with other authentication extensions (e.g., OAuth2).It introduces a new configuration parameter
additional_authin headersetter and ensures that the additional auth extension is started first using the Dependent interface.Link to tracking issue
Fixes #43935