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

Added NetworkConfigurationDiagnostic rest API + example #3599

Merged
merged 10 commits into from
Aug 15, 2018
Merged

Added NetworkConfigurationDiagnostic rest API + example #3599

merged 10 commits into from
Aug 15, 2018

Conversation

irrogozh
Copy link
Member

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

@azuresdkci
Copy link
Contributor

Can one of the admins verify this patch?

@azuresdkci azuresdkci requested a review from lmazuel August 7, 2018 18:15
@AutorestCI
Copy link

AutorestCI commented Aug 7, 2018

Automation for azure-sdk-for-ruby

Nothing to generate for azure-sdk-for-ruby

@AutorestCI
Copy link

AutorestCI commented Aug 7, 2018

Automation for azure-sdk-for-python

The initial PR has been merged into your service PR:
Azure/azure-sdk-for-python#3154

@AutorestCI
Copy link

AutorestCI commented Aug 7, 2018

Automation for azure-sdk-for-node

The initial PR has been merged into your service PR:
Azure/azure-sdk-for-node#3252

@AutorestCI
Copy link

AutorestCI commented Aug 7, 2018

Automation for azure-sdk-for-java

The initial PR has been merged into your service PR:
Azure/azure-sdk-for-java#2135

@AutorestCI
Copy link

AutorestCI commented Aug 7, 2018

Automation for azure-sdk-for-go

The initial PR has been merged into your service PR:
Azure/azure-sdk-for-go#2469

@lmazuel lmazuel closed this Aug 7, 2018
@lmazuel lmazuel reopened this Aug 7, 2018
@lmazuel
Copy link
Member

lmazuel commented Aug 7, 2018

Sorry, was the wrong tab, I never meant to close/open the PR :/

@lmazuel lmazuel added the WaitForARMFeedback <valid label in PR review process> add this label when ARM review is required label Aug 7, 2018
@lmazuel lmazuel requested a review from ravbhatnagar August 7, 2018 21:16
@MikhailTryakhov
Copy link
Contributor

@irrogozh please don't forget to merge to August branch

"queries"
],
"properties": {
"targetResourceId": {
Copy link
Contributor

Choose a reason for hiding this comment

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

what permissions are needed on the target resource to perform the network configuration diagnostic

Copy link
Member Author

Choose a reason for hiding this comment

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

Probably, read access on NSG.

"NetworkConfigurationDiagnosticResponse": {
"description": "Results of network configuration diagnostic on the target resource.",
"properties": {
"results": {
Copy link
Contributor

Choose a reason for hiding this comment

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

"value" array is the standard here.

Copy link
Member Author

Choose a reason for hiding this comment

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

It's not ObjectListPage. Value would be there only in this case...

Copy link
Member Author

Choose a reason for hiding this comment

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

'results' (as a name for array) was approved by our PMs...

"$ref": "./network.json#/parameters/SubscriptionIdParameter"
}
],
"responses": {
Copy link
Contributor

Choose a reason for hiding this comment

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

For all APIs., Model a "default" response to capture all the error states. The schema of this response should comply with ARM RPC error contract. Check Batch RP API spec for a sample.

Copy link
Member Author

Choose a reason for hiding this comment

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

Done, thank you!

@ravbhatnagar ravbhatnagar added ARMSignedOff <valid label in PR review process>add this label when ARM approve updates after review and removed WaitForARMFeedback <valid label in PR review process> add this label when ARM review is required labels Aug 15, 2018
@lmazuel lmazuel merged commit eb94056 into Azure:master Aug 15, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ARMSignedOff <valid label in PR review process>add this label when ARM approve updates after review
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants