Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Storage] Change the Management policy example per feature PM request #3217

Merged
merged 1 commit into from
Jun 12, 2018

Conversation

blueww
Copy link
Member

@blueww blueww commented Jun 12, 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.

We just have a PR #3197 changed the example. Per the PM request, just need another change.
The change is simple, just change 3 number in the example.

Following is the request from feature PM:

We can’t delete any blob with snapshots. So snapshot should be deleted before blob deletion, which means the snapshot delete days number should be smaller than the blob delete days (so instead of 5000, make it something like 30). I don’ think we should block the publishing of the current set. But I would like to update this as soon as possible. Can you make the update?

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 12, 2018

Automation for azure-libraries-for-java

Unable to detect any generation context from this PR.

@blueww blueww changed the title [Storage] cange the Management policy example per feature PM request [Storage] Change the Management policy example per feature PM request Jun 12, 2018
@AutorestCI
Copy link

AutorestCI commented Jun 12, 2018

Automation for azure-sdk-for-node

Unable to detect any generation context from this PR.

@AutorestCI
Copy link

AutorestCI commented Jun 12, 2018

Automation for azure-sdk-for-python

Unable to detect any generation context from this PR.

@AutorestCI
Copy link

AutorestCI commented Jun 12, 2018

Automation for azure-sdk-for-ruby

Unable to detect any generation context from this PR.

@AutorestCI
Copy link

AutorestCI commented Jun 12, 2018

Automation for azure-sdk-for-go

Unable to detect any generation context from this PR.

@sergey-shandar sergey-shandar merged commit 788f8f8 into Azure:master Jun 12, 2018
leniatgh pushed a commit that referenced this pull request Jul 2, 2020
…rsion stable/2020-06-01 (#9982)

* Adds base for updating Microsoft.CostManagement from version stable/2019-11-01 to version 2020-06-01

* Updates readme

* Updates API version in new specs and examples

* Latest

* Latest

* Latest

* Latest

* Latest

* Latest

* Latest

* Latest

* Latest

* Latest

* Placed "code" and "message" inside an "error" object so it conforms to the standard error structure (line #3217)
00Kai0 pushed a commit to 00Kai0/azure-rest-api-specs that referenced this pull request Oct 12, 2020
…rsion stable/2020-06-01 (Azure#9982)

* Adds base for updating Microsoft.CostManagement from version stable/2019-11-01 to version 2020-06-01

* Updates readme

* Updates API version in new specs and examples

* Latest

* Latest

* Latest

* Latest

* Latest

* Latest

* Latest

* Latest

* Latest

* Latest

* Placed "code" and "message" inside an "error" object so it conforms to the standard error structure (line Azure#3217)
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.

3 participants