[9.4] Fix composable inputs on API reference integration docs (#267472)#267703
Merged
kibanamachine merged 1 commit intoelastic:9.4from May 5, 2026
Merged
[9.4] Fix composable inputs on API reference integration docs (#267472)#267703kibanamachine merged 1 commit intoelastic:9.4from
kibanamachine merged 1 commit intoelastic:9.4from
Conversation
## Summary Found while working on composable packages elastic/elastic-package#3480 When an integration is bundled with inputs (composable packages) API reference should use the effective name instead of the input type. Effective name is introduced when two inputs share the same type, so they can be idetified. ### Checklist Check the PR satisfies following conditions. Reviewers should verify this PR satisfies this list as well. - [ ] Any text added follows [EUI's writing guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses sentence case text and includes [i18n support](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md) - [ ] [Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html) was added for features that require explanation or tutorials - [ ] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios - [ ] If a plugin configuration key changed, check if it needs to be allowlisted in the cloud and added to the [docker list](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker) - [ ] This was checked for breaking HTTP API changes, and any breaking changes have been approved by the breaking-change committee. The `release_note:breaking` label should be applied in these situations. - [ ] [Flaky Test Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was used on any tests changed - [ ] The PR description includes the appropriate Release Notes section, and the correct `release_note:*` label is applied per the [guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process) - [ ] Review the [backport guidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing) and apply applicable `backport:*` labels. ### How to test Tested using the nginx_composable text fixture under [elastic-package ](elastic/elastic-package#3480) ### Screenshots Before <img width="1368" height="610" alt="Screenshot 2026-04-30 at 09 35 31" src="https://github.com/user-attachments/assets/e0ea3cba-ee2b-4ede-9b8d-30f413d336a2" /> After <img width="1134" height="738" alt="Screenshot 2026-05-04 at 14 45 42" src="https://github.com/user-attachments/assets/7aecde20-4b0e-4384-8a61-bb1ea0c40d34" /> (cherry picked from commit 8c42329)
botelastic
Bot
added
the
Team:Fleet
8 tasks
|
Pinging @elastic/fleet (Team:Fleet) |
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
Contributor
ApprovabilityVerdict: Would Approve This bug fix extracts input-gathering logic into a shared service while fixing key generation for composable inputs. The changes are well-tested (204 lines of new tests), reuse existing utilities, and the author owns all modified files. Macroscope would have approved this PR. Enable approvability here. |
Contributor
Author
💛 Build succeeded, but was flaky
Failed CI StepsTest Failures
Metrics [docs]Module Count
Async chunks
Page load bundle
|
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
2 participants
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.
Backport
This will backport the following commits from
mainto9.4:Questions ?
Please refer to the Backport tool documentation