Merge Network-2018-02-01 to Master Networking Swagger Changes for Feb 2018#2642
Merge Network-2018-02-01 to Master Networking Swagger Changes for Feb 2018#2642
Conversation
…of Express Route Circuit Peering in 2018-02-01 API (#2358) * copy all files from 2018-01-01 to 2018-02-01 * update api version to 2018 in all files * add express route circuit connection as child of express route bgp peering * update readme.md * add examples * fix travis build error * fix travis build error * fix indentation errors * update reference to circuit connections in peering * fix indentation
* copy all files from 2018-01-01 to 2018-02-01 * update api version to 2018 in all files * add express route circuit connection as child of express route bgp peering * update readme.md * add examples * fix travis build error * fix travis build error * fix indentation errors * update reference to circuit connections in peering * fix indentation * fix indentation * fix indentation' * get latest file * Fix indentation * fix key * fix indentation and example * fix indentation * fix indentation * make circuit con singular
…way P2S clients. (#2521) * 1443089: Network feature: Setting custom ipsec policy for Virtual Network Gateway P2S clients. * 1443089:Fix network ReadMe file. * 1443089:Fix network ReadMe file. * Temporary bug fix
* Add support for Express Route Provider APIs A new top level NRP resource ExpressRouteCrossConnection is being introduced with this change. This resource shadows the customer ExpressRouteCircuit resouce in the customer subscription and enables the provider to perform CRUD operations on some of the sub-resources, such as peerings on the ExpressRoute Circuit
#2572) * remove wrong enum values from circuit connection status and fix enum name
* Update CrossConnection Route Table Summary record
Automation for azure-libraries-for-javaA PR has been created for you: |
Automation for azure-sdk-for-pythonNothing to generate for azure-sdk-for-python |
Automation for azure-sdk-for-goA PR has been created for you: |
* Initial version * Add eol * Add extra property in example * Add default values for fields * Rename operation IDs * Make 'id' read-only for all network resources * Revert "Make 'id' read-only for all network resources" This reverts commit 9a32d84.
|
It depends on the fix #2646 |
|
@dedhar can you pull down the latest changes from master into |
| "description": "Indicates if VM protection is enabled for all the subnets in the virtual network." | ||
| }, | ||
| "ddosProtectionPlan": { | ||
| "$ref": "#/definitions/SubResource", |
There was a problem hiding this comment.
Please fix this reference to ./network.json#/definitions/SubResource
There was a problem hiding this comment.
@murilogr : Can you take a look and fix this in your original PR?
* Initial version * Add eol * Add extra property in example * Add default values for fields * Rename operation IDs * Make 'id' read-only for all network resources * Revert "Make 'id' read-only for all network resources" This reverts commit 9a32d84. * Fix reference
…into Network-2018-02-01
|
@lmazuel Is the python failure due to |
|
Do not merge before #2644 |
…into Network-2018-02-01
|
@vinayada1 Please pull the latest changes from this branch and work on your changes |
…eering as references (#2696)
Automation for azure-sdk-for-nodeA PR has been created for you: |
|
All builds are a go! |
|
@AutorestCI rebuild azure-sdk-for-python |
* Remove async responses from Swagger * Update openapi-subtype * Remove x-ms-long-running-operation * Fix spelling * Prettier * Spelling * More spelling fixes Co-authored-by: Ben Viglietta <benvi@ntdev.microsoft.com>
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