Added the replica count API change to Shared Image Gallery swagger file.

[vanbasten2323]

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.

[AutorestCI]

Automation for azure-sdk-for-ruby

Nothing to generate for azure-sdk-for-ruby

[AutorestCI]

Automation for azure-sdk-for-python

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

[AutorestCI]

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#3481

[AutorestCI]

Automation for azure-sdk-for-java

Nothing to generate for azure-sdk-for-java

[AutorestCI]

Automation for azure-sdk-for-go

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

[huangpf]

If the name of the region is called name, why the replica count still has the region as the property's prefix? Why not just replicaCount?

[vanbasten2323]

Yes. Initially, we call it "replicaCount", the same as you suggested. Then we got some feedback from Kay Singh that it might be clearer to use "regionalReplicaCount". So we use this.

[huangpf]

OK

[huangpf]

source blob in the source region, or in the target region? Or target blob? Please consider revising the statement to make it clearer.

[vanbasten2323]

So it is the copies of the source blob in the target regions. Will this be better "This is the number of copies of the source blobs in this target region."?

[huangpf]

OK

[yugangw-msft]

@vanbasten2323 what exactly is the "number of copies of the source blobs mean"?

[yugangw-msft]

@singhkays, the original mail communicates the new name would be scaleTier, so i am bit confused now. Can you guys offer some explanation, so i can communicate better to CLI users.

[yugangw-msft]

Also, what is the service end default value for this?

[singhkays]

Clarified in offline call

[huangpf]

LGTM, with some minor comments.

[azuresdkci]

Can one of the admins verify this patch?