Conversation
|
Hi, @shahzzzam 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. vsswagger@microsoft.com |
|
[Call for Action] To better understand Azure service dev/test scenario, and support Azure service developer better on Swagger and REST API related tests in early phase, please help to fill in with this survey https://aka.ms/SurveyForEarlyPhase. It will take 5 to 10 minutes. If you already complete survey, please neglect this comment. Thanks. |
Swagger Validation Report
|
| Rule | Message |
|---|---|
| The operation 'ContainerRegistry_DeleteManifest' returns 202 status code, which indicates a long running operation, please enable 'x-ms-long-running-operation. Location: Azure.ContainerRegistry/stable/2021-07-01/containerregistry.json#L172 |
|
| The operation 'ContainerRegistryBlob_DeleteBlob' returns 202 status code, which indicates a long running operation, please enable 'x-ms-long-running-operation. Location: Azure.ContainerRegistry/stable/2021-07-01/containerregistry.json#L318 |
|
| The operation 'ContainerRegistryBlob_UploadChunk' returns 202 status code, which indicates a long running operation, please enable 'x-ms-long-running-operation. Location: Azure.ContainerRegistry/stable/2021-07-01/containerregistry.json#L453 |
|
| The operation 'ContainerRegistry_DeleteRepository' returns 202 status code, which indicates a long running operation, please enable 'x-ms-long-running-operation. Location: Azure.ContainerRegistry/stable/2021-07-01/containerregistry.json#L671 |
|
| The operation 'ContainerRegistry_DeleteTag' returns 202 status code, which indicates a long running operation, please enable 'x-ms-long-running-operation. Location: Azure.ContainerRegistry/stable/2021-07-01/containerregistry.json#L888 |
|
| The operation 'ContainerRegistryBlob_StartUpload' returns 202 status code, which indicates a long running operation, please enable 'x-ms-long-running-operation. Location: Azure.ContainerRegistry/stable/2021-07-01/containerregistry.json#L1243 |
️️✔️Avocado succeeded [Detail] [Expand]
Validation passes for Avocado.
️❌ModelValidation: 4 Errors, 0 Warnings failed [Detail]
| Rule | Message |
|---|---|
RESPONSE_BODY_NOT_IN_EXAMPLE |
Response statusCode "202" for operation "ContainerRegistry_DeleteRepository" has no response body provided in the example, however the response does have a "schema" defined in the swagger spec. |
INVALID_TYPE |
Expected type string but found type object Url: Azure.ContainerRegistry/stable/2021-07-01/containerregistry.json#L3172 |
INVALID_TYPE |
Expected type string but found type object Url: Azure.ContainerRegistry/stable/2021-07-01/containerregistry.json#L3172 |
INVALID_TYPE |
Expected type string but found type object Url: Azure.ContainerRegistry/stable/2021-07-01/containerregistry.json#L3172 |
️️✔️SemanticValidation succeeded [Detail] [Expand]
Validation passes for SemanticValidation.
️⚠️Cross-Version Breaking Changes: 12 Warnings warning [Detail]
- Compared Swaggers (Based on Oad v0.9.0)
- current:stable/2021-07-01/containerregistry.json compared with base:preview/2019-08-15-preview/containerregistry.json
️️✔️CredScan succeeded [Detail] [Expand]
There is no credential detected.
️️✔️[Staging] SDK Track2 Validation succeeded [Detail] [Expand]
Validation passes for SDKTrack2Validation
- The following tags are being changed in this PR
️️✔️[Staging] PrettierCheck succeeded [Detail] [Expand]
Validation passes for PrettierCheck.
️️✔️[Staging] SpellCheck succeeded [Detail] [Expand]
Validation passes for SpellCheck.
️️✔️[Staging] Lint(RPaaS) succeeded [Detail] [Expand]
Validation passes for Lint(RPaaS).
|
Swagger pipeline restarted successfully, please wait for status update in this comment. |
|
Hi, @shahzzzam your PR are labelled with WaitForARMFeedback. A notification email will be sent out shortly afterwards to notify ARM review board(armapireview@microsoft.com). |
|
Hi, @shahzzzam. Your PR has no update for 14 days and it is marked as stale PR. If no further update for over 14 days, the bot will close the PR. If you want to refresh the PR, please remove |
|
Hi @shahzzzam, Your PR has some issues. Please fix the CI sequentially by following the order of
|
5e043df to
1ab33fd
Compare
...ontainerregistry/data-plane/Azure.ContainerRegistry/stable/2021-07-01/containerregistry.json
Show resolved
Hide resolved
...ontainerregistry/data-plane/Azure.ContainerRegistry/stable/2021-07-01/containerregistry.json
Show resolved
Hide resolved
...ontainerregistry/data-plane/Azure.ContainerRegistry/stable/2021-07-01/containerregistry.json
Outdated
Show resolved
Hide resolved
...ontainerregistry/data-plane/Azure.ContainerRegistry/stable/2021-07-01/containerregistry.json
Outdated
Show resolved
Hide resolved
83652e4 to
c74b69e
Compare
|
Can someone please help with the error? I don't understand what file it refers to. |
|
Hi, @shahzzzam. Your PR has no update for 14 days and it is marked as stale PR. If no further update for over 14 days, the bot will close the PR. If you want to refresh the PR, please remove |
...ontainerregistry/data-plane/Azure.ContainerRegistry/stable/2021-07-01/containerregistry.json
Outdated
Show resolved
Hide resolved
...ontainerregistry/data-plane/Azure.ContainerRegistry/stable/2021-07-01/containerregistry.json
Outdated
Show resolved
Hide resolved
* add 2021-07-01 swagger * update swagger * update folders * update to support Azure/azure-sdk-for-net#22576 * remove preview items+introduce apiversion * address comments * run prettier-check * fix CI * re-add changes from old preview swagger * address comments * add missing example Co-authored-by: Anne Loomis Thompson <annelo@microsoft.com>
* add 2021-07-01 swagger * update swagger * update folders * update to support Azure/azure-sdk-for-net#22576 * remove preview items+introduce apiversion * address comments * run prettier-check * fix CI * re-add changes from old preview swagger * address comments * add missing example Co-authored-by: Anne Loomis Thompson <annelo@microsoft.com>
MSFT employees can try out our new experience at OpenAPI Hub - one location for using our validation tools and finding your workflow.
Changelog
Please ensure to add changelog with 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
Ensure to check this box if one of the following scenarios meet updates in the PR, so that label “WaitForARMFeedback” will be added automatically to involve ARM API Review. Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs, all “removals” and “adding a new property” no more require ARM API review.
Please 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 there are following updates in the PR, ensure to request an approval from 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.