Admin Swagger Specs for Commerce, Fabric, and Infrastructure Insights#1592
Admin Swagger Specs for Commerce, Fabric, and Infrastructure Insights#1592sarangan12 merged 8 commits intoAzure:currentfrom
Conversation
|
@deathly809, |
|
@deathly809 Please take a look at the build jobs here: https://travis-ci.org/Azure/azure-rest-api-specs/builds/268547010?utm_source=github_status&utm_medium=notification There are 2 sets of jobs: Regular & Allowed Failure Jobs. Here Regular Jobs must be completed successfully for approval. In this case, one of the regular jobs failed. Take a look at: https://travis-ci.org/Azure/azure-rest-api-specs/jobs/268547011 There are 25 errors which are listed at https://travis-ci.org/Azure/azure-rest-api-specs/jobs/268547011#L3678. I have looked at these errors and the messages seem to be self explanatory. Please fix them and update the PR |
|
I have gone through and fixed all the issues except one specific error. It says I cannot use x-ms-headers but the RP team returns the location to an operation status in the headers. What should I do about the header issue? Is there a way to get a waiver? |
| - "Microsoft.Fabric.Admin/2016-05-01/Volume.json" | ||
| - "Microsoft.Fabric.Admin/2016-05-01/LogicalSubnet.json" | ||
| - "Microsoft.Fabric.Admin/2016-05-01/MacAddressPool.json" | ||
| - "Microsoft.Fabric.Admin/2016-05-01/Operations.json" |
There was a problem hiding this comment.
The name of the file is oncorrect. operations.json vs Operations.json. Please fix
|
Hi There, I am the AutoRest Linter Azure bot. I am here to help. My task is to analyze the situation from the AutoRest linter perspective. Please review the below analysis result: File: File: File: AutoRest Linter Guidelines | AutoRest Linter Issues Send feedback and make AutoRest Linter Azure Bot smarter day by day! Thanks for your co-operation. |
|
Hi There, I am the AutoRest Linter Azure bot. I am here to help. My task is to analyze the situation from the AutoRest linter perspective. Please review the below analysis result: File: File: File: AutoRest Linter Guidelines | AutoRest Linter Issues Send feedback and make AutoRest Linter Azure Bot smarter day by day! Thanks for your co-operation. |
|
No modification for AutorestCI/azure-sdk-for-node |
|
No modification for AutorestCI/azure-sdk-for-ruby |
|
No modification for AutorestCI/azure-sdk-for-python |
PR information
api-versionin the path should match theapi-versionin the spec).Quality of Swagger
Known validation issues
Commerce
Not implemented yet. When I try to access this I get an exception.
Fabric
Not implemented yet. When I try to access this I get an exception.
This is to fix a naming issue. Without this Autorest appends Property (I think) to the end of the name and cannot deserialize the results from the RP.
It is either true or false.
This only works on a multi-node environment and I don't have one.
This only works on a multi-node environment and I don't have one.
InfrastructureInsights
Not implemented yet. When I try to access this I get an exception.
If I do this I cannot perform an operation. Newtonsoft has an issue where it cannot serialize readonly variables.
If I do this I cannot perform an operation. Newtonsoft has an issue where it cannot serialize readonly variables.
If I do this I cannot perform an operation. Newtonsoft has an issue where it cannot serialize readonly variables.
If I do this I cannot perform an operation. Newtonsoft has an issue where it cannot serialize readonly variables.
I don't know why the RP did this but you can only change a single variable from "Open" to "Closed" and then pass it using a PUT.