Repository navigation
Fix/auto state apply local salt files - #41
Merged
Merged
Conversation
securityonion now watches the directories under /opt/so/saltstack/local/salt/
that these pages tell users to edit, so hand-placed files are applied within
a few minutes instead of waiting for the next scheduled highstate.
Drop the Known Issues entry and turn the "not detected, so this step is
required" caveats on the zeek, elasticsearch, and rbac pages back into an
optional "if you don't want to wait" step.
Document the watched directories under Auto State Apply in salt.md, and say
plainly that anything else under local/salt/ still waits for the highstate.
Also correct two stale claims:
- zeek.md said intel and zkg packages reach separate sensor nodes only at
their next highstate. Auto State Apply targets every node running Zeek.
- logstash.md said a defined_pipelines change waits for the next highstate.
That is a SOC config save, which Auto State Apply has always detected.
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
2 participants
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.
securityonion now watches the directories under /opt/so/saltstack/local/salt/ that these pages tell users to edit, so hand-placed files are applied within a few minutes instead of waiting for the next scheduled highstate.
Drop the Known Issues entry and turn the "not detected, so this step is required" caveats on the zeek, elasticsearch, and rbac pages back into an optional "if you don't want to wait" step.
Document the watched directories under Auto State Apply in salt.md, and say plainly that anything else under local/salt/ still waits for the highstate.