-
Notifications
You must be signed in to change notification settings - Fork 5.1k
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
Updating the name for Storage Account Type for Edgzones #23741
Conversation
…ations in Gallery.json
Updating the name for Storage Account Type for Edgzones
Hi, @kjilla 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. vscswagger@microsoft.com |
Swagger Validation Report
|
compared swaggers (via Oad v0.10.4)] | new version | base version |
---|---|---|
gallery.json | 2022-03-03(200d15d) | 2022-03-03(main) |
Rule | Message |
---|---|
1047 - XmsEnumChanged |
The new version has a different x-ms-enum 'name' than the previous one. New: GalleryRP/stable/2022-03-03/gallery.json#L2560:9 Old: GalleryRP/stable/2022-03-03/gallery.json#L2560:9 |
️️✔️
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 v2.0.0) | new version | base version |
---|---|---|
package-2023-03-01 | package-2023-03-01(200d15d) | package-2023-03-01(main) |
package-2022-11-01 | package-2022-11-01(200d15d) | package-2022-11-01(main) |
package-2022-09-04 | package-2022-09-04(200d15d) | package-2022-09-04(main) |
package-2022-03-03 | package-2022-03-03(200d15d) | package-2022-03-03(main) |
The following errors/warnings exist before current PR submission:
Only 30 items are listed, please refer to log for more details.
Rule | Message |
---|---|
ResourceNameRestriction |
The resource name parameter 'galleryName' should be defined with a 'pattern' restriction. Location: GalleryRP/stable/2022-03-03/gallery.json#L37 |
ResourceNameRestriction |
The resource name parameter 'galleryName' should be defined with a 'pattern' restriction. Location: GalleryRP/stable/2022-03-03/gallery.json#L37 |
ResourceNameRestriction |
The resource name parameter 'galleryName' should be defined with a 'pattern' restriction. Location: GalleryRP/stable/2022-03-03/gallery.json#L37 |
ResourceNameRestriction |
The resource name parameter 'galleryName' should be defined with a 'pattern' restriction. Location: GalleryRP/stable/2022-03-03/gallery.json#L37 |
CreateOperationAsyncResponseValidation |
An async PUT operation must set long running operation options 'x-ms-long-running-operation-options' Location: GalleryRP/stable/2022-03-03/gallery.json#L38 |
CreateOperationAsyncResponseValidation |
An async PUT operation must set long running operation options 'x-ms-long-running-operation-options' Location: GalleryRP/stable/2022-03-03/gallery.json#L38 |
CreateOperationAsyncResponseValidation |
An async PUT operation must set long running operation options 'x-ms-long-running-operation-options' Location: GalleryRP/stable/2022-03-03/gallery.json#L38 |
CreateOperationAsyncResponseValidation |
An async PUT operation must set long running operation options 'x-ms-long-running-operation-options' Location: GalleryRP/stable/2022-03-03/gallery.json#L38 |
LongRunningResponseStatusCode |
A 'put' operation 'Galleries_CreateOrUpdate' with x-ms-long-running-operation extension must have a valid terminal success status code 200 or 201. Location: GalleryRP/stable/2022-03-03/gallery.json#L38 |
LongRunningResponseStatusCode |
A 'put' operation 'Galleries_CreateOrUpdate' with x-ms-long-running-operation extension must have a valid terminal success status code 200 or 201. Location: GalleryRP/stable/2022-03-03/gallery.json#L38 |
LongRunningResponseStatusCode |
A 'put' operation 'Galleries_CreateOrUpdate' with x-ms-long-running-operation extension must have a valid terminal success status code 200 or 201. Location: GalleryRP/stable/2022-03-03/gallery.json#L38 |
LongRunningResponseStatusCode |
A 'put' operation 'Galleries_CreateOrUpdate' with x-ms-long-running-operation extension must have a valid terminal success status code 200 or 201. Location: GalleryRP/stable/2022-03-03/gallery.json#L38 |
CreateOperationAsyncResponseValidation |
Only 201 is the supported response code for PUT async response. Location: GalleryRP/stable/2022-03-03/gallery.json#L84 |
CreateOperationAsyncResponseValidation |
Only 201 is the supported response code for PUT async response. Location: GalleryRP/stable/2022-03-03/gallery.json#L84 |
CreateOperationAsyncResponseValidation |
Only 201 is the supported response code for PUT async response. Location: GalleryRP/stable/2022-03-03/gallery.json#L84 |
CreateOperationAsyncResponseValidation |
Only 201 is the supported response code for PUT async response. Location: GalleryRP/stable/2022-03-03/gallery.json#L84 |
LroLocationHeader |
A 202 response should include an Location response header. Location: GalleryRP/stable/2022-03-03/gallery.json#L84 |
LroLocationHeader |
A 202 response should include an Location response header. Location: GalleryRP/stable/2022-03-03/gallery.json#L84 |
LroLocationHeader |
A 202 response should include an Location response header. Location: GalleryRP/stable/2022-03-03/gallery.json#L84 |
LroLocationHeader |
A 202 response should include an Location response header. Location: GalleryRP/stable/2022-03-03/gallery.json#L84 |
UnSupportedPatchProperties |
The patch operation body parameter schema should not contains property name. Location: GalleryRP/stable/2022-03-03/gallery.json#L136 |
UnSupportedPatchProperties |
The patch operation body parameter schema should not contains property type. Location: GalleryRP/stable/2022-03-03/gallery.json#L136 |
UnSupportedPatchProperties |
The patch operation body parameter schema should not contains property name. Location: GalleryRP/stable/2022-03-03/gallery.json#L136 |
UnSupportedPatchProperties |
The patch operation body parameter schema should not contains property type. Location: GalleryRP/stable/2022-03-03/gallery.json#L136 |
UnSupportedPatchProperties |
The patch operation body parameter schema should not contains property name. Location: GalleryRP/stable/2022-03-03/gallery.json#L136 |
UnSupportedPatchProperties |
The patch operation body parameter schema should not contains property type. Location: GalleryRP/stable/2022-03-03/gallery.json#L136 |
UnSupportedPatchProperties |
The patch operation body parameter schema should not contains property name. Location: GalleryRP/stable/2022-03-03/gallery.json#L136 |
UnSupportedPatchProperties |
The patch operation body parameter schema should not contains property type. Location: GalleryRP/stable/2022-03-03/gallery.json#L136 |
LroPatch202 |
The async patch operation should return 202. Location: GalleryRP/stable/2022-03-03/gallery.json#L146 |
LroPatch202 |
The async patch operation should return 202. Location: GalleryRP/stable/2022-03-03/gallery.json#L146 |
️⚠️
Avocado: 1 Warnings warning [Detail]
Rule | Message |
---|---|
The default tag contains multiple API versions swaggers. readme: specification/compute/resource-manager/readme.md tag: specification/compute/resource-manager/readme.md#tag-package-2023-03-01 |
️️✔️
ApiReadinessCheck succeeded [Detail] [Expand]
️⚠️
~[Staging] ServiceAPIReadinessTest: 0 Warnings warning [Detail]
API Test is not triggered due to precheck failure. Check pipeline log for details.
️️✔️
SwaggerAPIView succeeded [Detail] [Expand]
️️✔️
CadlAPIView succeeded [Detail] [Expand]
️️✔️
TypeSpecAPIView succeeded [Detail] [Expand]
️❌
ModelValidation: 61 Errors, 0 Warnings failed [Detail]
Only 30 items are listed, please refer to log for more details.
️️✔️
SemanticValidation succeeded [Detail] [Expand]
Validation passes for SemanticValidation.
️️✔️
PoliCheck succeeded [Detail] [Expand]
Validation passed for PoliCheck.
️️✔️
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.
️️✔️
TypeSpec Validation succeeded [Detail] [Expand]
Validation passes for TypeSpec Validation.
️️✔️
PR Summary succeeded [Detail] [Expand]
Validation passes for Summary.
Swagger Generation Artifacts
|
Generated ApiView
|
Fixing the build issue raised here. |
Hi @kjilla, Your PR has some issues. Please fix the CI sequentially by following the order of
|
Hi @kjilla, one or multiple breaking change(s) is detected in your PR. Please check out the breaking change(s), and provide business justification in the PR comment and @ PR assignee why you must have these change(s), and how external customer impact can be mitigated. Please ensure to follow breaking change policy to request breaking change review and approval before proceeding swagger PR review. |
Justification for breaking change: Because GalleryTargetExtendedLocation.StorageAccountType was added "StandardSSD_LRS" from #22255 while TargetRegion.StorageAccountType and GalleryArtifactPublishingProfileBase.StorageAccountType did not. So I am renaming the enum here. Added breaking change intake form here. The original change to add a new enum was approved by breaking change board earlier. Here the first PR. |
Hi,
I followed the guidance and updated the PR with the comment.
#23741 (comment)
I raised a breaking change intake form. The original PR<#22255> was approved by the review board.
Thanks,
Kusuma
From: Dapeng Zhang ***@***.***>
Sent: Thursday, April 27, 2023 02:25 AM
To: Azure/azure-rest-api-specs ***@***.***>
Cc: Kusuma Jilla ***@***.***>; Mention ***@***.***>
Subject: Re: [Azure/azure-rest-api-specs] Updating the name for Storage Account Type for Edgzones (PR #23741)
Hi @kjilla<https://github.com/kjilla> please follow the guidance here<#23741 (comment)> to get approval from the breaking change review board because your change just introduces a breaking change.
-
Reply to this email directly, view it on GitHub<#23741 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AHVQH5ZQ75ZESMU47SPGEY3XDI3QFANCNFSM6AAAAAAXM6GRMQ>.
You are receiving this because you were mentioned.Message ID: ***@***.******@***.***>>
|
This justification is not quite justified - the track 1 SDK generation issue has been resolved in this way:
|
@ArcturusZhang , since it is enum model-as-string: true, isn't the breaking change non-impacting? they can still provide StorageAccountType.Standard_SSD or EdgeZoneStorageAccountType.Standard_SSD ? I see the only other resolution would be adding directives to all other languages as we did for readme.csharp.md |
please merge @ArcturusZhang . the model validations for galleryRP are all getting addressed in 2022-08-03 release that is in progress |
@ArcturusZhang can you take a look on this pr and merge it ! Thanks |
@ArcturusZhang - is it possible for this one to get merged? It's blocking two projects on our side. Thanks! |
Hey I am sorry but we still have some discussion on our side because this change introduces breaking changes to all of our SDKs. |
ARM API Information (Control Plane)
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 (MS Employees Only):
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 apply 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 copy the existing version into the new directory structure for first commit and then push new changes, including version updates, in separate commits. You can use OpenAPIHub to initialize the PR for adding a new version. For 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 you have any breaking changes as defined in the Breaking Change Policy, request approval from the Breaking Change Review Board.
Action: to initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Additional details on the process and office hours are on the Breaking Change Wiki.
NOTE: To update API(s) in public preview for over 1 year (refer to Retirement of Previews)
Please follow the link to find more details on PR review process.