Closed lcawl closed 1 week ago
Pinging @elastic/kibana-docs (Team:Docs)
Pinging @elastic/obs-ux-management-team (Team:obs-ux-management)
Just comment with: - `/oblt-deploy` : Deploy a Kibana instance using the Observability test environments. - `run` `docs-build` : Re-trigger the docs validation. (use unformatted text in the comment!)
docker.elastic.co/kibana-ci/kibana-serverless:pr-202373-985d6cd26be8
β unchanged
Starting backport for target branches: 8.16, 8.17
Status | Branch | Result |
---|---|---|
β | 8.16 | Backport failed because of merge conflicts You might need to backport the following PRs to 8.16: - [Synthetics] Fix to handle ops genie as default connector !! (#201923) - [Stack Connectors][SentinelOne + Crowdstrike] Update Crowdstrike and Sentinelone connectors to NOT validate API responses (#202515) |
β | 8.17 | Backport failed because of merge conflicts You might need to backport the following PRs to 8.17: - [Synthetics] Fix to handle ops genie as default connector !! (#201923) - [Stack Connectors][SentinelOne + Crowdstrike] Update Crowdstrike and Sentinelone connectors to NOT validate API responses (#202515) - [Security solution] Remove legacy ESQL quick prompt (#201276) - [Security Solution] [Onboarding] t1_analyst role blocked from interacting with cards due to missing integration privileges (#202413) |
To create the backport manually run:
node scripts/backport --pr 202373
Please refer to the Backport tool documentation
Status | Branch | Result |
---|---|---|
β | 8.x | |
β | 8.17 | |
β | 8.16 |
Note: Successful backport PRs will be merged automatically after passing CI.
Please refer to the Backport tool documentation
Looks like this PR has backport PRs but they still haven't been merged. Please merge them ASAP to keep the branches relatively in sync.
Summary
Fixes https://github.com/elastic/docs-content/issues/153
In particular, it removes unnecessary server URL declarations from some SLO API files and updates the kibana API overlays so that the serverless API document is no longer referring to "localhost".
NOTE: Per https://spec.openapis.org/oas/v3.0.3#server-object the "default" value is required.
Checklist
Check the PR satisfies following conditions.
Reviewers should verify this PR satisfies this list as well.
release_note:breaking
label should be applied in these situations.release_note:*
label is applied per the guidelinesIdentify risks
Does this PR introduce any risks? For example, consider risks like hard to test bugs, performance regression, potential of data loss.
No
Screenshots
The Kibana Serverless API examples will look like this:
The Kibana API examples will look like this: