-
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
[Hub Generated] Review request for Microsoft.Cache to add version preview/2020-10-01-preview #11360
[Hub Generated] Review request for Microsoft.Cache to add version preview/2020-10-01-preview #11360
Conversation
[Staging] Swagger Validation Report
️✔️ |
Azure Pipelines successfully started running 1 pipeline(s). |
azure-sdk-for-net - Release
|
azure-sdk-for-python - Release
|
Azure CLI Extension Generation - Release
No readme.md specification configuration files were found that are associated with the files modified in this pull request, or swagger_to_sdk section in readme.md is not configured
|
Trenton Generation - Release
No readme.md specification configuration files were found that are associated with the files modified in this pull request, or swagger_to_sdk section in readme.md is not configured
|
azure-resource-manager-schemas - Release
No readme.md specification configuration files were found that are associated with the files modified in this pull request, or swagger_to_sdk section in readme.md is not configured
|
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run unifiedPipeline |
No pipelines are associated with this pull request. |
azure-sdk-for-python-track2 - Release
No readme.md specification configuration files were found that are associated with the files modified in this pull request, or swagger_to_sdk section in readme.md is not configured
|
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run unifiedPipeline |
No pipelines are associated with this pull request. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I see one small issue left, we should add the mutability details of clusteringPolicy
...senterprise/resource-manager/Microsoft.Cache/preview/2020-10-01-preview/redisenterprise.json
Show resolved
Hide resolved
...senterprise/resource-manager/Microsoft.Cache/preview/2020-10-01-preview/redisenterprise.json
Show resolved
Hide resolved
...senterprise/resource-manager/Microsoft.Cache/preview/2020-10-01-preview/redisenterprise.json
Show resolved
Hide resolved
Azure Pipelines successfully started running 1 pipeline(s). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks about right to me, I guess we are now waiting for arm feedback.
Hi, @greenms 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 |
Hi, @greenms your PR are labelled with WaitForARMFeedback. A notification email will be sent out shortly afterwards to notify ARM review board(armapireview@microsoft.com). cc @akning-ms |
...senterprise/resource-manager/Microsoft.Cache/preview/2020-10-01-preview/redisenterprise.json
Show resolved
Hide resolved
...senterprise/resource-manager/Microsoft.Cache/preview/2020-10-01-preview/redisenterprise.json
Show resolved
Hide resolved
@majastrz But... having re-scanned the PR spec, it seems to me that having additional provisioningStates like "Disabling, Scaling, Updating" has always been allowed according to the following, which implies various updates can change the provisioningState after it reaches a terminal state: "The provisioningState field should be returned on all future GETs, even after it is complete, until some other operation (e.g. a DELETE or UPDATE) causes it to transition to a non-terminal state." |
Adding non-terminal states is allowed, but adding terminal states is not. |
Azure Pipelines successfully started running 1 pipeline(s). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Latest changes look good. Signed off from ARM side.
Azure Pipelines successfully started running 1 pipeline(s). |
I got a notification that someone was asking about adding the Deleting state, but I can't see the comment. That's a non-terminal state, so that's definitely fine. |
Azure Pipelines successfully started running 1 pipeline(s). |
Still signed off from ARM side. |
...senterprise/resource-manager/Microsoft.Cache/preview/2020-10-01-preview/redisenterprise.json
Outdated
Show resolved
Hide resolved
@akning-ms May it be merged? |
…view/2020-10-01-preview (Azure#11360) * New Readme Config File * New Go Language Readme Config File * New Typescript Language Readme Config File * New Python Language Readme Config File * New C# Language Readme Config File * New Ruby Language Readme Config File * New Swagger Spec File * New Swagger Example Spec File * Initial updates for public preview * Add default error response. Add integer format. * Add 200 response to delete operations. * Add custom words for Redis Enterprise. * Update whitespace for prettier. * Update whitespace for prettier. * Update whitespace for prettier. * Revert "Update whitespace for prettier." This reverts commit 4f04b1b. * Revert "Update whitespace for prettier." This reverts commit ccca6d5. * Revert "Update whitespace for prettier." This reverts commit 3d72e6b. * Update whitespace for prettier. * Update Go settings * Including .NET SDK in list of SDKs automatically generated. * Update csharp settings. * Fix typo. * Updates addressing comments from reviewer. * Fix provisioningState errors. * Update clusteringPolicy description and related examples. * Remove Enterprise_E1 SKU. * Updates per comments from reviewer. * Remove illegal terminal states from provisioningState. Add new resourceState. * Utilize common properties from updated v2 types.json * Add 'Deleting' state to ProvisioningState enum.
This is a PR generated at OpenAPI Hub. You can view your work branch via this link.
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.
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 API Review Board as defined in the Breaking Change Policy.
Please follow the link to find more details on PR review process.