Add swagger changes for zone redundancy property to databases, elastic pools and editions

[emgu-ms]

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

• I have read the contribution guidelines.
• My spec meets the review criteria:
  • The spec conforms to the Swagger 2.0 specification.
  • The spec follows the guidelines described in the Swagger checklist document.
  • Validation tools were run on swagger spec(s) and have all been fixed in this PR.

[msftclas]

All CLA requirements met.

[fearthecowboy]

@emgu-ms -- if you are an MS employee, make sure your account is tied to your domain account so that it's cleared by the CLA check.

if not, you can sign the cla (follow the instructions in the post...)

[jaredmoo]

Looks good. Just want to make sure this is on in at least 1 production region and has .NET SDK test written and working on your machine before this gets merged.

[fearthecowboy]

@emgu-ms -- ping this thread when you've satisfied @jaredmoo 's conditions.

[jaredmoo]

I think you need a comma at the end here

[jaredmoo]

Looks good, please confirm that .NET SDK is working and then let's merge.

[jaredmoo]

Oh ho, linter errors. It looks like boolean format doesn't exist. I think you'll have to just remove those format's and treat it as plain string.

[fearthecowboy]

Is the value a boolean?

swagger uses "type":"boolean" -- not format

.

[jaredmoo]

The value is either "true" or "false" as a string, not true or false as a boolean literal. This is an unfortunate limitation in our API stack that implements api-version 2014-04-01. The later api-versions (which are being deployed soon) will have this as a real boolean.

[fearthecowboy]

Ah. ok.

,<

Ouch.

[azuresdkciprbot]

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.

[azuresdkciprbot]

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.

[fearthecowboy]

Hey @emgu-ms,

are we getting close to being ready to merge this?

[emgu-ms]

Yup! We're good! Thanks all :)

[AutorestCI]

Azure/azure-sdk-for-python#1546

[AutorestCI]

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

[AutorestCI]

Azure/azure-sdk-for-ruby#1063

[AutorestCI]

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

[AutorestCI]

Azure/azure-sdk-for-python#1555

[AutorestCI]

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