Skip to content
Validate OpenAPI schema with Spectral

Introduce Registry Core REST API v3 #45

Sign in to view logs

Introduce Registry Core REST API v3

Introduce Registry Core REST API v3 #45

Triggered via pull request December 4, 2023 16:52
@EricWittmannEricWittmann
opened #4085
EricWittmann:feat/core-rest-api-v3
Status Success
Total duration 36s
Artifacts –

validate-openapi.yaml

on: pull_request
Validate
26s
Validate
Fit to window
Zoom out
Zoom in

Annotations

20 warnings
Validate: common/src/main/resources/META-INF/openapi.json#L1
oas3-api-servers
Validate: common/src/main/resources/META-INF/openapi.json#L1
rhoas-servers-config
Validate: common/src/main/resources/META-INF/openapi.json#L17
oas3-valid-media-example "value" property type must be string
Validate: common/src/main/resources/META-INF/openapi.json#L17
oas3-valid-schema-example "version" property type must be string
Validate: common/src/main/resources/META-INF/openapi.json#L17
oas3-valid-schema-example "example" property must be equal to one of the allowed values: "OUTBOUND", "INBOUND". Did you mean "INBOUND"?
Validate: common/src/main/resources/META-INF/openapi.json#L17
oas3-valid-schema-example "example" property must have required property "state"
Validate: common/src/main/resources/META-INF/openapi.json#L17
oas3-valid-schema-example "example" property must have required property "group"
Validate: common/src/main/resources/META-INF/openapi.json#L17
oas3-valid-schema-example "createdOn" property must match format "date-time"
Validate: common/src/main/resources/META-INF/openapi.json#L17
rhoas-response-media-type application/json is the only acceptable content type
Validate: common/src/main/resources/META-INF/openapi.json#L18
rhoas-path-regexp OpenAPI paths must start with `/api/`, followed by a version. All paths must follow snake_case
Validate: app/src/main/resources-unfiltered/META-INF/resources/api-specifications/registry/v3/openapi.json#L1
oas3-api-servers
Validate: app/src/main/resources-unfiltered/META-INF/resources/api-specifications/registry/v3/openapi.json#L1
rhoas-servers-config
Validate: app/src/main/resources-unfiltered/META-INF/resources/api-specifications/registry/v3/openapi.json#L17
oas3-valid-media-example "value" property type must be string
Validate: app/src/main/resources-unfiltered/META-INF/resources/api-specifications/registry/v3/openapi.json#L17
oas3-valid-schema-example "version" property type must be string
Validate: app/src/main/resources-unfiltered/META-INF/resources/api-specifications/registry/v3/openapi.json#L17
oas3-valid-schema-example "example" property must be equal to one of the allowed values: "OUTBOUND", "INBOUND". Did you mean "INBOUND"?
Validate: app/src/main/resources-unfiltered/META-INF/resources/api-specifications/registry/v3/openapi.json#L17
oas3-valid-schema-example "example" property must have required property "state"
Validate: app/src/main/resources-unfiltered/META-INF/resources/api-specifications/registry/v3/openapi.json#L17
oas3-valid-schema-example "example" property must have required property "group"
Validate: app/src/main/resources-unfiltered/META-INF/resources/api-specifications/registry/v3/openapi.json#L17
oas3-valid-schema-example "createdOn" property must match format "date-time"
Validate: app/src/main/resources-unfiltered/META-INF/resources/api-specifications/registry/v3/openapi.json#L17
rhoas-response-media-type application/json is the only acceptable content type
Validate: app/src/main/resources-unfiltered/META-INF/resources/api-specifications/registry/v3/openapi.json#L18
rhoas-path-regexp OpenAPI paths must start with `/api/`, followed by a version. All paths must follow snake_case