Skip to content

[OAS Validation] Fix structural schema issues in Fleet APIs #264565

@TinaHeiligers

Description

@TinaHeiligers

The Fleet API schemas have two structural issues tracked under #256462.

One DELETE operation defines a requestBody, and around 7 schemas use inline oneOf/anyOf/allOf instead of referencing named components. (Counts approximate as of April 2026; run verification steps below for current numbers.)

DELETE operation with requestBody:

Method Path
DELETE /api/apm/settings/agent-configuration

Inline polymorphic schemas (7 instances):

Method Path Location
POST /api/fleet/agents/{agentId}/rollback response 200
POST /api/fleet/agents/{agentId}/privilege_level_change response 200
GET /api/fleet/epm/templates/{pkgName}/{pkgVersion}/inputs response 200
POST /api/fleet/outputs requestBody
PUT /api/fleet/outputs/{outputId} requestBody
POST /api/fleet/package_policies requestBody
PUT /api/fleet/package_policies/{packagePolicyId} requestBody

Verification:

node scripts/capture_oas_snapshot --no-serverless --include-path /api/fleet --include-path /api/apm
node scripts/validate_oas_snapshot

After the OAS snapshot validates, coordinate with @elastic/kibana-core to verify downstream client generation isn't affected. The tooling for scriptable codegen verification is tracked in #262361.

Part of #256462

Metadata

Metadata

Assignees

Labels

Feature:OASWork or issues related to Core-provided mechanisms for generating OASTeam:FleetTeam label for Observability Data Collection Fleet team

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions