[filebeat][GCS] - Added missing 'text/csv' content-type filter support#44923
Merged
ShourieG merged 2 commits intoelastic:mainfrom Jun 19, 2025
Merged
[filebeat][GCS] - Added missing 'text/csv' content-type filter support#44923ShourieG merged 2 commits intoelastic:mainfrom
ShourieG merged 2 commits intoelastic:mainfrom
Conversation
Contributor
🤖 GitHub commentsExpand to view the GitHub comments
Just comment with:
|
Contributor
|
This pull request does not have a backport label.
To fixup this pull request, you need to add the backport labels for the needed
|
Contributor
|
Pinging @elastic/security-service-integrations (Team:Security-Service Integrations) |
kcreddy
approved these changes
Jun 19, 2025
Contributor
|
@Mergifyio backport 8.17 8.18 8.19 9.0 |
Contributor
✅ Backports have been createdDetails
|
mergify bot
pushed a commit
that referenced
this pull request
Jun 19, 2025
#44923) Currently content-type "text/csv" did not have official filtering support even though we support csv decoding. This made objects having this content type defined were not picked up for processing. This PR as a "bugfix", adds support for explicit "text/csv" content-type filtering while processing each job. (cherry picked from commit a2b74e8) # Conflicts: # x-pack/filebeat/input/gcs/input_test.go
6 tasks
mergify bot
pushed a commit
that referenced
this pull request
Jun 19, 2025
#44923) Currently content-type "text/csv" did not have official filtering support even though we support csv decoding. This made objects having this content type defined were not picked up for processing. This PR as a "bugfix", adds support for explicit "text/csv" content-type filtering while processing each job. (cherry picked from commit a2b74e8) # Conflicts: # x-pack/filebeat/input/gcs/input_test.go
6 tasks
mergify bot
pushed a commit
that referenced
this pull request
Jun 19, 2025
#44923) Currently content-type "text/csv" did not have official filtering support even though we support csv decoding. This made objects having this content type defined were not picked up for processing. This PR as a "bugfix", adds support for explicit "text/csv" content-type filtering while processing each job. (cherry picked from commit a2b74e8) # Conflicts: # x-pack/filebeat/input/gcs/input_test.go
6 tasks
mergify bot
pushed a commit
that referenced
this pull request
Jun 19, 2025
#44923) Currently content-type "text/csv" did not have official filtering support even though we support csv decoding. This made objects having this content type defined were not picked up for processing. This PR as a "bugfix", adds support for explicit "text/csv" content-type filtering while processing each job. (cherry picked from commit a2b74e8) # Conflicts: # x-pack/filebeat/input/gcs/input_test.go
ShourieG
added a commit
that referenced
this pull request
Jun 20, 2025
…ntent-type filter support (#44927) Currently content-type "text/csv" did not have official filtering support even though we support csv decoding. This made objects having this content type defined were not picked up for processing. This PR as a "bugfix", adds support for explicit "text/csv" content-type filtering while processing each job. --------- Co-authored-by: Shourie Ganguly <shourie.ganguly@elastic.co>
ShourieG
added a commit
that referenced
this pull request
Jun 20, 2025
…ntent-type filter support (#44928) Currently content-type "text/csv" did not have official filtering support even though we support csv decoding. This made objects having this content type defined were not picked up for processing. This PR as a "bugfix", adds support for explicit "text/csv" content-type filtering while processing each job. --------- Co-authored-by: Shourie Ganguly <shourie.ganguly@elastic.co>
ShourieG
added a commit
that referenced
this pull request
Jun 20, 2025
…tent-type filter support (#44930) Currently content-type "text/csv" did not have official filtering support even though we support csv decoding. This made objects having this content type defined were not picked up for processing. This PR as a "bugfix", adds support for explicit "text/csv" content-type filtering while processing each job. --------- Co-authored-by: Shourie Ganguly <shourie.ganguly@elastic.co>
ShourieG
added a commit
that referenced
this pull request
Jun 23, 2025
…ntent-type filter support (#44929) Currently content-type "text/csv" did not have official filtering support even though we support csv decoding. This made objects having this content type defined were not picked up for processing. This PR as a "bugfix", adds support for explicit "text/csv" content-type filtering while processing each job. --------- Co-authored-by: Shourie Ganguly <shourie.ganguly@elastic.co>
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
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.
Type of change
Proposed commit message
Checklist
CHANGELOG.next.asciidocorCHANGELOG-developer.next.asciidoc.Disruptive User Impact
Author's Checklist
How to test this PR locally
Related issues
Use cases
Screenshots
Logs