Skip to content

Adding license header constant in SiteRecovery spec#1227

Merged
jhendrixMSFT merged 2 commits intoAzure:masterfrom
AsrOneSdk:masterRel1
May 15, 2017
Merged

Adding license header constant in SiteRecovery spec#1227
jhendrixMSFT merged 2 commits intoAzure:masterfrom
AsrOneSdk:masterRel1

Conversation

@avneeshrai
Copy link

@avneeshrai avneeshrai commented May 14, 2017

Change is to address the comment on PR: Azure/azure-sdk-for-net#3194

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


This change is Reviewable

@msftclas
Copy link

@avneeshrai,
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

"type": "string"
}
},
"properties": {},
Copy link
Member

Choose a reason for hiding this comment

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

Is there a reason why this was left empty?

Copy link
Author

@avneeshrai avneeshrai May 15, 2017

Choose a reason for hiding this comment

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

@jhendrixMSFT model VmmToAzureUpdateNetworkMappingInput in service as of now doesn't have any value specific to this instance as of now and has been introduced to make it future extensible and consistent with other sibling models (we expect it to have some fields in near future).
Swagger changes just represent what the service expects

"type": "object",
"properties": {
"InstanceType": {
"instanceType": {
Copy link
Member

Choose a reason for hiding this comment

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

Did the service change or is this update to the swagger making it match the service?

Copy link
Author

Choose a reason for hiding this comment

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

This update to swagger matches it to service.

@avneeshrai
Copy link
Author

@jhendrixMSFT responded to your comments. Let me know if any other action item is on me or merge if it can be merged :)

@jhendrixMSFT jhendrixMSFT merged commit f66ea25 into Azure:master May 15, 2017
@AutorestCI
Copy link

No modification for Ruby

@AutorestCI
Copy link

No modification for Python

@AutorestCI
Copy link

No modification for NodeJS

@avneeshrai avneeshrai deleted the masterRel1 branch August 12, 2017 10:03
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.

5 participants