Skip to content

[9.4] [Fleet] Support setting explicit names for ambiguous inputs (#262138)#263182

Merged
kibanamachine merged 1 commit intoelastic:9.4from
kibanamachine:backport/9.4/pr-262138
Apr 14, 2026
Merged

[9.4] [Fleet] Support setting explicit names for ambiguous inputs (#262138)#263182
kibanamachine merged 1 commit intoelastic:9.4from
kibanamachine:backport/9.4/pr-262138

Conversation

@kibanamachine
Copy link
Copy Markdown
Contributor

Backport

This will backport the following commits from main to 9.4:

Questions ?

Please refer to the Backport tool documentation

…262138)

In integration packages, if multiple inputs in the same policy template
have the same type, data streams using them don't have a way to
distinguish them. In this case Fleet misbehaves, showing mixed elements
in the UI and failing to correctly create policies.

This change supports to explicitly name inputs, so inputs of the same
type can be used in the same policy template, and data streams are able
to reference them unambiguously.

This change is specially relevant for OTel integration packages. On these
packages it is going to be frequent to have multiple inputs of the `otelcol`
type in the same policy template. Without this change OTel integration
packages with multiple data streams can hardly be used.

(cherry picked from commit 911c150)
@kibanamachine kibanamachine added the backport This PR is a backport of another PR label Apr 14, 2026
@kibanamachine kibanamachine enabled auto-merge (squash) April 14, 2026 18:12
@botelastic botelastic Bot added the Team:Fleet Team label for Observability Data Collection Fleet team label Apr 14, 2026
@elasticmachine
Copy link
Copy Markdown
Contributor

Pinging @elastic/fleet (Team:Fleet)

@macroscopeapp
Copy link
Copy Markdown
Contributor

macroscopeapp Bot commented Apr 14, 2026

Approvability

Verdict: Needs human review

This backport introduces new input disambiguation capability in Fleet by adding a name field to differentiate inputs sharing the same type. While the author owns all changed files and the change is backwards-compatible with extensive tests, it modifies core input matching behavior across validation, upgrades, and UI rendering - warranting human review for a runtime behavior change of this scope.

You can customize Macroscope's approvability policy. Learn more.

@kibanamachine kibanamachine merged commit dbae2cf into elastic:9.4 Apr 14, 2026
25 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport This PR is a backport of another PR Team:Fleet Team label for Observability Data Collection Fleet team

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants