change the name of a new enumeration in storage's latest api-version #20157
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
ArcturusZhang
requested review from
msyyc,
BigCat20196 and
JasonYang-MSFT
as code owners
|
Hi, @ArcturusZhang Thanks for your PR. I am workflow bot for review process. Here are some small tips. Any feedback about review process or workflow bot, pls contact swagger and tools team. [email protected] |
Swagger Validation Report
|
| compared swaggers (via Oad v0.9.6)] | new version | base version |
|---|---|---|
| blob.json | 2022-05-01(fe54ce1) | 2022-05-01(main) |
️️✔️Breaking Change(Cross-Version) succeeded [Detail] [Expand]
There are no breaking changes.
️️✔️CredScan succeeded [Detail] [Expand]
There is no credential detected.
️⚠️LintDiff: 0 Warnings warning [Detail]
| compared tags (via openapi-validator v1.13.0) | new version | base version |
|---|---|---|
| package-2022-05 | package-2022-05(fe54ce1) | package-2022-05(main) |
The following errors/warnings exist before current PR submission:
Only 30 items are listed, please refer to log for more details.
| Rule | Message |
|---|---|
|
Resource type naming must follow camel case. Path: '/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Storage/storageAccounts/{accountName}/blobServices/{BlobServicesName}' Location: Microsoft.Storage/stable/2022-05-01/blob.json#L58 |
|
The response is defined but without a default error response implementation.Consider adding it.' Location: Microsoft.Storage/stable/2022-05-01/blob.json#L45 |
|
The response is defined but without a default error response implementation.Consider adding it.' Location: Microsoft.Storage/stable/2022-05-01/blob.json#L102 |
|
The response is defined but without a default error response implementation.Consider adding it.' Location: Microsoft.Storage/stable/2022-05-01/blob.json#L139 |
|
The response is defined but without a default error response implementation.Consider adding it.' Location: Microsoft.Storage/stable/2022-05-01/blob.json#L204 |
|
The response is defined but without a default error response implementation.Consider adding it.' Location: Microsoft.Storage/stable/2022-05-01/blob.json#L261 |
|
The response is defined but without a default error response implementation.Consider adding it.' Location: Microsoft.Storage/stable/2022-05-01/blob.json#L313 |
|
The response is defined but without a default error response implementation.Consider adding it.' Location: Microsoft.Storage/stable/2022-05-01/blob.json#L354 |
|
The response is defined but without a default error response implementation.Consider adding it.' Location: Microsoft.Storage/stable/2022-05-01/blob.json#L391 |
|
The response is defined but without a default error response implementation.Consider adding it.' Location: Microsoft.Storage/stable/2022-05-01/blob.json#L442 |
|
The response is defined but without a default error response implementation.Consider adding it.' Location: Microsoft.Storage/stable/2022-05-01/blob.json#L490 |
|
The response is defined but without a default error response implementation.Consider adding it.' Location: Microsoft.Storage/stable/2022-05-01/blob.json#L550 |
|
The response is defined but without a default error response implementation.Consider adding it.' Location: Microsoft.Storage/stable/2022-05-01/blob.json#L603 |
|
The response is defined but without a default error response implementation.Consider adding it.' Location: Microsoft.Storage/stable/2022-05-01/blob.json#L656 |
|
The response is defined but without a default error response implementation.Consider adding it.' Location: Microsoft.Storage/stable/2022-05-01/blob.json#L708 |
|
The response is defined but without a default error response implementation.Consider adding it.' Location: Microsoft.Storage/stable/2022-05-01/blob.json#L768 |
|
The response is defined but without a default error response implementation.Consider adding it.' Location: Microsoft.Storage/stable/2022-05-01/blob.json#L824 |
|
The delete operation is defined without a 200 or 204 error response implementation,please add it.' Location: Microsoft.Storage/stable/2022-05-01/blob.json#L656 |
|
The integer type does not have a format, please add it. Location: Microsoft.Storage/stable/2022-05-01/blob.json#L903 |
|
The integer type does not have a format, please add it. Location: Microsoft.Storage/stable/2022-05-01/blob.json#L1038 |
|
The integer type does not have a format, please add it. Location: Microsoft.Storage/stable/2022-05-01/blob.json#L1151 |
|
The integer type does not have a format, please add it. Location: Microsoft.Storage/stable/2022-05-01/blob.json#L1408 |
|
The integer type does not have a format, please add it. Location: Microsoft.Storage/stable/2022-05-01/blob.json#L1488 |
|
The integer type does not have a format, please add it. Location: Microsoft.Storage/stable/2022-05-01/blob.json#L1492 |
|
The schema 'ContainerProperties' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.Storage/stable/2022-05-01/blob.json#L885 |
|
The schema 'BlobContainer' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.Storage/stable/2022-05-01/blob.json#L1020 |
|
The schema 'ImmutabilityPolicyProperty' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.Storage/stable/2022-05-01/blob.json#L1036 |
|
The schema 'ImmutabilityPolicyProperties' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.Storage/stable/2022-05-01/blob.json#L1066 |
|
The schema 'ImmutabilityPolicy' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.Storage/stable/2022-05-01/blob.json#L1089 |
|
The schema 'ImmutableStorageWithVersioning' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.Storage/stable/2022-05-01/blob.json#L1107 |
️️✔️Avocado succeeded [Detail] [Expand]
Validation passes for Avocado.
️️✔️ApiReadinessCheck succeeded [Detail] [Expand]
️️✔️ModelValidation succeeded [Detail] [Expand]
Validation passes for ModelValidation.
️️✔️SemanticValidation succeeded [Detail] [Expand]
Validation passes for SemanticValidation.
️️✔️PoliCheck succeeded [Detail] [Expand]
Validation passed for PoliCheck.
️⚠️SDK Track2 Validation: 1 Warnings warning [Detail]
- The following tags are being changed in this PR
- "https://github.com/Azure/azure-rest-api-specs/blob/fe54ce16d37ef4da02eecdc027ac33ac988d050e/specification/storage/resource-manager/readme.md#tag-package-2022-05">storage/resource-manager/readme.md#package-2022-05
| Rule | Message |
|---|---|
| "readme":"storage/resource-manager/readme.md", "tag":"package-2022-05", "details":"Security scheme azure_auth is unknown and will not be processed. Only supported types are AADToken, AzureKey, Anonymous" |
️️✔️PrettierCheck succeeded [Detail] [Expand]
Validation passes for PrettierCheck.
️️✔️SpellCheck succeeded [Detail] [Expand]
Validation passes for SpellCheck.
️️✔️Lint(RPaaS) succeeded [Detail] [Expand]
Validation passes for Lint(RPaaS).
️️✔️CadlValidation succeeded [Detail] [Expand]
Validation passes for CadlValidation.
Swagger Generation Artifacts
|
Generated ApiView
|
ghost
added
the
blueww
approved these changes
Aug 9, 2022
This was referenced Aug 9, 2022
This was referenced Aug 9, 2022
msyyc
requested changes
Aug 9, 2022
msyyc
approved these changes
Aug 10, 2022
This was referenced Aug 10, 2022
This was referenced Aug 10, 2022
Closed
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.
MSFT employees can try out our new experience at OpenAPI Hub - one location for using our validation tools and finding your workflow.
Azure 1st Party Service can try out the Shift Left experience to initiate API design review from ADO code repo. If you are interested, may request engineering support by filling in with the form https://aka.ms/ShiftLeftSupportForm.
Changelog
Add a changelog entry for this PR by answering the following questions:
Contribution checklist:
If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist
Otherwise your PR may be subject to ARM review requirements. Complete the following:
Check this box if any of the following appy to the PR so that the label "ARMReview" and "WaitForARMFeedback" will be added by bot to kick off ARM API Review. Missing to check this box in the following scenario may result in delays to the ARM manifest review and deployment.
-[ ] To review changes efficiently, ensure you are using OpenAPIHub to initialize the PR for adding a new version. More details, refer to the wiki.
Ensure you've reviewed following guidelines including ARM resource provider contract and REST guidelines. Estimated time (4 hours). This is required before you can request review from ARM API Review board.
If you are blocked on ARM review and want to get the PR merged with urgency, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.
Breaking Change Review Checklist
If any of the following scenarios apply to the PR, request approval from the Breaking Change Review Board as defined in the Breaking Change Policy.
Action: to initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Addition details on the process and office hours are on the Breaking change Wiki.
Please follow the link to find more details on PR review process.