-
Notifications
You must be signed in to change notification settings - Fork 5.2k
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
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Automation for azure-libraries-for-javaUnable to detect any generation context from this PR. |
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
Automation for azure-sdk-for-nodeUnable to detect any generation context from this PR. |
Automation for azure-sdk-for-pythonUnable to detect any generation context from this PR. |
Automation for azure-sdk-for-rubyUnable to detect any generation context from this PR. |
Automation for azure-sdk-for-goUnable to detect any generation context from this PR. |
sergey-shandar
approved these changes
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
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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:
PR information
api-version
in the path should match theapi-version
in the spec).Quality of Swagger