-
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
[filebeat] Fix long filepaths in diagnostics exceeding max path limits on Windows #40909
[filebeat] Fix long filepaths in diagnostics exceeding max path limits on Windows #40909
Conversation
Pinging @elastic/sec-deployment-and-devices (Team:Security-Deployment and Devices) |
This is odd linter complain to the line: beats/x-pack/filebeat/input/cel/input.go Line 1253 in 43d80af
Can't reproduce this on my machine and the |
@aleksmaus This is #39589. |
So what is the course of action in order to get this change in, which is unrelated to all the linter complains that surfaced just because I had to touch these files? |
The action is no action. Linter happiness is not a requirement for merging. |
Thank you for clarification. I didn't know. It is different in different repositories. Some of the repos are blocking PR on linter errors. Will revert. Let the linter complain away then. |
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.
Thanks, this is good to have in.
@ycombinator @belimawr @AndersonQ Guys, I need 👍 on this one from one of the code owners team members. Pretty please? :) |
I'm looking at it right now ;) |
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, but I have two small comments:
- Is the goal of this PR to ensure the max path limit is never going to be exceeded or is it to just reduce the input name used by some inputs?
- Unless it's a 9.0 breaking change, all PRs should be backported to 8.x. I've added the backport label.
According to the original issue, the goal was to reduce the pathing length. The other path parts are more or less have predictable length. |
Good to know. Thanks! |
I don't wanna block, but I don't see any tests to ensure the right name is used on the files. Unless it'd be too complicated, could you add some? |
…s on Windows (#40909) * [filebeat] Fix long filepaths in diagnostics exceeding max path limits on Windows * Update changelog with PR number * Adjust utz * Quiet the linter false positive * More linter pacification * Fix linter complains for errors checks in okta.go * Let the linter complain again * Revert revert (cherry picked from commit d82fe9a)
…s on Windows (#40909) (#40923) * [filebeat] Fix long filepaths in diagnostics exceeding max path limits on Windows * Update changelog with PR number * Adjust utz * Quiet the linter false positive * More linter pacification * Fix linter complains for errors checks in okta.go * Let the linter complain again * Revert revert (cherry picked from commit d82fe9a) Co-authored-by: Aleksandr Maus <aleksandr.maus@elastic.co>
Proposed commit message
Fix long filepaths in diagnostics exceeding max path limits on Windows.
Following the first proposal here
elastic/elastic-agent#3758 (comment)
Added
IDWithoutName
that doesn't include the source name and using that instead.Checklist
CHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.Related issues
Screenshots
The screenshot that shows the diagnostics collected before and after this change. The earlier diagnostics shows the long path that includes the sanitized okta log collection URL. The diagnostics after this change have shorter path that doesn't include the sanitized URL in the path.