[TSP] Generate all MGMT tsp files. January 22 #27471
Draft
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Next Steps to MergeNext steps that must be taken to merge this PR:
|
Swagger Validation Report
|
| Rule | Message |
|---|---|
|
"new":"https://github.com/Azure/azure-rest-api-specs/blob/73df454d791166fcebd74c4cab9981e491523cfd/specification/liftrqumulo/Qumulo.Management/resources.json", "old":"https://github.com/Azure/azure-rest-api-specs/blob/main/specification/liftrqumulo/Qumulo.Management/resources.json", "details":"Breaking change detector (OAD) invoked AutoRest. AutoRest threw a runtime error. First 6 lines of stack trace follow, indexed. First line should contain AutoRest command line invocation details. Second line should contain the main message reported by AutoRest. ==================== 1: Command failed: node "/mnt/vss/_work/_tasks/AzureApiValidation_5654d05d-82c1-48da-ad8f-161b817f6d41/0.0.72/common/temp/node_modules/.pnpm/@Azure+oad@0.10.4/node_modules/autorest/dist/app.js" --v2 --input-file=/mnt/vss/_work/1/same-version-c93b354fd9c14905bb574a8834c4d69b/specification/liftrqumulo/Qumulo.Management/resources.json --output-artifact=swagger-document.json --output-artifact=swagger-document.map --output-file=old --output-folder=/tmp -------------------- 2: FATAL: swagger-document/loader - FAILED -------------------- 3: FATAL: Error: File 'file:///mnt/vss/_work/1/same-version-c93b354fd9c14905bb574a8834c4d69b/specification/liftrqumulo/Qumulo.Management/resources.json' is not a valid OpenAPI 2.0 definition (expected 'swagger: 2.0') -------------------- 4: Error: File 'file:///mnt/vss/_work/1/same-version-c93b354fd9c14905bb574a8834c4d69b/specification/liftrqumulo/Qumulo.Management/resources.json' is not a valid OpenAPI 2.0 definition (expected 'swagger: 2.0') --------------------" |
|
"new":"https://github.com/Azure/azure-rest-api-specs/blob/73df454d791166fcebd74c4cab9981e491523cfd/specification/networkanalytics/NetworkAnalytics.Management/resources.json", "old":"https://github.com/Azure/azure-rest-api-specs/blob/main/specification/networkanalytics/NetworkAnalytics.Management/resources.json", "details":"Breaking change detector (OAD) invoked AutoRest. AutoRest threw a runtime error. First 6 lines of stack trace follow, indexed. First line should contain AutoRest command line invocation details. Second line should contain the main message reported by AutoRest. ==================== 1: Command failed: node "/mnt/vss/_work/_tasks/AzureApiValidation_5654d05d-82c1-48da-ad8f-161b817f6d41/0.0.72/common/temp/node_modules/.pnpm/@Azure+oad@0.10.4/node_modules/autorest/dist/app.js" --v2 --input-file=/mnt/vss/_work/1/same-version-c93b354fd9c14905bb574a8834c4d69b/specification/networkanalytics/NetworkAnalytics.Management/resources.json --output-artifact=swagger-document.json --output-artifact=swagger-document.map --output-file=old --output-folder=/tmp -------------------- 2: FATAL: swagger-document/loader - FAILED -------------------- 3: FATAL: Error: File 'file:///mnt/vss/_work/1/same-version-c93b354fd9c14905bb574a8834c4d69b/specification/networkanalytics/NetworkAnalytics.Management/resources.json' is not a valid OpenAPI 2.0 definition (expected 'swagger: 2.0') -------------------- 4: Error: File 'file:///mnt/vss/_work/1/same-version-c93b354fd9c14905bb574a8834c4d69b/specification/networkanalytics/NetworkAnalytics.Management/resources.json' is not a valid OpenAPI 2.0 definition (expected 'swagger: 2.0') --------------------" |
|
"new":"https://github.com/Azure/azure-rest-api-specs/blob/73df454d791166fcebd74c4cab9981e491523cfd/specification/playwrighttesting/PlaywrightTesting.Management/resources.json", "old":"https://github.com/Azure/azure-rest-api-specs/blob/main/specification/playwrighttesting/PlaywrightTesting.Management/resources.json", "details":"Breaking change detector (OAD) invoked AutoRest. AutoRest threw a runtime error. First 6 lines of stack trace follow, indexed. First line should contain AutoRest command line invocation details. Second line should contain the main message reported by AutoRest. ==================== 1: Command failed: node "/mnt/vss/_work/_tasks/AzureApiValidation_5654d05d-82c1-48da-ad8f-161b817f6d41/0.0.72/common/temp/node_modules/.pnpm/@Azure+oad@0.10.4/node_modules/autorest/dist/app.js" --v2 --input-file=/mnt/vss/_work/1/same-version-c93b354fd9c14905bb574a8834c4d69b/specification/playwrighttesting/PlaywrightTesting.Management/resources.json --output-artifact=swagger-document.json --output-artifact=swagger-document.map --output-file=old --output-folder=/tmp -------------------- 2: FATAL: swagger-document/loader - FAILED -------------------- 3: FATAL: Error: File 'file:///mnt/vss/_work/1/same-version-c93b354fd9c14905bb574a8834c4d69b/specification/playwrighttesting/PlaywrightTesting.Management/resources.json' is not a valid OpenAPI 2.0 definition (expected 'swagger: 2.0') -------------------- 4: Error: File 'file:///mnt/vss/_work/1/same-version-c93b354fd9c14905bb574a8834c4d69b/specification/playwrighttesting/PlaywrightTesting.Management/resources.json' is not a valid OpenAPI 2.0 definition (expected 'swagger: 2.0') --------------------" |
|
"new":"https://github.com/Azure/azure-rest-api-specs/blob/73df454d791166fcebd74c4cab9981e491523cfd/specification/servicenetworking/ServiceNetworking.Management/resources.json", "old":"https://github.com/Azure/azure-rest-api-specs/blob/main/specification/servicenetworking/ServiceNetworking.Management/resources.json", "details":"Breaking change detector (OAD) invoked AutoRest. AutoRest threw a runtime error. First 6 lines of stack trace follow, indexed. First line should contain AutoRest command line invocation details. Second line should contain the main message reported by AutoRest. ==================== 1: Command failed: node "/mnt/vss/_work/_tasks/AzureApiValidation_5654d05d-82c1-48da-ad8f-161b817f6d41/0.0.72/common/temp/node_modules/.pnpm/@Azure+oad@0.10.4/node_modules/autorest/dist/app.js" --v2 --input-file=/mnt/vss/_work/1/same-version-c93b354fd9c14905bb574a8834c4d69b/specification/servicenetworking/ServiceNetworking.Management/resources.json --output-artifact=swagger-document.json --output-artifact=swagger-document.map --output-file=old --output-folder=/tmp -------------------- 2: FATAL: swagger-document/loader - FAILED -------------------- 3: FATAL: Error: File 'file:///mnt/vss/_work/1/same-version-c93b354fd9c14905bb574a8834c4d69b/specification/servicenetworking/ServiceNetworking.Management/resources.json' is not a valid OpenAPI 2.0 definition (expected 'swagger: 2.0') -------------------- 4: Error: File 'file:///mnt/vss/_work/1/same-version-c93b354fd9c14905bb574a8834c4d69b/specification/servicenetworking/ServiceNetworking.Management/resources.json' is not a valid OpenAPI 2.0 definition (expected 'swagger: 2.0') --------------------" |
|
"new":"https://github.com/Azure/azure-rest-api-specs/blob/73df454d791166fcebd74c4cab9981e491523cfd/specification/sphere/Sphere.Management/resources.json", "old":"https://github.com/Azure/azure-rest-api-specs/blob/main/specification/sphere/Sphere.Management/resources.json", "details":"Breaking change detector (OAD) invoked AutoRest. AutoRest threw a runtime error. First 6 lines of stack trace follow, indexed. First line should contain AutoRest command line invocation details. Second line should contain the main message reported by AutoRest. ==================== 1: Command failed: node "/mnt/vss/_work/_tasks/AzureApiValidation_5654d05d-82c1-48da-ad8f-161b817f6d41/0.0.72/common/temp/node_modules/.pnpm/@Azure+oad@0.10.4/node_modules/autorest/dist/app.js" --v2 --input-file=/mnt/vss/_work/1/same-version-c93b354fd9c14905bb574a8834c4d69b/specification/sphere/Sphere.Management/resources.json --output-artifact=swagger-document.json --output-artifact=swagger-document.map --output-file=old --output-folder=/tmp -------------------- 2: FATAL: swagger-document/loader - FAILED -------------------- 3: FATAL: Error: File 'file:///mnt/vss/_work/1/same-version-c93b354fd9c14905bb574a8834c4d69b/specification/sphere/Sphere.Management/resources.json' is not a valid OpenAPI 2.0 definition (expected 'swagger: 2.0') -------------------- 4: Error: File 'file:///mnt/vss/_work/1/same-version-c93b354fd9c14905bb574a8834c4d69b/specification/sphere/Sphere.Management/resources.json' is not a valid OpenAPI 2.0 definition (expected 'swagger: 2.0') --------------------" |
️❌Breaking Change(Cross-Version): 2 Errors, 0 Warnings failed [Detail]
The following breaking changes are detected by comparison with the latest stable version:
| Rule | Message |
|---|---|
|
"new":"https://github.com/Azure/azure-rest-api-specs/blob/73df454d791166fcebd74c4cab9981e491523cfd/specification/containerservice/resource-manager/Microsoft.ContainerService/fleet/ContainerServiceFleet.Management/resource-manager/Microsoft.ContainerService/stable/2023-10-15/fleets.json", "old":"https://github.com/Azure/azure-rest-api-specs/blob/main/specification/containerservice/resource-manager/Microsoft.ContainerService/fleet/stable/2023-10-15/fleets.json", "details":"Breaking change detector (OAD) invoked AutoRest. AutoRest threw a runtime error. First 6 lines of stack trace follow, indexed. First line should contain AutoRest command line invocation details. Second line should contain the main message reported by AutoRest. ==================== 1: Command failed: node "/mnt/vss/_work/_tasks/AzureApiValidation_5654d05d-82c1-48da-ad8f-161b817f6d41/0.0.72/common/temp/node_modules/.pnpm/@Azure+oad@0.10.4/node_modules/autorest/dist/app.js" --v2 --input-file=specification/containerservice/resource-manager/Microsoft.ContainerService/fleet/ContainerServiceFleet.Management/resource-manager/Microsoft.ContainerService/stable/2023-10-15/fleets.json --output-artifact=swagger-document.json --output-artifact=swagger-document.map --output-file=new --output-folder=/tmp -------------------- 2: ERROR: Referenced file 'file:///mnt/vss/_work/1/azure-rest-api-specs/specification/containerservice/resource-manager/Microsoft.ContainerService/fleet/common-types/resource-management/v3/types.json' not found -------------------- 3: - file:///mnt/vss/_work/1/azure-rest-api-specs/specification/containerservice/resource-manager/Microsoft.ContainerService/fleet/ContainerServiceFleet.Management/resource-manager/Microsoft.ContainerService/stable/2023-10-15/fleets.json:2712:10 ($.definitions.UpdateStatus.properties.error["$ref"]) -------------------- 4: FATAL: swagger-document/loader - FAILED -------------------- 5: FATAL: Error: [OperationAbortedException] Error occurred. Exiting. -------------------- 6: Process() cancelled due to exception : [OperationAbortedException] Error occurred. Exiting. --------------------" |
The following breaking changes are detected by comparison with the latest preview version:
| Rule | Message |
|---|---|
|
"new":"https://github.com/Azure/azure-rest-api-specs/blob/73df454d791166fcebd74c4cab9981e491523cfd/specification/containerservice/resource-manager/Microsoft.ContainerService/fleet/ContainerServiceFleet.Management/resource-manager/Microsoft.ContainerService/stable/2023-10-15/fleets.json", "old":"https://github.com/Azure/azure-rest-api-specs/blob/main/specification/containerservice/resource-manager/Microsoft.ContainerService/fleet/preview/2023-08-15-preview/fleets.json", "details":"Breaking change detector (OAD) invoked AutoRest. AutoRest threw a runtime error. First 6 lines of stack trace follow, indexed. First line should contain AutoRest command line invocation details. Second line should contain the main message reported by AutoRest. ==================== 1: Command failed: node "/mnt/vss/_work/_tasks/AzureApiValidation_5654d05d-82c1-48da-ad8f-161b817f6d41/0.0.72/common/temp/node_modules/.pnpm/@Azure+oad@0.10.4/node_modules/autorest/dist/app.js" --v2 --input-file=specification/containerservice/resource-manager/Microsoft.ContainerService/fleet/ContainerServiceFleet.Management/resource-manager/Microsoft.ContainerService/stable/2023-10-15/fleets.json --output-artifact=swagger-document.json --output-artifact=swagger-document.map --output-file=new --output-folder=/tmp -------------------- 2: ERROR: Referenced file 'file:///mnt/vss/_work/1/azure-rest-api-specs/specification/containerservice/resource-manager/Microsoft.ContainerService/fleet/common-types/resource-management/v3/types.json' not found -------------------- 3: - file:///mnt/vss/_work/1/azure-rest-api-specs/specification/containerservice/resource-manager/Microsoft.ContainerService/fleet/ContainerServiceFleet.Management/resource-manager/Microsoft.ContainerService/stable/2023-10-15/fleets.json:2712:10 ($.definitions.UpdateStatus.properties.error["$ref"]) -------------------- 4: FATAL: swagger-document/loader - FAILED -------------------- 5: FATAL: Error: [OperationAbortedException] Error occurred. Exiting. -------------------- 6: Process() cancelled due to exception : [OperationAbortedException] Error occurred. Exiting. --------------------" |
️🔄CredScan inProgress [Detail]
️❌LintDiff: 1 Errors, 0 Warnings failed [Detail]
| Rule | Message |
|---|---|
|
"details":""stack":"ResolverError: Error reading file \"/mnt/vss/_work/1/azure-rest-api-specs/specification/containerservice/resource-manager/Microsoft.ContainerService/fleet/common-types/resource-management/v3/types.json\"\n at onError (/mnt/vss/_work/_tasks/AzureApiValidation_5654d05d-82c1-48da-ad8f-161b817f6d41/0.0.72/common/temp/node_modules/.pnpm/@APIDevTools+json-schema-ref-parser@9.0.9/node_modules/@apidevtools/json-schema-ref-parser/lib/parse.js:92:16)\n at runMicrotasks ()\n at processTicksAndRejections (internal/process/task_queues.js:95:5)", "code":"ERESOLVER", "message":"Error reading file \"/mnt/vss/_work/1/azure-rest-api-specs/specification/containerservice/resource-manager/Microsoft.ContainerService/fleet/common-types/resource-management/v3/types.json\"", "source":"/mnt/vss/_work/1/azure-rest-api-specs/specification/containerservice/resource-manager/Microsoft.ContainerService/fleet/common-types/resource-management/v3/types.json", "path":null, "name":"ResolverError", "footprint":"null+/mnt/vss/_work/1/azure-rest-api-specs/specification/containerservice/resource-manager/Microsoft.ContainerService/fleet/common-types/resource-management/v3/types.json+ERESOLVER+Error reading file \"/mnt/vss/_work/1/azure-rest-api-specs/specification/containerservice/resource-manager/Microsoft.ContainerService/fleet/common-types/resource-management/v3/types.json\""" |
️❌Avocado: 308 Errors, 0 Warnings failed [Detail]
Only 20 items are listed, please refer to log for more details.
| Rule | Message |
|---|---|
|
Can not find readme.md in the folder. If no readme.md file, it will block SDK generation. folder: resource-manager/Microsoft.Advisor/stable/2020-01-01 |
|
Can not find readme.md in the folder. If no readme.md file, it will block SDK generation. folder: Microsoft.Advisor/stable/2020-01-01/examples |
|
Can not find readme.md in the folder. If no readme.md file, it will block SDK generation. folder: resource-manager/Microsoft.AgFoodPlatform/preview/2021-09-01-preview |
|
Can not find readme.md in the folder. If no readme.md file, it will block SDK generation. folder: Microsoft.AgFoodPlatform/preview/2021-09-01-preview/examples |
|
Can not find readme.md in the folder. If no readme.md file, it will block SDK generation. folder: resource-manager/Microsoft.AlertsManagement/preview/2019-05-05-preview |
|
Can not find readme.md in the folder. If no readme.md file, it will block SDK generation. folder: Microsoft.AlertsManagement/stable/2021-08-08/examples |
|
Can not find readme.md in the folder. If no readme.md file, it will block SDK generation. folder: resource-manager/Microsoft.AlertsManagement/stable/2021-08-08 |
|
Can not find readme.md in the folder. If no readme.md file, it will block SDK generation. folder: resource-manager/Microsoft.AnalysisServices/stable/2017-08-01 |
|
Can not find readme.md in the folder. If no readme.md file, it will block SDK generation. folder: Microsoft.AnalysisServices/stable/2017-08-01/examples |
|
Can not find readme.md in the folder. If no readme.md file, it will block SDK generation. folder: resource-manager/Microsoft.ApiCenter/preview/2023-07-01-preview |
|
Can not find readme.md in the folder. If no readme.md file, it will block SDK generation. folder: Microsoft.ApiCenter/preview/2023-07-01-preview/examples |
|
Can not find readme.md in the folder. If no readme.md file, it will block SDK generation. folder: Microsoft.App/stable/2023-05-01/examples |
|
Can not find readme.md in the folder. If no readme.md file, it will block SDK generation. folder: resource-manager/Microsoft.App/stable/2023-05-01 |
|
Can not find readme.md in the folder. If no readme.md file, it will block SDK generation. folder: resource-manager/Microsoft.AppComplianceAutomation/preview/2022-11-16-preview |
|
Can not find readme.md in the folder. If no readme.md file, it will block SDK generation. folder: Microsoft.AppComplianceAutomation/preview/2022-11-16-preview/examples |
|
Can not find readme.md in the folder. If no readme.md file, it will block SDK generation. folder: resource-manager/Microsoft.AppConfiguration/stable/2022-05-01 |
|
Can not find readme.md in the folder. If no readme.md file, it will block SDK generation. folder: Microsoft.AppConfiguration/stable/2022-05-01/examples |
|
Can not find readme.md in the folder. If no readme.md file, it will block SDK generation. folder: resource-manager/Microsoft.Attestation/preview/2021-06-01-preview |
|
Can not find readme.md in the folder. If no readme.md file, it will block SDK generation. folder: Microsoft.Attestation/preview/2021-06-01-preview/examples |
|
Can not find readme.md in the folder. If no readme.md file, it will block SDK generation. folder: Microsoft.Authorization/stable/2015-07-01/examples |
️️✔️SwaggerAPIView succeeded [Detail] [Expand]
️❌TypeSpecAPIView: 0 Errors, 157 Warnings failed [Detail]
Only 20 items are listed, please refer to log for more details.
| Rule | Message |
|---|---|
| "How to fix":"Check the detailed log and verify if the TypeSpec emitter is able to create API review file for the changes in PR." | |
| "How to fix":"Check the detailed log and verify if the TypeSpec emitter is able to create API review file for the changes in PR." | |
| "How to fix":"Check the detailed log and verify if the TypeSpec emitter is able to create API review file for the changes in PR." | |
| "How to fix":"Check the detailed log and verify if the TypeSpec emitter is able to create API review file for the changes in PR." | |
| "How to fix":"Check the detailed log and verify if the TypeSpec emitter is able to create API review file for the changes in PR." | |
| "How to fix":"Check the detailed log and verify if the TypeSpec emitter is able to create API review file for the changes in PR." | |
| "How to fix":"Check the detailed log and verify if the TypeSpec emitter is able to create API review file for the changes in PR." | |
| "How to fix":"Check the detailed log and verify if the TypeSpec emitter is able to create API review file for the changes in PR." | |
| "How to fix":"Check the detailed log and verify if the TypeSpec emitter is able to create API review file for the changes in PR." | |
| "How to fix":"Check the detailed log and verify if the TypeSpec emitter is able to create API review file for the changes in PR." | |
| "How to fix":"Check the detailed log and verify if the TypeSpec emitter is able to create API review file for the changes in PR." | |
| "How to fix":"Check the detailed log and verify if the TypeSpec emitter is able to create API review file for the changes in PR." | |
| "How to fix":"Check the detailed log and verify if the TypeSpec emitter is able to create API review file for the changes in PR." | |
| "How to fix":"Check the detailed log and verify if the TypeSpec emitter is able to create API review file for the changes in PR." | |
| "How to fix":"Check the detailed log and verify if the TypeSpec emitter is able to create API review file for the changes in PR." | |
| "How to fix":"Check the detailed log and verify if the TypeSpec emitter is able to create API review file for the changes in PR." | |
| "How to fix":"Check the detailed log and verify if the TypeSpec emitter is able to create API review file for the changes in PR." | |
| "How to fix":"Check the detailed log and verify if the TypeSpec emitter is able to create API review file for the changes in PR." | |
| "How to fix":"Check the detailed log and verify if the TypeSpec emitter is able to create API review file for the changes in PR." | |
| "How to fix":"Check the detailed log and verify if the TypeSpec emitter is able to create API review file for the changes in PR." |
️❌ModelValidation: 311 Errors, 0 Warnings failed [Detail]
Only 20 items are listed, please refer to log for more details.
️❌SemanticValidation: 747 Errors, 0 Warnings failed [Detail]
Only 20 items are listed, please refer to log for more details.
| Rule | Message |
|---|---|
|
Unexpected internal error: ENOENT: no such file or directory, open '/mnt/vss/_work/1/azure-rest-api-specs/specification/advisor/common-types/resource-management/v3/types.json' Error: ENOENT: no such file or directory, open '/mnt/vss/_work/1/azure-rest-api-specs/specification/advisor/common-types/resource-management/v3/types.json' JsonUrl: Microsoft.Advisor/stable/2020-01-01/advisor.json |
|
Missing required property: swagger JsonUrl: specification/advisor/Advisor.Management/resources.json |
|
Missing required property: info JsonUrl: specification/advisor/Advisor.Management/resources.json |
|
Missing required property: paths JsonUrl: specification/advisor/Advisor.Management/resources.json |
|
Additional properties not allowed: Resources JsonUrl: specification/advisor/Advisor.Management/resources.json |
|
Unexpected internal error: ENOENT: no such file or directory, open '/mnt/vss/_work/1/azure-rest-api-specs/specification/agrifood/common-types/resource-management/v3/types.json' Error: ENOENT: no such file or directory, open '/mnt/vss/_work/1/azure-rest-api-specs/specification/agrifood/common-types/resource-management/v3/types.json' JsonUrl: Microsoft.AgFoodPlatform/preview/2021-09-01-preview/agfood.json |
|
Missing required property: swagger JsonUrl: specification/agrifood/AgFoodPlatform.Management/resources.json |
|
Missing required property: info JsonUrl: specification/agrifood/AgFoodPlatform.Management/resources.json |
|
Missing required property: paths JsonUrl: specification/agrifood/AgFoodPlatform.Management/resources.json |
|
Additional properties not allowed: Resources JsonUrl: specification/agrifood/AgFoodPlatform.Management/resources.json |
|
Unexpected internal error: ENOENT: no such file or directory, open '/mnt/vss/_work/1/azure-rest-api-specs/specification/alertsmanagement/common-types/resource-management/v3/types.json' Error: ENOENT: no such file or directory, open '/mnt/vss/_work/1/azure-rest-api-specs/specification/alertsmanagement/common-types/resource-management/v3/types.json' JsonUrl: Microsoft.AlertsManagement/preview/2019-05-05-preview/openapi.json |
|
Unexpected internal error: ENOENT: no such file or directory, open '/mnt/vss/_work/1/azure-rest-api-specs/specification/alertsmanagement/common-types/resource-management/v3/types.json' Error: ENOENT: no such file or directory, open '/mnt/vss/_work/1/azure-rest-api-specs/specification/alertsmanagement/common-types/resource-management/v3/types.json' JsonUrl: Microsoft.AlertsManagement/stable/2021-08-08/openapi.json |
|
Missing required property: swagger JsonUrl: specification/alertsmanagement/AlertsManagement.Management/resources.json |
|
Missing required property: info JsonUrl: specification/alertsmanagement/AlertsManagement.Management/resources.json |
|
Missing required property: paths JsonUrl: specification/alertsmanagement/AlertsManagement.Management/resources.json |
|
Additional properties not allowed: Resources JsonUrl: specification/alertsmanagement/AlertsManagement.Management/resources.json |
|
Unexpected internal error: ENOENT: no such file or directory, open '/mnt/vss/_work/1/azure-rest-api-specs/specification/analysisservices/common-types/resource-management/v3/types.json' Error: ENOENT: no such file or directory, open '/mnt/vss/_work/1/azure-rest-api-specs/specification/analysisservices/common-types/resource-management/v3/types.json' JsonUrl: Microsoft.AnalysisServices/stable/2017-08-01/analysisservices.json |
|
Missing required property: swagger JsonUrl: specification/analysisservices/Analysis.Management/resources.json |
|
Missing required property: info JsonUrl: specification/analysisservices/Analysis.Management/resources.json |
|
Missing required property: paths JsonUrl: specification/analysisservices/Analysis.Management/resources.json |
️🔄PoliCheck inProgress [Detail]
️❌SpellCheck: 36 Errors, 0 Warnings failed [Detail]
Only 20 items are listed, please refer to log for more details.
️️✔️Lint(RPaaS) succeeded [Detail]
| Rule | Message |
|---|---|
|
"details":""stack":"ResolverError: Error reading file \"/mnt/vss/_work/1/azure-rest-api-specs/specification/containerservice/resource-manager/Microsoft.ContainerService/fleet/common-types/resource-management/v3/types.json\"\n at onError (/mnt/vss/_work/_tasks/AzureApiValidation_5654d05d-82c1-48da-ad8f-161b817f6d41/0.0.72/common/temp/node_modules/.pnpm/@APIDevTools+json-schema-ref-parser@9.0.9/node_modules/@apidevtools/json-schema-ref-parser/lib/parse.js:92:16)\n at runMicrotasks ()\n at processTicksAndRejections (internal/process/task_queues.js:95:5)", "code":"ERESOLVER", "message":"Error reading file \"/mnt/vss/_work/1/azure-rest-api-specs/specification/containerservice/resource-manager/Microsoft.ContainerService/fleet/common-types/resource-management/v3/types.json\"", "source":"/mnt/vss/_work/1/azure-rest-api-specs/specification/containerservice/resource-manager/Microsoft.ContainerService/fleet/common-types/resource-management/v3/types.json", "path":null, "name":"ResolverError", "footprint":"null+/mnt/vss/_work/1/azure-rest-api-specs/specification/containerservice/resource-manager/Microsoft.ContainerService/fleet/common-types/resource-management/v3/types.json+ERESOLVER+Error reading file \"/mnt/vss/_work/1/azure-rest-api-specs/specification/containerservice/resource-manager/Microsoft.ContainerService/fleet/common-types/resource-management/v3/types.json\""" |
️❌PR Summary: 0 Errors, 0 Warnings failed [Detail]
️️✔️Automated merging requirements met succeeded [Detail] [Expand]
Swagger Generation Artifacts
|
| Rule | Message |
|---|---|
|
"logUrl":"https://apidrop.visualstudio.com/Content%20CI/_build/results?buildId=409390&view=logs&j=fd490c07-0b22-5182-fac9-6d67fe1e939b", "detail":"Run.ps1 failed with exit code 1 " |
️️✔️SDK Breaking Change Tracking succeeded [Detail] [Expand]
Breaking Changes Tracking
️🔄 $(sdkName) inProgress [Detail]
Generated ApiView
|
AzureRestAPISpecReview
added
CI-RpaaSRPNotInPrivateRepo
resource-manager
RPaaS
TypeSpec
|
Hi @dvbb This PR was flagged for attempting to introduce a new RP namespace to the main branch without first merging the new RP to the RPSaaSMaster branch. Please add the new RP in a merge to RPSaaSMaster before continuing the merge to main. |
|
PR validation pipeline can not start as the pull request is not merged or mergeable - most likely it has merge conflicts. |
|
PR validation pipeline can not start as the pull request is not merged or mergeable - most likely it has merge conflicts. |
|
PR validation pipeline can not start as the pull request is not merged or mergeable - most likely it has merge conflicts. |
|
PR validation pipeline can not start as the pull request is not merged or mergeable - most likely it has merge conflicts. |
|
PR validation pipeline can not start as the pull request is not merged or mergeable - most likely it has merge conflicts. |
|
PR validation pipeline can not start as the pull request is not merged or mergeable - most likely it has merge conflicts. |
|
PR validation pipeline can not start as the pull request is not merged or mergeable - most likely it has merge conflicts. |
|
PR validation pipeline can not start as the pull request is not merged or mergeable - most likely it has merge conflicts. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
ARM (Control Plane) API Specification Update Pull Request
Tip
Overwhelmed by all this guidance? See the
Getting helpsection at the bottom of this PR description.Note
As of January 2024 there is no PR assignee. This is expected. See https://aka.ms/azsdk/pr-arm-review.
PR review workflow diagram
Please understand this diagram before proceeding. It explains how to get your PR approved & merged.
Click here to see the details of Step 1
Breaking changes review (Diagram Step 1)
If the automation determines you have breaking changes, i.e. Step 1 from the diagram applies to you,
you must follow the breaking changes process.
IMPORTANT This applies even if:
Such claims must be reviewed, and the process is the same.
Click here to see the details of Step 2
ARM API changes review (Diagram Step 2)
Click here to see the diagram footnotes
Diagram footnotes
[1] See ARM review queue (for PR merge queues, see [2]).
[2] public repo merge queue, private repo merge queue (for ARM review queue, [1])
The ARM reviewer on-call engineer visits the merge queue twice a day, so the approximate ETA for merges is 12 - 24 hours.
Purpose of this PR
What's the purpose of this PR? Check the specific option that applies. This is mandatory!
Due diligence checklist
To merge this PR, you must go through the following checklist and confirm you understood
and followed the instructions by checking all the boxes:
ARM resource provider contract and
REST guidelines (estimated time: 4 hours).
I understand this is required before I can proceed to the diagram Step 2, "ARM API changes review", for this PR.
Additional information
Viewing API changes
For convenient view of the API changes made by this PR, refer to the URLs provided in the table
in the
Generated ApiViewcomment added to this PR. You can use ApiView to show API versions diff.Suppressing failures
If one or multiple validation error/warning suppression(s) is detected in your PR, please follow the
suppressions guide to get approval.
Getting help
Purpose of this PRandDue diligence checklist.Next Steps to Mergecomment. It will appear within few minutes of submitting this PR and will continue to be up-to-date with current PR state.and https://aka.ms/ci-fix.
queuedstate, please add a comment with contents/azp run.This should result in a new comment denoting a
PR validation pipelinehas started and the checks should be updated after few minutes.