-
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: Split common tty definitions #42004
Conversation
No functional changes, just move tty things to a common place so that the upcoming system/process provider can use it. Last of the PRs to split common code for the new system/process provider (I promise).
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) |
No functional changes, just move tty things to a common place so that the upcoming system/process provider can use it. Last of the PRs to split common code for the new system/process provider (I promise). (cherry picked from commit 560b842)
No functional changes, just move tty things to a common place so that the upcoming system/process provider can use it. Last of the PRs to split common code for the new system/process provider (I promise).
No functional changes, just move tty things to a common place so that the upcoming system/process provider can use it. Last of the PRs to split common code for the new system/process provider (I promise). (cherry picked from commit 560b842) Co-authored-by: Christiano Haesbaert <[email protected]>
Proposed commit message
No functional changes, just move tty things to a common place so that the upcoming system/process provider can use it.
Last of the PRs to split common code for the new system/process provider (I promise).
Checklist
- [ ] 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 worksCHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.