[OpenAPI generator] add `transformSchemaName` config options by janmonschke · Pull Request #250857 · elastic/kibana

janmonschke · 2026-01-29T09:57:49Z

Summary

If a yaml definition defines the type names in lowercase, like in the cases codebase, the generator would generate lowercase type/schema names. This is against our eslint rules.

in: query
name: assignees
description: >
  Filters the returned cases by assignees.
  Valid values are `none` or unique identifiers for the user profiles.
  These identifiers can be found by using the suggest user profile API.

would generate:

export type assignees = z.infer<typeof assignees>; // <-- ESLint error
export const assignees = z.array(...)

This PR adds a transformSchemaName option that allows to transform the schema names to PascalCase.

That allows us to generate the correct schema names without having to touch the API documentation yaml files.

This is the code that is generated with transformSchemaName set to pascalCase.

export type Assignees = z.infer<typeof Assignees>;
export const Assignees = z.array(...)

For now transformSchemaName only supports pascalCase but it can be extended in the future.

elasticmachine · 2026-01-29T09:57:53Z

Pinging @elastic/kibana-cases (Team:Cases)

elasticmachine · 2026-01-29T10:42:31Z

⏳ Build in-progress, with failures

Buildkite Build
Commit: 7389212

Failed CI Steps

Checks

History

💔 Build #387305 failed e3e7de5

jaredburgettelastic

LGTM for Entity Analytics

stephmilovic

CR only, LGTM!

rylnd

Whitespace-only changes for Detection Engine 😅 . LGTM!

szwarckonrad

DW changes LGTM!

nikitaindik

Checked the file changes and the generated output. It all looks good to me.

…orms

kibanamachine · 2026-02-04T15:45:07Z

Starting backport for target branches: 8.19, 9.1, 9.2, 9.3

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

kibanamachine · 2026-02-04T15:53:32Z

💔 All backports failed

Status	Branch	Result
❌	8.19	Backport failed because of merge conflicts You might need to backport the following PRs to 8.19: - [DOCS][SECURITY] Updates API docs for Elastic Endpoint exceptions (#223053)
❌	9.1	Backport failed because of merge conflicts
❌	9.2	Backport failed because of merge conflicts
❌	9.3	Backport failed because of merge conflicts

Manual backport

To create the backport manually run:

node scripts/backport --pr 250857

Questions ?

Please refer to the Backport tool documentation

kibanamachine · 2026-02-05T15:49:08Z

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 250857 locally
cc: @janmonschke

kibanamachine · 2026-02-06T15:49:53Z

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 250857 locally
cc: @janmonschke

kibanamachine · 2026-02-09T17:49:00Z

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 250857 locally
cc: @janmonschke

janmonschke · 2026-02-10T09:46:08Z

💚 All backports created successfully

Status	Branch	Result
✅	9.3

Note: Successful backport PRs will be merged automatically after passing CI.

Questions ?

Please refer to the Backport tool documentation

…#250857) ## Summary If a yaml definition defines the type names in lowercase, like in the cases codebase, the generator would generate lowercase type/schema names. This is against our eslint rules. ```yaml in: query name: assignees description: > Filters the returned cases by assignees. Valid values are `none` or unique identifiers for the user profiles. These identifiers can be found by using the suggest user profile API. ``` would generate: ```ts export type assignees = z.infer<typeof assignees>; // <-- ESLint error export const assignees = z.array(...) ``` This PR adds a transformSchemaName option that allows to transform the schema names to `PascalCase`. That allows us to generate the correct schema names without having to touch the API documentation yaml files. This is the code that is generated with `transformSchemaName` set to `pascalCase`. ```ts export type Assignees = z.infer<typeof Assignees>; export const Assignees = z.array(...) ``` For now `transformSchemaName` only supports `pascalCase` but it can be extended in the future. --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com> Co-authored-by: Michael Olorunnisola <michael.olorunnisola@elastic.co> (cherry picked from commit cb8b556) # Conflicts: # x-pack/solutions/security/packages/kbn-securitysolution-exceptions-common/api/model/exception_list_common.gen.ts

…#250857) ## Summary If a yaml definition defines the type names in lowercase, like in the cases codebase, the generator would generate lowercase type/schema names. This is against our eslint rules. ```yaml in: query name: assignees description: > Filters the returned cases by assignees. Valid values are `none` or unique identifiers for the user profiles. These identifiers can be found by using the suggest user profile API. ``` would generate: ```ts export type assignees = z.infer<typeof assignees>; // <-- ESLint error export const assignees = z.array(...) ``` This PR adds a transformSchemaName option that allows to transform the schema names to `PascalCase`. That allows us to generate the correct schema names without having to touch the API documentation yaml files. This is the code that is generated with `transformSchemaName` set to `pascalCase`. ```ts export type Assignees = z.infer<typeof Assignees>; export const Assignees = z.array(...) ``` For now `transformSchemaName` only supports `pascalCase` but it can be extended in the future. --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com> Co-authored-by: Michael Olorunnisola <michael.olorunnisola@elastic.co> (cherry picked from commit cb8b556) # Conflicts: # x-pack/solutions/security/packages/kbn-securitysolution-exceptions-common/api/model/exception_list_common.gen.ts # x-pack/solutions/security/plugins/security_solution/common/api/endpoint/actions/file_download/file_download.gen.ts # x-pack/solutions/security/plugins/security_solution/common/api/endpoint/actions/file_info/file_info.gen.ts # x-pack/solutions/security/plugins/security_solution/common/api/endpoint/model/schema/common.gen.ts # x-pack/solutions/security/plugins/security_solution/common/api/entity_analytics/monitoring/monitoring_entity_source/monitoring_entity_source.gen.ts

janmonschke · 2026-02-10T10:02:19Z

💚 All backports created successfully

Status	Branch	Result
✅	9.2
✅	9.1
✅	8.19

Note: Successful backport PRs will be merged automatically after passing CI.

Questions ?

Please refer to the Backport tool documentation

…#250857) ## Summary If a yaml definition defines the type names in lowercase, like in the cases codebase, the generator would generate lowercase type/schema names. This is against our eslint rules. ```yaml in: query name: assignees description: > Filters the returned cases by assignees. Valid values are `none` or unique identifiers for the user profiles. These identifiers can be found by using the suggest user profile API. ``` would generate: ```ts export type assignees = z.infer<typeof assignees>; // <-- ESLint error export const assignees = z.array(...) ``` This PR adds a transformSchemaName option that allows to transform the schema names to `PascalCase`. That allows us to generate the correct schema names without having to touch the API documentation yaml files. This is the code that is generated with `transformSchemaName` set to `pascalCase`. ```ts export type Assignees = z.infer<typeof Assignees>; export const Assignees = z.array(...) ``` For now `transformSchemaName` only supports `pascalCase` but it can be extended in the future. --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com> Co-authored-by: Michael Olorunnisola <michael.olorunnisola@elastic.co> (cherry picked from commit cb8b556) # Conflicts: # src/platform/packages/shared/kbn-openapi-generator/src/parser/get_generation_context.ts # x-pack/platform/packages/shared/kbn-elastic-assistant-common/impl/schemas/attack_discovery/common_attributes.gen.ts # x-pack/solutions/security/packages/kbn-securitysolution-exceptions-common/api/import_exceptions/import_exceptions.gen.ts # x-pack/solutions/security/packages/kbn-securitysolution-exceptions-common/api/model/exception_list_common.gen.ts # x-pack/solutions/security/packages/kbn-securitysolution-lists-common/api/import_list_items/import_list_items.gen.ts # x-pack/solutions/security/plugins/security_solution/common/api/endpoint/actions/file_download/file_download.gen.ts # x-pack/solutions/security/plugins/security_solution/common/api/endpoint/actions/file_info/file_info.gen.ts # x-pack/solutions/security/plugins/security_solution/common/api/endpoint/actions/response_actions/run_script/run_script.gen.ts # x-pack/solutions/security/plugins/security_solution/common/api/endpoint/model/schema/common.gen.ts # x-pack/solutions/security/plugins/security_solution/common/api/entity_analytics/monitoring/monitoring_entity_source/monitoring_entity_source.gen.ts

…250857) (#252467) # Backport This will backport the following commits from `main` to `9.3`: - [[OpenAPI generator] add `transformSchemaName` config options (#250857)](#250857)  ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport)

…250857) (#252468) # Backport This will backport the following commits from `main` to `9.2`: - [[OpenAPI generator] add `transformSchemaName` config options (#250857)](#250857)  ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport)  --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>

…250857) (#252472) # Backport This will backport the following commits from `main` to `8.19`: - [[OpenAPI generator] add `transformSchemaName` config options (#250857)](#250857)  ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport)  --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>

## Summary Depends on #250857 Adds a new step to the CI that generates zod schemas from the API yaml specifications --------- Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com> Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>

…0913) ## Summary Depends on elastic#250857 Adds a new step to the CI that generates zod schemas from the API yaml specifications --------- Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com> Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>

add transformSchemaName config options

e3e7de5

janmonschke added release_note:skip Skip the PR/issue when compiling release notes backport:skip This PR does not require backporting labels Jan 29, 2026

janmonschke requested a review from a team as a code owner January 29, 2026 09:57

janmonschke added the Team:Cases Security Solution Cases team label Jan 29, 2026

janmonschke requested a review from nikitaindik January 29, 2026 09:57

Changes from yarn openapi:generate

7389212

elastic-vault-github-plugin-prod bot requested a review from a team as a code owner January 29, 2026 10:20

Changes from yarn openapi:generate

86d83f2

elastic-vault-github-plugin-prod bot requested review from a team as code owners January 29, 2026 10:42

elastic-vault-github-plugin-prod bot requested review from hop-dev, paul-tavares and szwarckonrad January 29, 2026 10:42

elastic-vault-github-plugin-prod bot requested a review from rylnd January 29, 2026 10:42

janmonschke added backport:all-open Backport to all branches that could still receive a release and removed backport:skip This PR does not require backporting labels Jan 29, 2026

joeypoon approved these changes Jan 29, 2026

View reviewed changes

jaredburgettelastic approved these changes Jan 29, 2026

View reviewed changes

janmonschke mentioned this pull request Jan 29, 2026

[Cases] Generate cases API docs and zod schemas on the CI #250913

Merged

stephmilovic approved these changes Jan 29, 2026

View reviewed changes

rylnd approved these changes Jan 30, 2026

View reviewed changes

szwarckonrad approved these changes Feb 2, 2026

View reviewed changes

paul-tavares approved these changes Feb 2, 2026

View reviewed changes

nikitaindik approved these changes Feb 3, 2026

View reviewed changes

Merge branch 'main' into cases/zod-schema-generation-generator-transf…

67f77e3

…orms

hop-dev approved these changes Feb 3, 2026

View reviewed changes

michaelolo24 merged commit cb8b556 into elastic:main Feb 4, 2026
16 checks passed

kibanamachine added the v9.4.0 label Feb 4, 2026

kibanamachine added the backport missing Added to PRs automatically when the are determined to be missing a backport. label Feb 5, 2026

janmonschke mentioned this pull request Feb 10, 2026

[9.3] [OpenAPI generator] add transformSchemaName config options (#250857) #252467

Merged

This was referenced Feb 10, 2026

[9.2] [OpenAPI generator] add transformSchemaName config options (#250857) #252468

Merged

[9.1] [OpenAPI generator] add transformSchemaName config options (#250857) #252471

Closed

janmonschke mentioned this pull request Feb 10, 2026

[8.19] [OpenAPI generator] add transformSchemaName config options (#250857) #252472

Merged

kibanamachine added v9.3.0 v9.2.6 labels Feb 10, 2026

kibanamachine added v8.19.12 and removed backport missing Added to PRs automatically when the are determined to be missing a backport. labels Feb 10, 2026

Conversation

janmonschke commented Jan 29, 2026 • edited by kibanamachine Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary

Uh oh!

elasticmachine commented Jan 29, 2026

Uh oh!

elasticmachine commented Jan 29, 2026

⏳ Build in-progress, with failures

Failed CI Steps

History

Uh oh!

jaredburgettelastic left a comment

Choose a reason for hiding this comment

Uh oh!

stephmilovic left a comment

Choose a reason for hiding this comment

Uh oh!

rylnd left a comment

Choose a reason for hiding this comment

Uh oh!

szwarckonrad left a comment

Choose a reason for hiding this comment

Uh oh!

nikitaindik left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

kibanamachine commented Feb 4, 2026

Uh oh!

kibanamachine commented Feb 4, 2026

💔 All backports failed

Manual backport

Questions ?

Uh oh!

kibanamachine commented Feb 5, 2026

Uh oh!

kibanamachine commented Feb 6, 2026

Uh oh!

kibanamachine commented Feb 9, 2026

Uh oh!

janmonschke commented Feb 10, 2026

💚 All backports created successfully

Questions ?

Uh oh!

janmonschke commented Feb 10, 2026

💚 All backports created successfully

Questions ?

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

12 participants

janmonschke commented Jan 29, 2026 •

edited by kibanamachine

Loading