-
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
Fix the wrong event type for a new file #36098
Merged
Merged
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
It's supposed to emit a `create` event, not a `write` event when a previously ignored empty file gets written to.
rdner
added
Filebeat
Filebeat
Team:Elastic-Agent-Data-Plane
Label for the Agent Data Plane team
backport-7.17
Automated backport to the 7.17 branch with mergify
bugfix
labels
Jul 18, 2023
Pinging @elastic/elastic-agent-data-plane (Team:Elastic-Agent-Data-Plane) |
botelastic
bot
added
needs_team
Indicates that the issue/PR needs a Team:* label
and removed
needs_team
Indicates that the issue/PR needs a Team:* label
labels
Jul 18, 2023
leehinman
approved these changes
Jul 18, 2023
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. Thanks again for adding that test, this should help us maintain the behavior.
mergify bot
pushed a commit
that referenced
this pull request
Jul 18, 2023
It's supposed to emit a `create` event, not a `write` event when a previously ignored empty file gets written to. (cherry picked from commit f52d38a)
rdner
added a commit
that referenced
this pull request
Jul 18, 2023
It's supposed to emit a `create` event, not a `write` event when a previously ignored empty file gets written to. (cherry picked from commit f52d38a) Co-authored-by: Denis <[email protected]>
Scholar-Li
pushed a commit
to Scholar-Li/beats
that referenced
this pull request
Feb 5, 2024
It's supposed to emit a `create` event, not a `write` event when a previously ignored empty file gets written to.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
backport-7.17
Automated backport to the 7.17 branch with mergify
bugfix
Filebeat
Filebeat
Team:Elastic-Agent-Data-Plane
Label for the Agent Data Plane team
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.
What does this PR do?
It's supposed to emit a
create
event, not awrite
event when a previously ignored empty file gets written to.- [ ] I have made corresponding changes to the documentation- [ ] I have made corresponding change to the default configuration files- [ ] I have added an entry inCHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.Related issues