Merge Networking v2017 09 01 into current#1661
Conversation
* Copying networking files under 2017-08-01 to 2017-09-01 * Updated api-version to 2017-09-01 for examples
…1616) * Add new paths and definitions for application security groups (ASGs) * Add IPConfiguration-ApplicationSecurityGroup relationship * Add SecurityRule-ApplicationSecurityGroup relationship * Revert "Add IPConfiguration-ApplicationSecurityGroup relationship" This reverts commit ebe9e74. * Revert "Add SecurityRule-ApplicationSecurityGroup relationship" This reverts commit ab48476. * Revert "Add new paths and definitions for application security groups (ASGs)" This reverts commit 20be954. * Create new folder for 09-01 * Add new paths and definitions for application security groups (ASGs) * Add IPConfiguration-ApplicationSecurityGroup relationship * Add SecurityRule-ApplicationSecurityGroup relationship * Add new tag in readme.md * Change version in json files * Fix readme.md * Change name of the relationship to security rules * Fix security rule relationship to be many-to-many * Change returning type for collections (to references) * Remove useless parameter * Add to the end of the paths * Remove expand from get * Add collections API * Add examples * Fix operation name * Mark resource ID as a read-only property * Fix SDK generation issue * Fix model validation errors * Add readOnly flags to application security group properties * Add missing provisioning state in the docs * Add missing field to Resource * Reposition 'location' in the example * Fix missing 'id' field in collections * Update ResourceGUID message * Remove text/json * Remove ref from paths * Remove unnecessary file * Remove paths * Remove definitions
|
@ajinkyapotdarvjti, |
|
No modification for AutorestCI/azure-sdk-for-node |
|
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. |
* Add List API * Remove whitespace
|
No modification for AutorestCI/azure-sdk-for-node |
|
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. |
veronicagg
left a comment
There was a problem hiding this comment.
This PR is merging the branch created specifically for Network team, which contains commits that were merged to that branch and reviewed by SDK team and ARM team already.
|
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