Add automatic support for V2 search endpoints #127
Merged
Conversation
This file contains 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
fix: updated version of search endpoint /search/v2/jobs/export
…er/info endpoint.
|
cc: @thilles I modified your changes to use the Javascript SDK to determine Splunk version, then fallback to deprecated search endpoints if version isn't determined or if using older (8.x for example) versions that don't yet support search V2 APIs. FYI I've tested this on a local Splunk 9.3.0 deployment but not an older deployment. |
|
Good to go |
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.
Upgrade to v2.0.0 of splunk-sdk-javascript which provides automatic support for v2 search endpoints. For export endpoints (which aren't supported by the SDK at this time) use the SDK to determine which endpoint should be used based on the Splunk version from the /services/server/info endpoint (
service.getInfo()).