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

NetworkWatcher: Added new parameters to QueryConnectionMonitorResult and ConnectivityCheckRequest #2763

Merged
merged 8 commits into from
Mar 30, 2018

Conversation

irrogozh
Copy link
Member

@irrogozh irrogozh commented Mar 28, 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

@AutorestCI
Copy link

AutorestCI commented Mar 28, 2018

Automation for azure-libraries-for-java

The initial PR has been merged into your service PR:
AutorestCI/azure-libraries-for-java#22

@AutorestCI
Copy link

AutorestCI commented Mar 28, 2018

Automation for azure-sdk-for-python

Nothing to generate for azure-sdk-for-python

@AutorestCI
Copy link

AutorestCI commented Mar 28, 2018

Automation for azure-sdk-for-go

Nothing to generate for azure-sdk-for-go

@AutorestCI
Copy link

AutorestCI commented Mar 28, 2018

Automation for azure-sdk-for-node

A PR has been created for you based on this PR content.

Once this PR will be merged, content will be added to your service PR:
Azure/azure-sdk-for-node#2610

@salameer
Copy link
Member

Hi @irrogozh

@MikhailTryakhov we neel to Ack on CHanges for Networking that are against master, please follow up with him

=Thanks,

Samer

"ProtocolConfiguration": {
"description": "Configuration of the protocol.",
"properties": {
"hTTPConfiguration": {
Copy link
Contributor

Choose a reason for hiding this comment

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

is hTTP case expected?

Copy link
Member Author

Choose a reason for hiding this comment

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

Fixed

@MikhailTryakhov
Copy link
Contributor

@salameer As I can see there are no breaking changes, it need to be merged ASAP to make it GA :)
@irrogozh could you please make minor fixes to use similar case for option names and we can escalate merging

@MikhailTryakhov
Copy link
Contributor

LGTM
@anuchandy could you please review?

@@ -1697,7 +1697,7 @@
"UDP"
],
"x-ms-enum": {
"name": "Protocol",
"name": "IpFlowProtocol",
Copy link
Contributor

Choose a reason for hiding this comment

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

breaking change 1

@@ -2890,6 +2958,19 @@
},
"ConnectionMonitorQueryResult": {
"properties": {
"sourceStatus": {
Copy link
Contributor

Choose a reason for hiding this comment

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

breaking change 2 (constructor signature)

@olydis
Copy link
Contributor

olydis commented Mar 30, 2018

@MikhailTryakhov @salameer FYI, there are SDK breaking changes (see my comments) but indeed no API breakage.
@MikhailTryakhov do you require review from @anuchandy?

Copy link
Contributor

@olydis olydis left a comment

Choose a reason for hiding this comment

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

LGTM

@MikhailTryakhov
Copy link
Contributor

MikhailTryakhov commented Mar 30, 2018

@olydis I meant no API breakage. I needed Anu because have no rights to approve :) now it can be merged

@olydis
Copy link
Contributor

olydis commented Mar 30, 2018

@MikhailTryakhov well, all reviewers (like me) have the power to merge, so whoever is assigned to a PR will be the POC 🙂

@olydis olydis merged commit 576abc9 into Azure:master Mar 30, 2018
iscai-msft pushed a commit that referenced this pull request Jul 9, 2021
tianxchen-ms referenced this pull request in test-repo-billy/azure-rest-api-specs Apr 26, 2022
dw511214992 referenced this pull request in dw511214992/azure-rest-api-specs Jul 8, 2022
dw511214992 referenced this pull request in test-repo-billy/azure-rest-api-specs Oct 27, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants