-
Notifications
You must be signed in to change notification settings - Fork 8.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[DOCS][API] Add /api/fleet to Fleet API paths #192652
Conversation
🤖 GitHub commentsExpand to view the GitHub comments
Just comment with:
|
Pinging @elastic/fleet (Team:Fleet) |
💚 Build Succeeded
Metrics [docs]
To update your PR or re-run it, just comment with: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
FYI we are moving to use kibana's schema generation, so these bundles will be generated: #184685
💔 All backports failed
Manual backportTo create the backport manually run:
Questions ?Please refer to the Backport tool documentation |
(cherry picked from commit 94aac7a)
💚 All backports created successfully
Note: Successful backport PRs will be merged automatically after passing CI. Questions ?Please refer to the Backport tool documentation |
# Backport This will backport the following commits from `main` to `8.15`: - [[DOCS][API] Add /api/fleet to Fleet API paths (#192652)](#192652) <!--- Backport version: 8.9.8 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Lisa Cawley","email":"[email protected]"},"sourceCommit":{"committedDate":"2024-09-12T14:03:40Z","message":"[DOCS][API] Add /api/fleet to Fleet API paths (#192652)","sha":"94aac7ad09900407f70656e9e5516806f69cf68e","branchLabelMapping":{"^v8.16.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Fleet","docs","v8.16.0","v8.15.2"],"number":192652,"url":"https://github.com/elastic/kibana/pull/192652","mergeCommit":{"message":"[DOCS][API] Add /api/fleet to Fleet API paths (#192652)","sha":"94aac7ad09900407f70656e9e5516806f69cf68e"}},"sourceBranch":"main","suggestedTargetBranches":["8.15"],"targetPullRequestStates":[{"branch":"main","label":"v8.16.0","labelRegex":"^v8.16.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/192652","number":192652,"mergeCommit":{"message":"[DOCS][API] Add /api/fleet to Fleet API paths (#192652)","sha":"94aac7ad09900407f70656e9e5516806f69cf68e"}},{"branch":"8.15","label":"v8.15.2","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT-->
Summary
This PR moves
api/fleet
from the OpenAPI servers definition into the path definition, since it's being lost when we merge this file into all the rest of the Kibana APIs (for example: https://www.elastic.co/docs/api/doc/kibana/operation/operation-new-agent-action). I've also commented out theinternal/fleet
endpoint since it seemed unlikely we want this published publicly. If that's an incorrect assumption, we can uncomment and re-generate the bundles.