Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merge Network-2018-02-01 to Master Networking Swagger Changes for Feb 2018 #2642

Merged
merged 16 commits into from
Mar 23, 2018

Conversation

dedhar
Copy link
Contributor

@dedhar dedhar commented Mar 13, 2018

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

  • The title of the PR is clear and informative.
  • There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For information on cleaning up the commits in your pull request, see this page.
  • Except for special cases involving multiple contributors, the PR is started from a fork of the main repository, not a branch.
  • If applicable, the PR references the bug/issue that it fixes.
  • Swagger files are correctly named (e.g. the api-version in the path should match the api-version in the spec).

Quality of Swagger

dedhar and others added 7 commits January 29, 2018 17:35
…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
@AutorestCI
Copy link

AutorestCI commented Mar 13, 2018

Automation for azure-libraries-for-java

A PR has been created for you:
Azure/azure-libraries-for-java#372

@AutorestCI
Copy link

AutorestCI commented Mar 13, 2018

Automation for azure-sdk-for-python

Nothing to generate for azure-sdk-for-python

@AutorestCI
Copy link

AutorestCI commented Mar 13, 2018

Automation for azure-sdk-for-go

A PR has been created for you:
Azure/azure-sdk-for-go#1402

Copy link

@murilogr murilogr left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do not merge until #2567 is merged into Network-2018-02-01

* 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.
Copy link

@murilogr murilogr left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

#2567 was merged. It contains all my changes. Looks good for my changes.

@murilogr
Copy link

It depends on the fix #2646

@salameer salameer assigned dsgouda and unassigned fearthecowboy Mar 15, 2018
@dsgouda
Copy link
Contributor

dsgouda commented Mar 15, 2018

@dedhar can you pull down the latest changes from master into Network-2018-02-01 and push the commit. That might probably be causing the build errors

"description": "Indicates if VM protection is enabled for all the subnets in the virtual network."
},
"ddosProtectionPlan": {
"$ref": "#/definitions/SubResource",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please fix this reference to ./network.json#/definitions/SubResource

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@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
@dsgouda
Copy link
Contributor

dsgouda commented Mar 16, 2018

@lmazuel Is the python failure due to XmsParameterLocation errors reported?

@dsgouda dsgouda added the DoNotMerge <valid label in PR review process> use to hold merge after approval label Mar 16, 2018
@dsgouda
Copy link
Contributor

dsgouda commented Mar 16, 2018

Do not merge before #2644

@dsgouda
Copy link
Contributor

dsgouda commented Mar 16, 2018

@vinayada1 Please pull the latest changes from this branch and work on your changes

@AutorestCI
Copy link

AutorestCI commented Mar 22, 2018

Automation for azure-sdk-for-node

A PR has been created for you:
Azure/azure-sdk-for-node#2534

@dsgouda
Copy link
Contributor

dsgouda commented Mar 22, 2018

@lmazuel Can you take a look at the CI failures here

@dsgouda
Copy link
Contributor

dsgouda commented Mar 23, 2018

All builds are a go!

Copy link
Contributor

@dsgouda dsgouda left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@dsgouda dsgouda merged commit 682e15a into master Mar 23, 2018
@lmazuel
Copy link
Member

lmazuel commented Mar 23, 2018

@AutorestCI rebuild azure-sdk-for-python

@lmazuel lmazuel deleted the Network-2018-02-01 branch July 25, 2018 23:03
mccleanp pushed a commit that referenced this pull request Mar 23, 2022
* 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>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
DoNotMerge <valid label in PR review process> use to hold merge after approval
Projects
None yet
Development

Successfully merging this pull request may close these issues.