[OAS] Promote space path on serverless APIs#241203
Merged
lcawl merged 7 commits intoelastic:mainfrom Nov 3, 2025
Merged
Conversation
lcawl
added
release_note:skip
…atus --include-path /api/alerting/rule/ --include-path /api/alerting/rules --include-path /api/actions --include-path /api/security/role --include-path /api/spaces --include-path /api/streams --include-path /api/fleet --include-path /api/saved_objects/_import --include-path /api/saved_objects/_export --include-path /api/maintenance_window --include-path /api/agent_builder --update
elastic-vault-github-plugin-prod
bot
requested a review
from a team
as a code owner
Contributor
💛 Build succeeded, but was flaky
Failed CI StepsTest Failures
Metrics [docs]
|
jesuswr
approved these changes
Nov 3, 2025
…atus --include-path /api/alerting/rule/ --include-path /api/alerting/rules --include-path /api/actions --include-path /api/security/role --include-path /api/spaces --include-path /api/streams --include-path /api/fleet --include-path /api/saved_objects/_import --include-path /api/saved_objects/_export --include-path /api/maintenance_window --include-path /api/agent_builder --update
Contributor
|
Starting backport for target branches: 9.2 https://github.com/elastic/kibana/actions/runs/19045280075 |
Contributor
💔 All backports failed
Manual backportTo create the backport manually run: Questions ?Please refer to the Backport tool documentation |
lcawl
added a commit
to lcawl/kibana
that referenced
this pull request
Nov 3, 2025
(cherry picked from commit d72994b)
Contributor
Author
💚 All backports created successfully
Note: Successful backport PRs will be merged automatically after passing CI. Questions ?Please refer to the Backport tool documentation |
kibanamachine
added
the
backport missing
Contributor
|
Looks like this PR has a backport PR but it still hasn't been merged. Please merge it ASAP to keep the branches relatively in sync. |
lcawl
added a commit
that referenced
this pull request
Nov 6, 2025
# Backport This will backport the following commits from `main` to `9.2`: - [[OAS] Promote space path on serverless APIs (#241203)](#241203) <!--- Backport version: 10.1.0 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Lisa Cawley","email":"lcawley@elastic.co"},"sourceCommit":{"committedDate":"2025-11-03T18:31:20Z","message":"[OAS] Promote space path on serverless APIs (#241203)","sha":"d72994bd60d6464748de2b456d40a1d0da11dcd9","branchLabelMapping":{"^v9.3.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","docs","Feature:OAS","backport:version","v9.3.0","v9.2.1"],"title":"[OAS] Promote space path on serverless APIs","number":241203,"url":"https://github.com/elastic/kibana/pull/241203","mergeCommit":{"message":"[OAS] Promote space path on serverless APIs (#241203)","sha":"d72994bd60d6464748de2b456d40a1d0da11dcd9"}},"sourceBranch":"main","suggestedTargetBranches":["9.2"],"targetPullRequestStates":[{"branch":"main","label":"v9.3.0","branchLabelMappingKey":"^v9.3.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/241203","number":241203,"mergeCommit":{"message":"[OAS] Promote space path on serverless APIs (#241203)","sha":"d72994bd60d6464748de2b456d40a1d0da11dcd9"}},{"branch":"9.2","label":"v9.2.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT-->
kibanamachine
removed
the
backport missing
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
5 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.
Summary
This PR reverts #230931 so that space details are re-added to the Kibana Serverless APIs.
It also updates the overlays so that https://www.elastic.co/docs/api/doc/kibana/topic/topic-kibana-spaces appears in the Kibana Serverless API docs too.
Screenshots
The new "Kibana Spaces" topic in the Kibana Serverless APIs:
NOTE: I changed it to use "KIBANA_URL" rather than "localhost:5601" so the same content can be used in both sets of APIs.
Each API now also has the space variation details, for example:
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, uses sentence case text and includes i18n support- [ ] Documentation was added for features that require explanation or tutorials- [ ] Unit or functional tests 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- [ ] This was checked for breaking HTTP API changes, and any breaking changes have been approved by the breaking-change committee. Therelease_note:breakinglabel should be applied in these situations.- [ ] Flaky Test Runner was used on any tests changed- [ ] The PR description includes the appropriate Release Notes section, and the correctrelease_note:*label is applied per the guidelines- [ ] Review the backport guidelines and apply applicablebackport:*labels.Identify risks
N/A