Items expects a single field, not a list #233414

tobio · 2025-08-28T22:32:50Z

Summary

From the spec the items field should be a single schema defining the types within an array. If the array may contain multiple types then the schema should combine those types via oneOf.

Related to #228077

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. The release_note:breaking label 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 correct release_note:* label is applied per the guidelines
Review the backport guidelines and apply applicable backport:* labels.

elasticmachine · 2025-08-28T22:32:56Z

Pinging @elastic/obs-ux-management-team (Team:obs-ux-management)

…t --include-path /api/status --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 --update'

elasticmachine · 2025-08-29T04:16:16Z

💛 Build succeeded, but was flaky

Buildkite Build
Commit: 426599a

Failed CI Steps

Test Failures

[job] [logs] FTR Configs #55 / serverless search UI index details page - search solution developer search index details page page loading error reload button shows details page again

Metrics [docs]

✅ unchanged

History

💛 Build #333896 was flaky d4c9a60

cc @tobio

afharo

Thanks for fixing it!

kibanamachine · 2025-08-29T21:00:40Z

Starting backport for target branches: 8.18, 8.19, 9.0, 9.1

https://github.com/elastic/kibana/actions/runs/17334154890

kibanamachine · 2025-08-29T21:08:26Z

💔 All backports failed

Status	Branch	Result
❌	8.18	Backport failed because of merge conflicts You might need to backport the following PRs to 8.18: - [AI assistant] Add setting to configure default LLM (#231940) - Use an explicit string for @timestamp (#233256) - Moves fast-glob to devDependencies (#233376)
❌	8.19	Backport failed because of merge conflicts You might need to backport the following PRs to 8.19: - [ES\|QL] Fixes lookup indexes route failures on read permissions (#233282) - [AI assistant] Add setting to configure default LLM (#231940) - [SKA] move generated integration API test clients to a new location (#233112) - [Index management] Clean all tests after execution and navigate directly to the tab (#232198)
❌	9.0	Backport failed because of merge conflicts You might need to backport the following PRs to 9.0: - [AI assistant] Add setting to configure default LLM (#231940)
❌	9.1	Backport failed because of merge conflicts You might need to backport the following PRs to 9.1: - [AI assistant] Add setting to configure default LLM (#231940) - [SKA] move generated integration API test clients to a new location (#233112) - [Index management] Clean all tests after execution and navigate directly to the tab (#232198)

Manual backport

To create the backport manually run:

node scripts/backport --pr 233414

Questions ?

Please refer to the Backport tool documentation

## Summary From the [spec](https://swagger.io/docs/specification/v3_0/data-models/data-types/#arrays) the `items` field should be a single schema defining the types within an array. If the array may contain multiple types then the schema should combine those types via `oneOf`. Related to elastic#228077 ### Checklist Check the PR satisfies following conditions. Reviewers should verify this PR satisfies this list as well. - [x] 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) - [x] [Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html) was added for features that require explanation or tutorials - [x] [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 - [x] 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) - [x] 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. - [x] [Flaky Test Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was used on any tests changed - [x] 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) - [x] Review the [backport guidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing) and apply applicable `backport:*` labels. --------- Co-authored-by: kibanamachine <[email protected]>

kibanamachine · 2025-09-01T21:48:31Z

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 233414 locally
cc: @tobio

## Summary From the [spec](https://swagger.io/docs/specification/v3_0/data-models/data-types/#arrays) the `items` field should be a single schema defining the types within an array. If the array may contain multiple types then the schema should combine those types via `oneOf`. Related to elastic#228077 ### Checklist Check the PR satisfies following conditions. Reviewers should verify this PR satisfies this list as well. - [x] 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) - [x] [Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html) was added for features that require explanation or tutorials - [x] [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 - [x] 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) - [x] 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. - [x] [Flaky Test Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was used on any tests changed - [x] 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) - [x] Review the [backport guidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing) and apply applicable `backport:*` labels. --------- Co-authored-by: kibanamachine <[email protected]>

kibanamachine · 2025-09-02T21:48:37Z

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 233414 locally
cc: @tobio

kibanamachine · 2025-09-03T22:48:41Z

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 233414 locally
cc: @tobio

kibanamachine · 2025-09-04T22:48:51Z

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 233414 locally
cc: @tobio

Items expects a single field, not a list

bdec911

tobio self-assigned this Aug 28, 2025

tobio requested review from a team as code owners August 28, 2025 22:32

botelastic bot added the Team:actionable-obs Formerly "obs-ux-management", responsible for SLO, o11y alerting, significant events, & synthetics. label Aug 28, 2025

tobio added release_note:skip Skip the PR/issue when compiling release notes backport:all-open Backport to all branches that could still receive a release labels Aug 28, 2025

elastic-vault-github-plugin-prod bot requested a review from a team as a code owner August 28, 2025 22:49

tobio and others added 2 commits August 29, 2025 12:14

Merge branch 'main' into fix-get-parameter-response-items

78ad98f

cesco-f approved these changes Aug 29, 2025

View reviewed changes

mdbirnstiehl approved these changes Aug 29, 2025

View reviewed changes

afharo approved these changes Aug 29, 2025

View reviewed changes

tobio merged commit 99a1139 into elastic:main Aug 29, 2025
13 checks passed

kibanamachine added the v9.2.0 label Aug 29, 2025

kibanamachine added the backport missing Added to PRs automatically when the are determined to be missing a backport. label Sep 1, 2025

tobio removed the backport missing Added to PRs automatically when the are determined to be missing a backport. label Sep 2, 2025

kibanamachine added the backport missing Added to PRs automatically when the are determined to be missing a backport. label Sep 3, 2025

tobio added the backport:skip This PR does not require backporting label Sep 5, 2025

kibanamachine removed the backport missing Added to PRs automatically when the are determined to be missing a backport. label Sep 5, 2025

tobio removed the backport:all-open Backport to all branches that could still receive a release label Sep 5, 2025

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Items expects a single field, not a list #233414

Items expects a single field, not a list #233414

Uh oh!

tobio commented Aug 28, 2025 •

edited by kibanamachine

Loading

Uh oh!

elasticmachine commented Aug 28, 2025

Uh oh!

elasticmachine commented Aug 29, 2025

Uh oh!

afharo left a comment

Uh oh!

Uh oh!

kibanamachine commented Aug 29, 2025

Uh oh!

kibanamachine commented Aug 29, 2025

Uh oh!

kibanamachine commented Sep 1, 2025

Uh oh!

kibanamachine commented Sep 2, 2025

Uh oh!

kibanamachine commented Sep 3, 2025

Uh oh!

kibanamachine commented Sep 4, 2025

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

6 participants

Items expects a single field, not a list #233414

Items expects a single field, not a list #233414

Uh oh!

Conversation

tobio commented Aug 28, 2025 • edited by kibanamachine Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary

Checklist

Uh oh!

elasticmachine commented Aug 28, 2025

Uh oh!

elasticmachine commented Aug 29, 2025

💛 Build succeeded, but was flaky

Failed CI Steps

Test Failures

Metrics [docs]

History

Uh oh!

afharo left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

kibanamachine commented Aug 29, 2025

Uh oh!

kibanamachine commented Aug 29, 2025

💔 All backports failed

Manual backport

Questions ?

Uh oh!

kibanamachine commented Sep 1, 2025

Uh oh!

kibanamachine commented Sep 2, 2025

Uh oh!

kibanamachine commented Sep 3, 2025

Uh oh!

kibanamachine commented Sep 4, 2025

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

6 participants

tobio commented Aug 28, 2025 •

edited by kibanamachine

Loading