Skip to content

Conversation

@ankushbindlish2
Copy link
Member

@ankushbindlish2 ankushbindlish2 commented Oct 1, 2018

  • Added TierFilesOlderThanDays in ServerEndpoint
  • Add TriggerRollover request
  • Remove Tags from ServerEndpoint

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

Changes with schema change and request
@azuresdkci
Copy link
Contributor

Can one of the admins verify this patch?

@AutorestCI
Copy link

AutorestCI commented Oct 1, 2018

Automation for azure-sdk-for-js

Nothing to generate for azure-sdk-for-js

@AutorestCI
Copy link

AutorestCI commented Oct 1, 2018

Automation for azure-sdk-for-python

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

@AutorestCI
Copy link

AutorestCI commented Oct 1, 2018

Automation for azure-sdk-for-ruby

Nothing to generate for azure-sdk-for-ruby

@AutorestCI
Copy link

AutorestCI commented Oct 1, 2018

Automation for azure-sdk-for-node

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

@AutorestCI
Copy link

AutorestCI commented Oct 1, 2018

Automation for azure-sdk-for-java

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

@AutorestCI
Copy link

AutorestCI commented Oct 1, 2018

Automation for azure-sdk-for-go

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

cd h:\csharpsdk\azure-rest-api-specs\specification
npx autorest --validation --azure-validator --message-format=json  h:\csharpsdk\azure-rest-api-specs\specification\storagesync\resource-manager\readme.md
oav validate-spec h:\csharpsdk\azure-rest-api-specs\specification\storagesync\resource-manager\Microsoft.StorageSync\stable\2018-07-01\storagesync.json
oav validate-example h:\csharpsdk\azure-rest-api-specs\specification\storagesync\resource-manager\Microsoft.StorageSync\stable\2018-07-01\storagesync.json -f h:\csharpsdk\azure-rest-api-specs\output\Expected_1.log
@sergey-shandar sergey-shandar added the WaitForARMFeedback <valid label in PR review process> add this label when ARM review is required label Oct 1, 2018
Copy link
Contributor

@sergey-shandar sergey-shandar left a comment

Choose a reason for hiding this comment

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

We still need ARM approval.

@ravbhatnagar
Copy link
Contributor

Looks good. signing off from ARM side,

@ravbhatnagar ravbhatnagar added ARMSignedOff <valid label in PR review process>add this label when ARM approve updates after review and removed ARMReviewInProgress WaitForARMFeedback <valid label in PR review process> add this label when ARM review is required labels Oct 3, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ARMSignedOff <valid label in PR review process>add this label when ARM approve updates after review

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants