Skip to content

Swagger spec for Server DNS Aliasing#1858

Merged
alvadb merged 3 commits intoAzure:currentfrom
maboja-msft:current
Oct 18, 2017
Merged

Swagger spec for Server DNS Aliasing#1858
alvadb merged 3 commits intoAzure:currentfrom
maboja-msft:current

Conversation

@maboja-msft
Copy link
Copy Markdown
Contributor

@maboja-msft maboja-msft commented Oct 13, 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

@maboja-msft
Copy link
Copy Markdown
Contributor Author

@jaredmoo @nathannfan Please comment

@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/sql/resource-manager/readme.md
Before the PR: Warning(s): 0 Error(s): 0
After the PR: Warning(s): 0 Error(s): 0

AutoRest Linter Guidelines | AutoRest Linter Issues | Send feedback

Thanks for your co-operation.

Copy link
Copy Markdown
Contributor

@jaredmoo jaredmoo left a comment

Choose a reason for hiding this comment

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

Overall looks great, minor comments. Please confirm that the service is in at least 1 production region and you have .net sdk tests passing that use code generated from this swagger.

- Microsoft.Sql/2015-05-01-preview/syncMembers.json
- Microsoft.Sql/2015-05-01-preview/virtualNetworkRules.json
- Microsoft.Sql/2017-03-01-preview/cancelOperations.json
- Microsoft.Sql/2017-03-01-preview/serverDnsAliases.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.

please also add to schema-2017-03-preview section

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.

This tag does not exist, so I have created it

"serverName": "dns-alias-new-server",
"dnsAliasName": "dns-alias-name-1",
"api-version": "2017-03-01-preview",
"parameters": {
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.

nit: tabs/spaces here and in other example files

},
{
"$ref": "#/parameters/ApiVersionParameter"
}
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 no body parameter?

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, those requests don't have body

}
},
"ServerDnsAliasAcquisition": {
"description": "A server dns alias acquisition request.",
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.

DNS or dns? Please pick one and stuck with it :)

@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/sql/resource-manager/readme.md
Before the PR: Warning(s): 0 Error(s): 0
After the PR: Warning(s): 0 Error(s): 0

AutoRest Linter Guidelines | AutoRest Linter Issues | Send feedback

Thanks for your co-operation.

@salameer
Copy link
Copy Markdown
Member

Captain @alvadb

Ping on this one :)

@maboja-msft
Copy link
Copy Markdown
Contributor Author

In response to Jared's comment: yes, service is in at least one production region (in fact it is deployed and working in all regions) and .net client tests are passing.

Copy link
Copy Markdown

@alvadb alvadb left a comment

Choose a reason for hiding this comment

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

Please fix example errors in next commit.

@alvadb alvadb merged commit 5ff1e77 into Azure:current Oct 18, 2017
@AutorestCI
Copy link
Copy Markdown

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

@AutorestCI
Copy link
Copy Markdown

@AutorestCI
Copy link
Copy Markdown

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