Skip to content
Validate OpenAPI-Specifications

Add HTTP/XFCCAuth endpoint in the scheduler component #6627

Sign in to view logs

Add HTTP/XFCCAuth endpoint in the scheduler component

Add HTTP/XFCCAuth endpoint in the scheduler component #6627

Triggered via pull request February 14, 2025 15:18
@bonzofenixbonzofenix
synchronize #3437
add-cf-endpoint-to-scheduler
Status Success
Total duration 1m 45s
Artifacts –

openapi-specs-check.yaml

on: pull_request
validate
1m 37s
validate
Fit to window
Zoom out
Zoom in

Annotations

10 warnings
no-empty-servers: api/application-metric-api.openapi.yaml#L1
Servers must be present.
operation-operationId: api/application-metric-api.openapi.yaml#L78
Operation object should contain `operationId` field.
no-empty-servers: api/custom-metrics-api.openapi.yaml#L1
Servers must be present.
operation-operationId: api/custom-metrics-api.openapi.yaml#L29
Operation object should contain `operationId` field.
no-empty-servers: api/internal-scaling-history-api.openapi.yaml#L1
Servers must be present.
operation-operationId: api/internal-scaling-history-api.openapi.yaml#L76
Operation object should contain `operationId` field.
no-empty-servers: api/policy-api.openapi.yaml#L1
Servers must be present.
operation-operationId: api/policy-api.openapi.yaml#L64
Operation object should contain `operationId` field.
operation-operationId: api/policy-api.openapi.yaml#L29
Operation object should contain `operationId` field.
operation-operationId: api/policy-api.openapi.yaml#L49
Operation object should contain `operationId` field.