Cherry-pick #18878 to 7.8: [Filebeat] Remove references to non-existent Zeek signatures fileset #19042
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
) In elastic#13683, a `signatures` fileset is enabled, but it did not exist. This removes it from the module.d/zeek.yml config file so that the module can start. In elastic#12812 there was a signatures fileset but that PR never merged. Perhaps the fileset from that closed PR can be brought into master. Relates: #18868 (cherry picked from commit 229aee0)
botelastic
bot
added
the
needs_team
💚 Build Succeeded
Expand to view the summary
Build stats
Test stats 🧪
|
|
Pinging @elastic/siem (Team:SIEM) |
botelastic
bot
removed
the
needs_team
adriansr
approved these changes
Jun 8, 2020
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.
Cherry-pick of PR #18878 to 7.8 branch. Original message:
What does this PR do?
In #13683, a
signaturesfileset is enabled, but it did not exist. This removesit from the module.d/zeek.yml config file so that the module can start.
In #12812 there was a signatures fileset but that PR never merged. Perhaps
the fileset from that closed PR can be brought into master.
Why is it important?
The module doesn't start under the default config because of the missing fileset.
Checklist
CHANGELOG.next.asciidocorCHANGELOG-developer.next.asciidoc.Related issues