Skip to content

Added new top level resource for verifying VNET for ASE#1574

Merged
sergey-shandar merged 9 commits intoAzure:currentfrom
hforeste:current
Aug 29, 2017
Merged

Added new top level resource for verifying VNET for ASE#1574
sergey-shandar merged 9 commits intoAzure:currentfrom
hforeste:current

Conversation

@hforeste
Copy link
Copy Markdown
Contributor

@hforeste hforeste commented Aug 23, 2017

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

@msftclas
Copy link
Copy Markdown

@hforeste,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot

},
"/subscriptions/{subscriptionId}/providers/Microsoft.Web/verifyHostingEnvironmentVnet": {
"post": {
"summary": "Verifies if this VNET is compatible with an App Service Environment by analyzing the Network Security Group rules",
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

'summary' and 'description' shouldn't be the same.

  • 'summary' is a short summary of what operation does.
  • 'description' is a verbose explanation.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

I shortened the summary in the next iteration.
Our tooling auto generates this swagger file hence why the summary and description are the same. Similar to the other APIs in the file.

"operationId": "VerifyHostingEnvironmentVnet",
"consumes": [
"application/json",
"text/json",
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Does your service support all of these types? AFAIK, ARM recommends only "allpication/json".

}
}
},
"Object": {
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Is there a reason to create an alias for an object type?

"200": {
"description": "OK",
"schema": {
"$ref": "#/definitions/Object"
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Is it possible to provide more information about what is the response structure? For example, does it have some common properties?

}
},
"VnetParameters": {
"description": "",
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Could you provide a 'description' for the type? The description is used to generate API comments and documentation so it is useful for our customers.

Copy link
Copy Markdown
Contributor

@sergey-shandar sergey-shandar left a comment

Choose a reason for hiding this comment

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

Could you provide x-ms-example(s) for the new operation?

"text/json",
"application/xml",
"text/xml"
],
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

@hforeste still the same question, does your service support all of the content types (text/json, application/xml)? If supported content type are the same, could you place them to the top level of the swagger?
@ravbhatnagar are you ok with these content types?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

@sergey-shandar , our tooling automatically adds these content types. We're planning to fix this here in the near future.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

@hforeste Excellent! Do you have a ticket for this issue so we can track it?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

I'll have to check with @naveedaz, not sure where this work item might be tracked. Navy, do you have a work item tracked for this?

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

@hforeste - ARM does not support content types other than application/json. So, please remove them. Even though these are generated by a tool, will it be a problem if you manually fix these?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

No, it should not be a problem. Thanks!

"properties": {
"description": "VnetValidationFailureDetails resource specific properties",
"properties": {
"failed": {
Copy link
Copy Markdown
Contributor

@sergey-shandar sergey-shandar Aug 24, 2017

Choose a reason for hiding this comment

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

  • Could you add description to the property?

"type": "boolean"
},
"failedTests": {
"type": "array",
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

same here: description

"testName": {
"type": "string"
},
"details": {
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

same here, 'description'

@sergey-shandar sergey-shandar added the WaitForARMFeedback <valid label in PR review process> add this label when ARM review is required label Aug 24, 2017
@hforeste
Copy link
Copy Markdown
Contributor Author

Could you provide x-ms-example(s) for the new operation?
->I think we can address this afterwards.

@sergey-shandar
Copy link
Copy Markdown
Contributor

@hforeste do you need help with examples?

@ravbhatnagar ravbhatnagar removed the WaitForARMFeedback <valid label in PR review process> add this label when ARM review is required label Aug 29, 2017
"api-version": "2016-03-01",
"vNetParameters": {
"properties": {
"vnetResourceGroup": 'vNet123rg',
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

JSON errors. Please, use double quotes "".

"parameters": {
"subscriptionId": "34adfa4f-cedf-4dc0-ba29-b6d1a69ab345",
"api-version": "2016-03-01",
"vNetParameters": {
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

the property should be called "parameters".

@azuresdkciprbot
Copy link
Copy Markdown

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: specification/web/resource-manager/readme.md
Before the PR: Warning(s): 1637 Error(s): 98
After the PR: Warning(s): 1641 Error(s): 98

AutoRest Linter Guidelines | AutoRest Linter Issues

Send feedback and make AutoRest Linter Azure Bot smarter day by day!

Thanks for your co-operation.

@azuresdkciprbot
Copy link
Copy Markdown

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: specification/web/resource-manager/readme.md
Before the PR: Warning(s): 1637 Error(s): 98
After the PR: Warning(s): 1637 Error(s): 98

AutoRest Linter Guidelines | AutoRest Linter Issues

Send feedback and make AutoRest Linter Azure Bot smarter day by day!

Thanks for your co-operation.

@sergey-shandar sergey-shandar merged commit 45c6e27 into Azure:current Aug 29, 2017
@AutorestCI
Copy link
Copy Markdown

No modification for AutorestCI/azure-sdk-for-node

@AutorestCI
Copy link
Copy Markdown

@AutorestCI
Copy link
Copy Markdown

@AutorestCI
Copy link
Copy Markdown

No modification for AutorestCI/azure-sdk-for-node

@AutorestCI
Copy link
Copy Markdown

No modification for AutorestCI/azure-sdk-for-ruby

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants