Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

AAD to Microsoft Entra updates #26725

Merged
merged 24 commits into from
Dec 12, 2023

Merge branch 'aad-entra-update' of https://github.com/stevemunk/azure…

4e068b4
Select commit
Loading
Failed to load commit list.
Merged

AAD to Microsoft Entra updates #26725

Merge branch 'aad-entra-update' of https://github.com/stevemunk/azure…
4e068b4
Select commit
Loading
Failed to load commit list.
openapi-pipeline-app / Swagger ModelValidation failed Nov 17, 2023 in 2m 24s

Swagger ModelValidation failed

ModelValidation: 591 Errors, 0 Warnings
View more details.

Details

Only 50 items are listed, please refer to log for more details.

Rule Message
❌ RESPONSE_SCHEMA_NOT_IN_SPEC Response statusCode 200 for operation Data_Upload has response body provided in the example, however the response does not have a "schema" defined in the swagger spec.
Url: Creator/preview/2.0/data.json#L167:22
ExampleUrl: 2.0/examples/data/Data_Upload.json#L26:16
❌ RESPONSE_SCHEMA_NOT_IN_SPEC Response statusCode 409 for operation Data_Upload has response body provided in the example, however the response does not have a "schema" defined in the swagger spec.
Url: Creator/preview/2.0/data.json#L167:22
ExampleUrl: 2.0/examples/data/Data_Upload.json#L26:16
❌ RESPONSE_SCHEMA_NOT_IN_SPEC Response statusCode 200 for operation Data_Update has response body provided in the example, however the response does not have a "schema" defined in the swagger spec.
Url: Creator/preview/2.0/data.json#L247:22
ExampleUrl: 2.0/examples/data/Data_Update.json#L26:16
❌ RESPONSE_SCHEMA_NOT_IN_SPEC Response statusCode 409 for operation Data_Update has response body provided in the example, however the response does not have a "schema" defined in the swagger spec.
Url: Creator/preview/2.0/data.json#L247:22
ExampleUrl: 2.0/examples/data/Data_Update.json#L26:16
❌ RESPONSE_SCHEMA_NOT_IN_SPEC Response statusCode 200 for operation Data_GetOperation has response body provided in the example, however the response does not have a "schema" defined in the swagger spec.
Url: Creator/preview/2.0/data.json#L353:22
ExampleUrl: 2.0/examples/data/Data_GetOperationStillRunning.json#L7:16
❌ RESPONSE_SCHEMA_NOT_IN_SPEC Response statusCode 200 for operation Data_GetOperation has response body provided in the example, however the response does not have a "schema" defined in the swagger spec.
Url: Creator/preview/2.0/data.json#L353:22
ExampleUrl: 2.0/examples/data/Data_GetOperation.json#L7:16
❌ RESPONSE_SCHEMA_NOT_IN_SPEC Response statusCode 200 for operation Dataset_Create has response body provided in the example, however the response does not have a "schema" defined in the swagger spec.
Url: Creator/preview/2.0/dataset.json#L140:22
ExampleUrl: 2.0/examples/dataset/Dataset_Create.json#L7:16
❌ RESPONSE_SCHEMA_NOT_IN_SPEC Response statusCode 200 for operation Dataset_GetOperation has response body provided in the example, however the response does not have a "schema" defined in the swagger spec.
Url: Creator/preview/2.0/dataset.json#L269:22
ExampleUrl: 2.0/examples/dataset/Dataset_GetOperationStillRunning.json#L7:16
❌ RESPONSE_SCHEMA_NOT_IN_SPEC Response statusCode 200 for operation Dataset_GetOperation has response body provided in the example, however the response does not have a "schema" defined in the swagger spec.
Url: Creator/preview/2.0/dataset.json#L269:22
ExampleUrl: 2.0/examples/dataset/Dataset_GetOperation.json#L7:16
❌ RESPONSE_SCHEMA_NOT_IN_SPEC Response statusCode 200 for operation Conversion_Convert has response body provided in the example, however the response does not have a "schema" defined in the swagger spec.
Url: Creator/preview/2.0/dwgconversion.json#L155:22
ExampleUrl: 2.0/examples/conversion/Conversion_Conversion.json#L8:16
❌ RESPONSE_SCHEMA_NOT_IN_SPEC Response statusCode 200 for operation Conversion_GetOperation has response body provided in the example, however the response does not have a "schema" defined in the swagger spec.
Url: Creator/preview/2.0/dwgconversion.json#L281:22
ExampleUrl: 2.0/examples/conversion/Conversion_GetOperationStillRunning.json#L7:16
❌ RESPONSE_SCHEMA_NOT_IN_SPEC Response statusCode 200 for operation Conversion_GetOperation has response body provided in the example, however the response does not have a "schema" defined in the swagger spec.
Url: Creator/preview/2.0/dwgconversion.json#L281:22
ExampleUrl: 2.0/examples/conversion/Conversion_GetOperation.json#L7:16
❌ RESPONSE_SCHEMA_NOT_IN_SPEC Response statusCode 200 for operation Tileset_Create has response body provided in the example, however the response does not have a "schema" defined in the swagger spec.
Url: Creator/preview/2.0/tileset.json#L130:22
ExampleUrl: 2.0/examples/tileset/Tileset_Create.json#L7:16
❌ RESPONSE_SCHEMA_NOT_IN_SPEC Response statusCode 200 for operation Tileset_GetOperation has response body provided in the example, however the response does not have a "schema" defined in the swagger spec.
Url: Creator/preview/2.0/tileset.json#L256:22
ExampleUrl: 2.0/examples/tileset/Tileset_GetOperationStillRunning.json#L7:16
❌ RESPONSE_SCHEMA_NOT_IN_SPEC Response statusCode 200 for operation Tileset_GetOperation has response body provided in the example, however the response does not have a "schema" defined in the swagger spec.
Url: Creator/preview/2.0/tileset.json#L256:22
ExampleUrl: 2.0/examples/tileset/Tileset_GetOperation.json#L7:16
❌ INVALID_TYPE Expected type number but found type string
Url: Creator/preview/2.0/wfs.json#L92:16
ExampleUrl: 2.0/examples/wfs/WFS_GetFeatures.json#L8:13
❌ RESPONSE_SCHEMA_NOT_IN_SPEC Response statusCode 400 for operation Alias_Create has response body provided in the example, however the response does not have a "schema" defined in the swagger spec.
Url: Alias/preview/2.0/alias.json#L193:22
ExampleUrl: preview/2.0/examples/Alias_Create.json#L7:16
❌ RESPONSE_SCHEMA_NOT_IN_SPEC Response statusCode 401 for operation Alias_Create has response body provided in the example, however the response does not have a "schema" defined in the swagger spec.
Url: Alias/preview/2.0/alias.json#L193:22
ExampleUrl: preview/2.0/examples/Alias_Create.json#L7:16
❌ RESPONSE_SCHEMA_NOT_IN_SPEC Response statusCode 403 for operation Alias_Create has response body provided in the example, however the response does not have a "schema" defined in the swagger spec.
Url: Alias/preview/2.0/alias.json#L193:22
ExampleUrl: preview/2.0/examples/Alias_Create.json#L7:16
❌ RESPONSE_SCHEMA_NOT_IN_SPEC Response statusCode 404 for operation Alias_Create has response body provided in the example, however the response does not have a "schema" defined in the swagger spec.
Url: Alias/preview/2.0/alias.json#L193:22
ExampleUrl: preview/2.0/examples/Alias_Create.json#L7:16
❌ RESPONSE_SCHEMA_NOT_IN_SPEC Response statusCode 500 for operation Alias_Create has response body provided in the example, however the response does not have a "schema" defined in the swagger spec.
Url: Alias/preview/2.0/alias.json#L193:22
ExampleUrl: preview/2.0/examples/Alias_Create.json#L7:16
❌ RESPONSE_SCHEMA_NOT_IN_SPEC Response statusCode 400 for operation Alias_List has response body provided in the example, however the response does not have a "schema" defined in the swagger spec.
Url: Alias/preview/2.0/alias.json#L240:22
ExampleUrl: preview/2.0/examples/Alias_List.json#L7:16
❌ RESPONSE_SCHEMA_NOT_IN_SPEC Response statusCode 401 for operation Alias_List has response body provided in the example, however the response does not have a "schema" defined in the swagger spec.
Url: Alias/preview/2.0/alias.json#L240:22
ExampleUrl: preview/2.0/examples/Alias_List.json#L7:16
❌ RESPONSE_SCHEMA_NOT_IN_SPEC Response statusCode 403 for operation Alias_List has response body provided in the example, however the response does not have a "schema" defined in the swagger spec.
Url: Alias/preview/2.0/alias.json#L240:22
ExampleUrl: preview/2.0/examples/Alias_List.json#L7:16
❌ RESPONSE_SCHEMA_NOT_IN_SPEC Response statusCode 404 for operation Alias_List has response body provided in the example, however the response does not have a "schema" defined in the swagger spec.
Url: Alias/preview/2.0/alias.json#L240:22
ExampleUrl: preview/2.0/examples/Alias_List.json#L7:16
❌ RESPONSE_SCHEMA_NOT_IN_SPEC Response statusCode 500 for operation Alias_List has response body provided in the example, however the response does not have a "schema" defined in the swagger spec.
Url: Alias/preview/2.0/alias.json#L240:22
ExampleUrl: preview/2.0/examples/Alias_List.json#L7:16
❌ RESPONSE_SCHEMA_NOT_IN_SPEC Response statusCode 400 for operation Alias_Assign has response body provided in the example, however the response does not have a "schema" defined in the swagger spec.
Url: Alias/preview/2.0/alias.json#L289:22
ExampleUrl: preview/2.0/examples/Alias_Assign.json#L9:16
❌ RESPONSE_SCHEMA_NOT_IN_SPEC Response statusCode 401 for operation Alias_Assign has response body provided in the example, however the response does not have a "schema" defined in the swagger spec.
Url: Alias/preview/2.0/alias.json#L289:22
ExampleUrl: preview/2.0/examples/Alias_Assign.json#L9:16
❌ RESPONSE_SCHEMA_NOT_IN_SPEC Response statusCode 403 for operation Alias_Assign has response body provided in the example, however the response does not have a "schema" defined in the swagger spec.
Url: Alias/preview/2.0/alias.json#L289:22
ExampleUrl: preview/2.0/examples/Alias_Assign.json#L9:16
❌ RESPONSE_SCHEMA_NOT_IN_SPEC Response statusCode 404 for operation Alias_Assign has response body provided in the example, however the response does not have a "schema" defined in the swagger spec.
Url: Alias/preview/2.0/alias.json#L289:22
ExampleUrl: preview/2.0/examples/Alias_Assign.json#L9:16
❌ RESPONSE_SCHEMA_NOT_IN_SPEC Response statusCode 500 for operation Alias_Assign has response body provided in the example, however the response does not have a "schema" defined in the swagger spec.
Url: Alias/preview/2.0/alias.json#L289:22
ExampleUrl: preview/2.0/examples/Alias_Assign.json#L9:16
❌ RESPONSE_SCHEMA_NOT_IN_SPEC Response statusCode 400 for operation Alias_Delete has response body provided in the example, however the response does not have a "schema" defined in the swagger spec.
Url: Alias/preview/2.0/alias.json#L333:22
ExampleUrl: preview/2.0/examples/Alias_Delete.json#L8:16
❌ RESPONSE_SCHEMA_NOT_IN_SPEC Response statusCode 401 for operation Alias_Delete has response body provided in the example, however the response does not have a "schema" defined in the swagger spec.
Url: Alias/preview/2.0/alias.json#L333:22
ExampleUrl: preview/2.0/examples/Alias_Delete.json#L8:16
❌ RESPONSE_SCHEMA_NOT_IN_SPEC Response statusCode 403 for operation Alias_Delete has response body provided in the example, however the response does not have a "schema" defined in the swagger spec.
Url: Alias/preview/2.0/alias.json#L333:22
ExampleUrl: preview/2.0/examples/Alias_Delete.json#L8:16
❌ RESPONSE_SCHEMA_NOT_IN_SPEC Response statusCode 404 for operation Alias_Delete has response body provided in the example, however the response does not have a "schema" defined in the swagger spec.
Url: Alias/preview/2.0/alias.json#L333:22
ExampleUrl: preview/2.0/examples/Alias_Delete.json#L8:16
❌ RESPONSE_SCHEMA_NOT_IN_SPEC Response statusCode 500 for operation Alias_Delete has response body provided in the example, however the response does not have a "schema" defined in the swagger spec.
Url: Alias/preview/2.0/alias.json#L333:22
ExampleUrl: preview/2.0/examples/Alias_Delete.json#L8:16
❌ RESPONSE_SCHEMA_NOT_IN_SPEC Response statusCode 400 for operation Alias_GetDetails has response body provided in the example, however the response does not have a "schema" defined in the swagger spec.
Url: Alias/preview/2.0/alias.json#L374:22
ExampleUrl: preview/2.0/examples/Alias_GetDetails.json#L8:16
❌ RESPONSE_SCHEMA_NOT_IN_SPEC Response statusCode 401 for operation Alias_GetDetails has response body provided in the example, however the response does not have a "schema" defined in the swagger spec.
Url: Alias/preview/2.0/alias.json#L374:22
ExampleUrl: preview/2.0/examples/Alias_GetDetails.json#L8:16
❌ RESPONSE_SCHEMA_NOT_IN_SPEC Response statusCode 403 for operation Alias_GetDetails has response body provided in the example, however the response does not have a "schema" defined in the swagger spec.
Url: Alias/preview/2.0/alias.json#L374:22
ExampleUrl: preview/2.0/examples/Alias_GetDetails.json#L8:16
❌ RESPONSE_SCHEMA_NOT_IN_SPEC Response statusCode 404 for operation Alias_GetDetails has response body provided in the example, however the response does not have a "schema" defined in the swagger spec.
Url: Alias/preview/2.0/alias.json#L374:22
ExampleUrl: preview/2.0/examples/Alias_GetDetails.json#L8:16
❌ RESPONSE_SCHEMA_NOT_IN_SPEC Response statusCode 500 for operation Alias_GetDetails has response body provided in the example, however the response does not have a "schema" defined in the swagger spec.
Url: Alias/preview/2.0/alias.json#L374:22
ExampleUrl: preview/2.0/examples/Alias_GetDetails.json#L8:16
❌ INVALID_TYPE Expected type array but found type number
Url: DEM/preview/1.0/elevation.json#L175:22
ExampleUrl: preview/1.0/examples/GetDataForPoints.json#L5:15
❌ INVALID_TYPE Expected type array but found type string
Url: DEM/preview/1.0/elevation.json#L175:22
ExampleUrl: preview/1.0/examples/GetDataForPoints.json#L5:15
❌ RESPONSE_SCHEMA_NOT_IN_SPEC Response statusCode 400 for operation Elevation_GetDataForPoints has response body provided in the example, however the response does not have a "schema" defined in the swagger spec.
Url: DEM/preview/1.0/elevation.json#L187:22
ExampleUrl: preview/1.0/examples/GetDataForPoints.json#L8:16
❌ RESPONSE_SCHEMA_NOT_IN_SPEC Response statusCode 401 for operation Elevation_GetDataForPoints has response body provided in the example, however the response does not have a "schema" defined in the swagger spec.
Url: DEM/preview/1.0/elevation.json#L187:22
ExampleUrl: preview/1.0/examples/GetDataForPoints.json#L8:16
❌ RESPONSE_SCHEMA_NOT_IN_SPEC Response statusCode 403 for operation Elevation_GetDataForPoints has response body provided in the example, however the response does not have a "schema" defined in the swagger spec.
Url: DEM/preview/1.0/elevation.json#L187:22
ExampleUrl: preview/1.0/examples/GetDataForPoints.json#L8:16
❌ RESPONSE_SCHEMA_NOT_IN_SPEC Response statusCode 404 for operation Elevation_GetDataForPoints has response body provided in the example, however the response does not have a "schema" defined in the swagger spec.
Url: DEM/preview/1.0/elevation.json#L187:22
ExampleUrl: preview/1.0/examples/GetDataForPoints.json#L8:16
❌ RESPONSE_SCHEMA_NOT_IN_SPEC Response statusCode 500 for operation Elevation_GetDataForPoints has response body provided in the example, however the response does not have a "schema" defined in the swagger spec.
Url: DEM/preview/1.0/elevation.json#L187:22
ExampleUrl: preview/1.0/examples/GetDataForPoints.json#L8:16
❌ RESPONSE_SCHEMA_NOT_IN_SPEC Response statusCode 400 for operation Elevation_PostDataForPoints has response body provided in the example, however the response does not have a "schema" defined in the swagger spec.
Url: DEM/preview/1.0/elevation.json#L246:22
ExampleUrl: preview/1.0/examples/PostDataForPoints.json#L17:16
❌ RESPONSE_SCHEMA_NOT_IN_SPEC Response statusCode 401 for operation Elevation_PostDataForPoints has response body provided in the example, however the response does not have a "schema" defined in the swagger spec.
Url: DEM/preview/1.0/elevation.json#L246:22
ExampleUrl: preview/1.0/examples/PostDataForPoints.json#L17:16
View more details on openapi-pipeline-app