Per chat with @vishaangelova today, I was wrong in my previous comment...the Fleet APIs were missing from the docs because https://github.com/elastic/kibana/blob/8.19/oas_docs/scripts/merge_ess_oas.js was looking for that info in ${REPO_ROOT}/x-pack/plugins/fleet/common/openapi/bundled.yaml ... but the path is actually https://github.com/elastic/kibana/tree/8.19/x-pack/platform/plugins/shared/fleet/common/openapi.

Two solutions are therefore possible, depending on which source files are most accurate:

If the files in the x-pack/platform/plugins/shared/fleet/common/openapi folder are accurate, the solution is to fix the path in the merge_ess_oas.js file.
If the files in that folder are not accurate and it's preferable to derive the information from the code, the capture_oas_snapshot.sh should be updated to pull them in, the merge_ess_oas.js should be updated to remove mention of the other Fleet-specific YAML file, and optionally those manually maintained files should be removed to avoid future confusion. This is essentially what was done for the other branches in [Fleet] remove old bundled.yaml from oas, fixed tags kibana#194788

[Feedback]: Kibana Fleet APis are missing in 8.x branch #1601

Description