Add Edge Processor support #389
Open
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
|
Ok another annoying note is that the authentication token used here to connect the Edge Processor back to SCS expires after 5 minutes, so after initial deployment, you'll have to update the token again to deploy to additional servers or if they go offline for long enough. This feels like a design issue on Splunk's side, and I'm not sure if/how we want to handle that, or that kind of inflexibility invalidates the worth of using Puppet to manage/deploy Edge Processors. Thoughts? |
|
Can you update the REFERENCE.md file by running |
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.
Pull Request (PR) description
Adding support for installing/configuring/managing the Edge Processor from Splunk.
This Pull Request (PR) fixes the following issues
Fixes #388