tls.hostnameVerification=false now logs a WARN when the transport is built. No validation gate: certificate chain checks still apply, and configs that set it deliberately keep working.
Username, password, tls.caCertificatePath, tls.trustStorePath and tls.keyStorePath must resolve to content. Null, empty and blank count as missing, and the error names the field plus the ${...} reference, never a resolved value. This replaces "Failed to create OpenSearch transport: null".
opensearchUrl with userinfo (https://u:p@host or https://u@host) is a validation error; the message does not echo the credentials.
Testing
New OpenSearchTransportFactoryTest (empty, blank and unset references for BASIC credentials and each TLS path; hostname warning via QCollectingLogger) and a userinfo case in QuickSearchQBitConfigValidationTest. All failed before the fix.
CI=true ./mvnw verify: 312 unit and 18 integration tests pass, JaCoCo checks met.
## Summary
- `tls.hostnameVerification=false` now logs a WARN when the transport is built. No validation gate: certificate chain checks still apply, and configs that set it deliberately keep working.
- Username, password, `tls.caCertificatePath`, `tls.trustStorePath` and `tls.keyStorePath` must resolve to content. Null, empty and blank count as missing, and the error names the field plus the `${...}` reference, never a resolved value. This replaces "Failed to create OpenSearch transport: null".
- `opensearchUrl` with userinfo (`https://u:p@host` or `https://u@host`) is a validation error; the message does not echo the credentials.
## Testing
- New `OpenSearchTransportFactoryTest` (empty, blank and unset references for BASIC credentials and each TLS path; hostname warning via `QCollectingLogger`) and a userinfo case in `QuickSearchQBitConfigValidationTest`. All failed before the fix.
- `CI=true ./mvnw verify`: 312 unit and 18 integration tests pass, JaCoCo checks met.
Closes #15
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Summary
tls.hostnameVerification=falsenow logs a WARN when the transport is built. No validation gate: certificate chain checks still apply, and configs that set it deliberately keep working.tls.caCertificatePath,tls.trustStorePathandtls.keyStorePathmust resolve to content. Null, empty and blank count as missing, and the error names the field plus the${...}reference, never a resolved value. This replaces "Failed to create OpenSearch transport: null".opensearchUrlwith userinfo (https://u:p@hostorhttps://u@host) is a validation error; the message does not echo the credentials.Testing
OpenSearchTransportFactoryTest(empty, blank and unset references for BASIC credentials and each TLS path; hostname warning viaQCollectingLogger) and a userinfo case inQuickSearchQBitConfigValidationTest. All failed before the fix.CI=true ./mvnw verify: 312 unit and 18 integration tests pass, JaCoCo checks met.Closes #15