pipeline: remove redundant Paths from Settings and Supporter

[orestisfl]

Proposed commit message

pipeline: remove redundant Paths from Settings and Supporter

Pipeline stored both beatInfo and a separate *paths.Path, and
threaded it through the processing.Supporter.Create interface just
to call SetPaths on processors. Now that Info carries Paths, remove
the field from Pipeline and Settings, drop the parameter from
Supporter.Create, and let the builder read paths from info.Paths.

Checklist

• My code follows the style guidelines of this project
• 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 works.
• I have added an entry in ./changelog/fragments using the changelog tool.

Disruptive User Impact

None. Internal API change only.

How to test this PR locally

Related issues

• Closes [bug-hunter] dockerlogbeat leaves beat.Info.Paths nil, breaking queue.disk configuration #50450
• Relates [beatreceiver] move paths object into Beat.Info #49803
• Blocked by Move Paths from beat.Beat to beat.Info #49836

[github-actions]

🤖 GitHub comments

Just comment with:

• run docs-build : Re-trigger the docs validation. (use unformatted text in the comment!)

[elasticmachine]

Pinging @elastic/elastic-agent-data-plane (Team:Elastic-Agent-Data-Plane)

[coderabbitai]

Note

Reviews paused

It looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the reviews.auto_review.auto_pause_after_reviewed_commits setting.

Use the following commands to manage reviews:

• @coderabbitai resume to resume automatic reviews.
• @coderabbitai review to trigger a single review.

Use the checkboxes below for quick actions:

• ▶️ Resume reviews
• 🔍 Trigger review

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Enterprise

Run ID: 569b5eff-cad7-43de-9306-51e31f8e6c31

📥 Commits

Reviewing files that changed from the base of the PR and between 2b476b7 and 4b057df.

📒 Files selected for processing (1)

• x-pack/dockerlogbeat/pipelinemanager/libbeattools_test.go

---

📝 Walkthrough

Walkthrough

The change removes the Paths field from pipeline.Settings and the paths *paths.Path parameter from the Supporter.Create/processor creation API. Pipeline construction, processor creation, and queue factory initialization no longer pass explicit path arguments; path configuration is provided via beat.Info.Paths instead. Call sites and tests were updated to set beat.Info.Paths (including a new test ensuring getBeatInfo initializes Paths).

🚥 Pre-merge checks | ✅ 2

✅ Passed checks (2 passed)

Check name	Status	Explanation
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

• 🛠️ Update Documentation: Commit on current branch
• 🛠️ Update Documentation: Create PR

Tip

💬 Introducing Slack Agent: The best way for teams to turn conversations into code.

Slack Agent is built on CodeRabbit's deep understanding of your code, so your team can collaborate across the entire SDLC without losing context.

• Generate code and open pull requests
• Plan features and break down work
• Investigate incidents and troubleshoot customer tickets together
• Automate recurring tasks and respond to alerts with triggers
• Summarize progress and report instantly

Built for teams:

• Shared memory across your entire org—no repeating context
• Per-thread sandboxes to safely plan and execute work
• Governance built-in—scoped access, auditability, and budget controls

One agent for your entire SDLC. Right inside Slack.

👉 Get started

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[github-actions]

TL;DR

All three failing Buildkite jobs are failing in cross-build go build before tests/package logic runs, with the same error obtaining VCS status: exit status 128 error. Immediate unblock is to make Git metadata resolvable inside the crossbuild container (preferred) or run cross-build with -buildvcs=false.

Remediation

• Ensure the Docker cross-build container can resolve the repo Git metadata after the pipeline checkout change (the container only mounts the workspace path; if .git now points outside it, go build VCS stamping fails).
• As a short-term unblock, append -buildvcs=false to cross-build go build args/flags for these Buildkite jobs.
• Re-run:
  • x-pack/dockerlogbeat unit-test build step (mage build unitTest)
  • packetbeat packaging steps (linux and linux arm64)

Investigation details

Root Cause

This is a configuration/infrastructure failure, not a beat-specific code regression:

• x-pack/dockerlogbeat and both packetbeat packaging jobs fail with the same VCS stamping error from go build.
• The failure happens inside golang-crossbuild Docker runs before unit tests/assertions or packaging content checks.

Relevant build path in repo:

• dev-tools/mage/crossbuild.go:362-364 mounts only repoInfo.RootDir into the container (-v <root>:/go/src/..., -w <workdir>).
• dev-tools/mage/build.go:267 invokes go build without -buildvcs=false.

If the checkout change in this PR alters where Git metadata lives (e.g. .git indirection/info paths outside the mounted workspace), go build cannot collect VCS info and exits with status 128.

Evidence

• Build: https://buildkite.com/elastic/beats/builds/45693
• Jobs:
  • https://buildkite.com/elastic/beats-xpack-dockerlogbeat/builds/27152
  • https://buildkite.com/elastic/beats-packetbeat/builds/29645
• Key log excerpts:
  • /tmp/gh-aw/buildkite-logs/beats-xpack-dockerlogbeat-ubuntu-x-packdockerlogbeat-ubuntu-x86_64-unit-tests.txt:131-135
    • error obtaining VCS status: exit status 128
    • Use -buildvcs=false to disable VCS stamping.
  • /tmp/gh-aw/buildkite-logs/beats-packetbeat-ubuntu-packetbeat-packaging-linux.txt:115-119
    • same error/signature
  • /tmp/gh-aw/buildkite-logs/beats-packetbeat-ubuntu-packetbeat-packaging-linux-arm64.txt:115-119
    • same error/signature

Verification

Not run locally in this environment; diagnosis is based on the failing job logs and the cross-build invocation path.

Follow-up

After fixing Git metadata visibility (or applying temporary -buildvcs=false), these jobs should progress past the current early build failure, which will confirm this root cause.

Note

🔒 Integrity filter blocked 2 items

The following items were blocked because they don't meet the GitHub integrity level.

• pipeline: remove redundant Paths from Settings and Supporter #49841 pull_request_read: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #49841 pull_request_read: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".

To allow these resources, lower min-integrity in your GitHub frontmatter:

tools:
  github:
    min-integrity: approved  # merged | approved | unapproved | none

---

What is this? | From workflow: PR Buildkite Detective

Give us feedback! React with 🚀 if perfect, 👍 if helpful, 👎 if not.

[github-actions]

@Mergifyio backport 8.19 9.3 9.4

[mergify]

backport 8.19 9.3 9.4

✅ Backports have been created

Details

• #50615 [8.19](backport #49841) pipeline: remove redundant Paths from Settings and Supporter has been created for branch 8.19 but encountered conflicts

Cherry-pick of 3712f9b has failed:

On branch mergify/bp/8.19/pr-49841
Your branch is up to date with 'origin/8.19'.

You are currently cherry-picking commit 3712f9bc7.
  (fix conflicts and run "git cherry-pick --continue")
  (use "git cherry-pick --skip" to skip this patch)
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

Changes to be committed:
	modified:   libbeat/cmd/instance/beat.go
	modified:   libbeat/publisher/pipeline/client_test.go
	modified:   libbeat/publisher/pipeline/stress/run.go
	modified:   libbeat/publisher/processing/default.go
	modified:   libbeat/publisher/processing/default_test.go
	modified:   libbeat/publisher/processing/processing.go
	modified:   x-pack/dockerlogbeat/pipelinemanager/libbeattools.go
	new file:   x-pack/dockerlogbeat/pipelinemanager/libbeattools_test.go
	modified:   x-pack/libbeat/cmd/instance/beat.go

Unmerged paths:
  (use "git add <file>..." to mark resolution)
	both modified:   libbeat/publisher/pipeline/pipeline.go

To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally

• #50616 [9.3](backport #49841) pipeline: remove redundant Paths from Settings and Supporter has been created for branch 9.3 but encountered conflicts

Cherry-pick of 3712f9b has failed:

On branch mergify/bp/9.3/pr-49841
Your branch is up to date with 'origin/9.3'.

You are currently cherry-picking commit 3712f9bc7.
  (fix conflicts and run "git cherry-pick --continue")
  (use "git cherry-pick --skip" to skip this patch)
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

Changes to be committed:
	modified:   libbeat/cmd/instance/beat.go
	modified:   libbeat/publisher/pipeline/client_test.go
	modified:   libbeat/publisher/pipeline/stress/run.go
	modified:   libbeat/publisher/processing/default.go
	modified:   libbeat/publisher/processing/default_test.go
	modified:   libbeat/publisher/processing/processing.go
	modified:   x-pack/dockerlogbeat/pipelinemanager/libbeattools.go
	new file:   x-pack/dockerlogbeat/pipelinemanager/libbeattools_test.go
	modified:   x-pack/libbeat/cmd/instance/beat.go

Unmerged paths:
  (use "git add <file>..." to mark resolution)
	both modified:   libbeat/publisher/pipeline/pipeline.go

To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally

• #50617 [9.4](backport #49841) pipeline: remove redundant Paths from Settings and Supporter has been created for branch 9.4 but encountered conflicts

Cherry-pick of 3712f9b has failed:

On branch mergify/bp/9.4/pr-49841
Your branch is up to date with 'origin/9.4'.

You are currently cherry-picking commit 3712f9bc7.
  (fix conflicts and run "git cherry-pick --continue")
  (use "git cherry-pick --skip" to skip this patch)
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

Changes to be committed:
	modified:   libbeat/cmd/instance/beat.go
	modified:   libbeat/publisher/pipeline/client_test.go
	modified:   libbeat/publisher/pipeline/stress/run.go
	modified:   libbeat/publisher/processing/default.go
	modified:   libbeat/publisher/processing/default_test.go
	modified:   libbeat/publisher/processing/processing.go
	modified:   x-pack/dockerlogbeat/pipelinemanager/libbeattools.go
	new file:   x-pack/dockerlogbeat/pipelinemanager/libbeattools_test.go
	modified:   x-pack/libbeat/cmd/instance/beat.go

Unmerged paths:
  (use "git add <file>..." to mark resolution)
	both modified:   libbeat/publisher/pipeline/pipeline.go

To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally