-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
[exporter/signalfxexporter] allow user to add their own CA to the cert pool #16250
Conversation
yes, I can make that change. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
few nits, otherwise LGTM
@dloucasfx please take a look at the failing tests |
It's a difference in error message between golang 1.19 (the version I developed with) and 1.18 where the CI is failing. 1.18 error:
1.19 error:
I used regex instead of contains and this |
Signed-off-by: Dani Louca <dlouca@splunk.com>
Co-authored-by: Dmitrii Anoshin <anoshindx@gmail.com>
Co-authored-by: Dmitrii Anoshin <anoshindx@gmail.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks like github-action re-requested a review from you @dmitryax, can you confirm this is still good? I'm not sure what triggered the action after your approval 🤔
Maybe because of additional commits after that. It's good to merge |
…t pool (open-telemetry#16250) Adding new feature to allow the user to add their own CA to the ingest and api client cert pool. This is needed when the exporter is pointing to a TLS enabled signalfx receiver or/and TLS enabled http_forwarder and the CA is not in the system cert pool (ex: agent <--> GW setup) Signed-off-by: Dani Louca <dlouca@splunk.com> Co-authored-by: Dmitrii Anoshin <anoshindx@gmail.com>
…t pool (open-telemetry#16250) Adding new feature to allow the user to add their own CA to the ingest and api client cert pool. This is needed when the exporter is pointing to a TLS enabled signalfx receiver or/and TLS enabled http_forwarder and the CA is not in the system cert pool (ex: agent <--> GW setup) Signed-off-by: Dani Louca <dlouca@splunk.com> Co-authored-by: Dmitrii Anoshin <anoshindx@gmail.com>
Signed-off-by: Dani Louca dlouca@splunk.com
Description:
Adding new feature to allow the user to add their own CA to the ingest and api client cert pool.
This is needed when the exporter is pointing to a TLS enabled signalfx receiver or/and TLS enabled http_forwarder
and the CA is not in the system cert pool (ex: agent <--> GW setup)
Testing:
Unit test and manual validation
Documentation:
ingest_ca_file
andapi_url
can be used to set the absolute path to the CA file.This is needed when the exporter is pointing to a TLS enabled signalfx receiver or/and TLS enabled http_forwarder
and the CA is not in the system cert pool