-
Notifications
You must be signed in to change notification settings - Fork 4.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Auditbeat] improve docs for exclude_files option of file_integrity #35669
base: main
Are you sure you want to change the base?
Conversation
💚 CLA has been signed |
This pull request does not have a backport label.
To fixup this pull request, you need to add the backport labels for the needed
|
❕ Build Aborted
Expand to view the summary
Build stats
Steps errorsExpand to view the steps failures
|
/test |
The exclude_files option can be used for excluding directories, too, if recursive is set to true. Also (after spending hours on it) I've added a working example of a folder exclusion for Windows.
Thank you @efd6 ! Co-authored-by: Dan Kortschak <90160302+efd6@users.noreply.github.com>
This pull request does not have a backport label.
To fixup this pull request, you need to add the backport labels for the needed
|
Pinging @elastic/sec-linux-platform (Team:Security-Linux Platform) |
This pull request is now in conflicts. Could you fix it? 🙏
|
1 similar comment
This pull request is now in conflicts. Could you fix it? 🙏
|
-- Type of change
What does this PR do?
The exclude_files option can be used for excluding directories, too, if recursive is set to true. Also (after spending hours on it) I've added a working example of a folder exclusion for Windows.
Why is it important?
It seems not documented elsewhere ;-)
Checklist
- [ ] My code follows the style guidelines of this project- [ ] I have commented my code, particularly in hard-to-understand areas- [ ] I have made corresponding changes to the documentation- [ ] I have made corresponding change to the default configuration files- [ ] I have added tests that prove my fix is effective or that my feature works- [ ] I have added an entry inCHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.Author's Checklist