-
Notifications
You must be signed in to change notification settings - Fork 3.7k
[pulsar-client-tools] add tls truststore and hn-verification option to argument #6742
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
Conversation
|
/pulsarbot run-failure-checks |
| String tlsTrustCertsFilePath; | ||
|
|
||
| @Parameter(names = { "--tls-allow-insecure" }, description = "Allow TLS insecure connection") | ||
| Boolean tlsAllowInsecureConnection = null; |
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.
This is a boxed value.
I think you need to change the value assignments in PulsarClientTool constructor.
this.tlsAllowInsecureConnection = Boolean
.parseBoolean(properties.getProperty("tlsAllowInsecureConnection", "false"));
this.tlsEnableHostnameVerification = Boolean
.parseBoolean(properties.getProperty("tlsEnableHostnameVerification", "false"));
this.tlsTrustCertsFilePath = properties.getProperty("tlsTrustCertsFilePath");
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.
yes, that's correct. I fixed it.
|
@rdhabalia Could you please take a look at sijie's comments? |
|
move to 2.7.0 first. |
|
Closed as stale and conflict. Please rebase and resubmit the patch if it's still relevant. |
Motivation
Allow configure
tlsTrustCertsFilePathtlsAllowInsecureConnectiontlsEnableHostnameVerificationusing CLI argument in pulsar-client tools.