DRILL-8370: Upgrade splunk-sdk-java to 1.9.3 #2719
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jnturton
added
dependencies
ci
|
The latest commit adds a patch for Splunk's broken validateCertificates toggle by @cgivre. |
|
Just noting here for future reference, but here is the issue on Splunk's SDK that references the SSL issue: |
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
| } | ||
| } | ||
| }; | ||
| context.init(null, trustAll, null); |
Check failure
Code scanning / CodeQL
`TrustManager` that accepts all certificates
|
@cgivre okay the last commit may have gotten rid of those sporadic CI failures 🤞. |
jnturton
removed
the
backport-to-stable
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
DRILL-8370: Upgrade splunk-sdk-java to 1.9.3
Description
Changes in splunk-sdk-java since 1.9.1.
Also removes the execution order dependence in the Splunk unit tests created by their expecting a certain number of records in the _audit index. I believe this order dependence is behind recent, apparently random CI run failures in the Splunk unit tests.
Documentation
N/A
Testing
Splunk unit tests.