nicoloboschi opened a new pull request, #19290:
URL: https://github.com/apache/pulsar/pull/19290

   ### Motivation
   
   Regression of https://github.com/apache/pulsar/pull/11681
   
   In case of standalone functions worker, the pulsar client connected to the 
broker doesn't pick up the `brokerClientTrustCertsFilePath` configuration if 
authentication is disabled.
   
   This causes issues if `TlsEnableHostnameVerification=true` and the 
certificate is self signed.
   
   I don't think is much critical since non authenticated clusters are very 
rare when tls is enabled. 
   
   ### Modifications
   
   * Pass the `brokerClientTrustCertsFilePath` option if auth is disabled
   
   ### Verifying this change
   
   - [ ] Make sure that the change passes the CI checks.
   
   *(Please pick either of the following options)*
   
   This change is a trivial rework / code cleanup without any test coverage.
   
   *(or)*
   
   This change is already covered by existing tests, such as *(please describe 
tests)*.
   
   *(or)*
   
   This change added tests and can be verified as follows:
   
   *(example:)*
     - *Added integration tests for end-to-end deployment with large payloads 
(10MB)*
     - *Extended integration test for recovery after broker failure*
   
   ### Documentation
   
   <!-- DO NOT REMOVE THIS SECTION. CHECK THE PROPER BOX ONLY. -->
   
   - [ ] `doc` <!-- Your PR contains doc changes. Please attach the local 
preview screenshots (run `sh start.sh` at `pulsar/site2/website`) to your PR 
description, or else your PR might not get merged. -->
   - [ ] `doc-required` <!-- Your PR changes impact docs and you will update 
later -->
   - [x] `doc-not-needed` <!-- Your PR changes do not impact docs -->
   - [ ] `doc-complete` <!-- Docs have been already added -->
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to