Skip to content

Conversation

@blueww
Copy link
Member

@blueww blueww commented Jun 8, 2018

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.

Since the management policy format change, update the swagger example.
This won't impact the api in swagger.
Update the example are mainly for the rest doc generate.

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

@AutorestCI
Copy link

AutorestCI commented Jun 8, 2018

Automation for azure-sdk-for-go

Unable to detect any generation context from this PR.

@AutorestCI
Copy link

AutorestCI commented Jun 8, 2018

Automation for azure-sdk-for-python

Unable to detect any generation context from this PR.

@AutorestCI
Copy link

AutorestCI commented Jun 8, 2018

Automation for azure-sdk-for-ruby

Unable to detect any generation context from this PR.

@AutorestCI
Copy link

AutorestCI commented Jun 8, 2018

Automation for azure-libraries-for-java

Unable to detect any generation context from this PR.

@AutorestCI
Copy link

AutorestCI commented Jun 8, 2018

Automation for azure-sdk-for-node

Unable to detect any generation context from this PR.

Choose a reason for hiding this comment

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

hi Wei, small issue here. TierToCool days should be smaller than TierToArchive days, otherwise there would be a run time error. can you make change it from 1000 to 30?

Choose a reason for hiding this comment

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

same as the comment above

@hovsepm
Copy link
Contributor

hovsepm commented Jun 8, 2018

LGTM. Please let me know when the comments from @yzheng-msft will be addressed to merge the PR.

@azuresdkci azuresdkci assigned lmazuel and unassigned hovsepm Jun 8, 2018
@azuresdkci azuresdkci requested a review from lmazuel June 8, 2018 21:34
@blueww
Copy link
Member Author

blueww commented Jun 11, 2018

@hovsepm , @yzheng-msft , all comments has been resolved.
Would you please help to merge the PR?
Thanks!

@anuchandy anuchandy self-assigned this Jun 11, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

8 participants