Added new top level resource for verifying VNET for ASE#1574
Added new top level resource for verifying VNET for ASE#1574sergey-shandar merged 9 commits intoAzure:currentfrom
Conversation
|
@hforeste, |
| }, | ||
| "/subscriptions/{subscriptionId}/providers/Microsoft.Web/verifyHostingEnvironmentVnet": { | ||
| "post": { | ||
| "summary": "Verifies if this VNET is compatible with an App Service Environment by analyzing the Network Security Group rules", |
There was a problem hiding this comment.
'summary' and 'description' shouldn't be the same.
- 'summary' is a short summary of what operation does.
- 'description' is a verbose explanation.
There was a problem hiding this comment.
I shortened the summary in the next iteration.
Our tooling auto generates this swagger file hence why the summary and description are the same. Similar to the other APIs in the file.
| "operationId": "VerifyHostingEnvironmentVnet", | ||
| "consumes": [ | ||
| "application/json", | ||
| "text/json", |
There was a problem hiding this comment.
Does your service support all of these types? AFAIK, ARM recommends only "allpication/json".
| } | ||
| } | ||
| }, | ||
| "Object": { |
There was a problem hiding this comment.
Is there a reason to create an alias for an object type?
| "200": { | ||
| "description": "OK", | ||
| "schema": { | ||
| "$ref": "#/definitions/Object" |
There was a problem hiding this comment.
Is it possible to provide more information about what is the response structure? For example, does it have some common properties?
| } | ||
| }, | ||
| "VnetParameters": { | ||
| "description": "", |
There was a problem hiding this comment.
Could you provide a 'description' for the type? The description is used to generate API comments and documentation so it is useful for our customers.
sergey-shandar
left a comment
There was a problem hiding this comment.
Could you provide x-ms-example(s) for the new operation?
| "text/json", | ||
| "application/xml", | ||
| "text/xml" | ||
| ], |
There was a problem hiding this comment.
@hforeste still the same question, does your service support all of the content types (text/json, application/xml)? If supported content type are the same, could you place them to the top level of the swagger?
@ravbhatnagar are you ok with these content types?
There was a problem hiding this comment.
@sergey-shandar , our tooling automatically adds these content types. We're planning to fix this here in the near future.
There was a problem hiding this comment.
@hforeste Excellent! Do you have a ticket for this issue so we can track it?
There was a problem hiding this comment.
I'll have to check with @naveedaz, not sure where this work item might be tracked. Navy, do you have a work item tracked for this?
There was a problem hiding this comment.
@hforeste - ARM does not support content types other than application/json. So, please remove them. Even though these are generated by a tool, will it be a problem if you manually fix these?
There was a problem hiding this comment.
No, it should not be a problem. Thanks!
| "properties": { | ||
| "description": "VnetValidationFailureDetails resource specific properties", | ||
| "properties": { | ||
| "failed": { |
There was a problem hiding this comment.
- Could you add description to the property?
| "type": "boolean" | ||
| }, | ||
| "failedTests": { | ||
| "type": "array", |
There was a problem hiding this comment.
same here: description
| "testName": { | ||
| "type": "string" | ||
| }, | ||
| "details": { |
There was a problem hiding this comment.
same here, 'description'
|
Could you provide x-ms-example(s) for the new operation? |
|
@hforeste do you need help with examples? |
| "api-version": "2016-03-01", | ||
| "vNetParameters": { | ||
| "properties": { | ||
| "vnetResourceGroup": 'vNet123rg', |
There was a problem hiding this comment.
JSON errors. Please, use double quotes "".
| "parameters": { | ||
| "subscriptionId": "34adfa4f-cedf-4dc0-ba29-b6d1a69ab345", | ||
| "api-version": "2016-03-01", | ||
| "vNetParameters": { |
There was a problem hiding this comment.
the property should be called "parameters".
|
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: 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: 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-node |
|
No modification for AutorestCI/azure-sdk-for-ruby |
This checklist is used to make sure that common issues in a pull request are addressed. This will expedite the process of getting your pull request merged and avoid extra work on your part to fix issues discovered during the review process.
PR information
api-versionin the path should match theapi-versionin the spec).Quality of Swagger