locks: remove redundant beatPaths parameter#49837
locks: remove redundant beatPaths parameter#49837orestisfl wants to merge 2 commits intoelastic:mainfrom
Conversation
🤖 GitHub commentsJust comment with:
|
0d7b105 to
ed5649d
Compare
Now that Paths lives in beat.Info, there is no need to pass it as a separate argument alongside Info.
ed5649d to
d4574ad
Compare
|
Pinging @elastic/elastic-agent-data-plane (Team:Elastic-Agent-Data-Plane) |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (3)
📝 WalkthroughWalkthroughThe pull request refactors the lock initialization pattern across the beat instance. The ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
TL;DRBuildkite failures are all caused by one compile-time code bug: Remediation
Investigation detailsRoot Cause
Evidence
Verification
Follow-upAfter this fix, if metricbeat integration still fails, re-evaluate for any secondary runtime/test issues; current failures stop at compile time. Note 🔒 Integrity filter blocked 2 itemsThe following items were blocked because they don't meet the GitHub integrity level.
To allow these resources, lower tools:
github:
min-integrity: approved # merged | approved | unapproved | noneWhat is this? | From workflow: PR Buildkite Detective Give us feedback! React with 🚀 if perfect, 👍 if helpful, 👎 if not. |
Proposed commit message
Checklist
I have commented my code, particularly in hard-to-understand areasI have made corresponding changes to the documentationI have made corresponding change to the default configuration filesI have added an entry in./changelog/fragmentsusing the changelog tool.Disruptive User Impact
None. Internal API change only.
How to test this PR locally
Related issues
Beat.Info#49803