Open konrad-jamrozik opened 7 months ago
In general, we should nicely wrap relevant AutoRest exceptions. Another, different case (from Teams, here, by Zhenhua Hu):
{
"type": "AutoRest exception",
"message": "!Error: There are multiple operations defined for 'get: /providers/Microsoft.PortalServices/operations'. You are probably trying to use an input with multiple API versions with an autorest V2 generator, and that will not work.",
"readmeUrl": "[https://github.com/Azure/azure-rest-api-specs-pr/blob/RPSaaSDev/specification/portalservices/resource-manager/readme.md",](https://github.com/Azure/azure-rest-api-specs-pr/blob/RPSaaSDev/specification/portalservices/resource-manager/readme.md%22,)
"tag": "package-2023-08-01-preview",
"context": "before"
},
Bug reported in Teams by Suhas Rao here
Affected PR:
Root-cause
The file https://github.com/Azure/azure-rest-api-specs/blob/main/specification/monitor/resource-manager/Microsoft.Monitor/stable/2023-04-03/monitoringAccounts_API.json
is missing from the
RPSaaSMaster
branch but it is mentioned in the processed README resulting in error of:Root-cause analysis
From the build log:
We can see:
From the check run we can get link to README.md:
In both cases we can see that Tag: package-2023-04 has input files:
Microsoft.Monitor/stable/2023-04-03/monitoringAccounts_API.json
At the same time we can see that
specification/monitor/resource-manager/Microsoft.Monitor
does not even havestable
directory, in bothRPSaaSMaster
and the "new" commit.However, it is present in public main:
As well as private main:
Hence the issue is that the file is missing from
RPSaaSMaster
Related work