Added service endpoints APIs#1533
Conversation
|
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. |
|
@ravbhatnagar New swagger file. |
sergey-shandar
left a comment
There was a problem hiding this comment.
Waiting for ARM feedback.
|
Ping....Why does this need ARM review again? this has already been reviewed by them. we are renaming this property. so we had to remove and replace it back. @sergey-shandar @ravbhatnagar |
|
@DeepakRajendranMsft I see a new file Microsoft.Network/2017-06-01/endpointService.json. Could you send a link to the ARM review for this file? |
|
this is the PR where we dropped it #1486. we wouldnt have put in there if we didnt get ARM approval :) |
|
@ravbhatnagar could you confirm ARM review? I still can't see a ARM review confirmation for the new file. |
|
@sergey-shandar - looks good. |
|
@sergey-shandar can this be merged please |
| "$ref": "./routeTable.json#/definitions/RouteTable", | ||
| "description": "The reference of the RouteTable resource." | ||
| }, | ||
| "serviceEndpoints": { |
There was a problem hiding this comment.
@EvgenyAgafonchikov @ravbhatnagar this property is used in response which may introduce API breaking changes, or SDK breaking changes if it's used in GET-PUT scenario. If we don't plan to use it in such scenario, we should mark it as "read only".
There was a problem hiding this comment.
@amarzavery @salameer this is well documented and we are okay with the breaking change.
it is read-write property.
There was a problem hiding this comment.
@ravbhatnagar can you sign off on this new additional property.
|
@DeepakRajendranMsft - Is this again the same case where it has already been added on the service side for this api-version and swagger update is happening now? |
|
@ravbhatnagar yes. because we did a rename of the property. |
|
@sergey-shandar - ARM signs off. |
|
No modification for AutorestCI/azure-sdk-for-node |
This reverts commit f69dc64.
* Revert "[Event Grid] Event grid C# code generation section. (#1561)" This reverts commit 461a494. * Revert "Bug Fix when linter runs on json file without being included in tag (#1560)" This reverts commit d6bc117. * Revert "Remove databaseName uri param from Databases_Import op. (#1558)" This reverts commit 69d0a5d. * Revert "Added 200 response for event grid event subscription delete operation. (#1555)" This reverts commit ad55af7. * Revert "Add some content to Swagger from docs.msft.com (#1549)" This reverts commit b955458. * Revert "[Azure Analysis Services] Add gateway info to version 0714 and version 0801 (#1526)" This reverts commit bf407b7. * Revert "Copied service endpoints specs to 2017-08-01 (#1548)" This reverts commit 64c905a. * Revert "Removed `x-ms-pageable` from Network Interface's `GetEffectiveRouteTable` and `ListEffectiveNetworkSecurityGroups` methods (#1547)" This reverts commit da940d5. * Revert "Added service endpoints APIs (#1533)" This reverts commit f69dc64. * Revert "Added support for ECC to Key Vault (#1538)" This reverts commit 4a9084f.
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