ignore schedule priority when updating splunk_saved_search #193
Open
Stan0304 wants to merge 1 commit into
Open
ignore schedule priority when updating splunk_saved_search #193Stan0304 wants to merge 1 commit into
Stan0304 wants to merge 1 commit into
Conversation
|
is this something that is being considered? we experience the same issues when our company has moved to Splunk Cloud from OnPrem. |
Collaborator
|
Hi @Stan0304 there are now merge conflicts. If you resolve those I can review and get this merged. Sorry for the long delay. |
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
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.
Description
As describe in #2, I get the following error when I am trying to update splunk_saved_search.
We are using Splunk Cloud and I am not admin of the Splunk instance. The token I use has been shared with me by a Splunk Admin and I do not have any way change anything about the Splunk TOKEN. So having this new flag
ignore_schedule_prioritywas the only to go onExample usage