-
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
Update common types with Operation + OperationListResult #11356
Conversation
Hi, @TimLovellSmith 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] |
[Staging] Swagger Validation Report
️✔️ |
Azure Pipelines successfully started running 1 pipeline(s). |
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-sdk-for-go - 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-sdk-for-java - 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-sdk-for-python - 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 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
|
azure-sdk-for-js - 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-sdk-for-net - 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-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
|
@pilor Looks like common-types v2 lacks these definitions too, should I add them there also? Edit: looks like we can't really 'refactor' redis without upsetting the linter due to a lot of 'breaking change' validations related to read-only, even though this has always really been a read-only API... plus the addition of a few new property definitions (but we don't really return them today). Maybe we should only do the change to depend on common-types in our future api versions? I can revert the redis part unless there's a fair way to suppress these.
|
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.
You could either also add it to v2 or ONLY add it to v2... up to you
…ListResult." which the linter breaking change the detection wasn't a fan of. This reverts commit f8f696f.
Azure Pipelines successfully started running 1 pipeline(s). |
…ng with most of the improvements to descriptions etc.
Azure Pipelines successfully started running 1 pipeline(s). |
Azure Pipelines successfully started running 1 pipeline(s). |
@leni-msft May it be merged? |
@akning-ms @pilor Thank you for the merge and the review! |
* Add titles and descriptions for 'commontypes/v1/Resource' common types. * Define the 'Operation' and 'OperationListResult' common types in common-types v1. * REFATOR: Update 'redis.json' to use common-types v1 OperationListResult. * Revert "REFATOR: Update 'redis.json' to use common-types v1 OperationListResult." which the linter breaking change the detection wasn't a fan of. This reverts commit f8f696f. * Improvements to descriptions, and 'readOnly' annotations on OperationListResult * Fix typo in the Resource description. * Also add the Operation definition to common-types' v2/types.json, along with most of the improvements to descriptions etc. * Revise descriptions with API consumers as intended audience.
This is porting a change to common-types I had proposed but hadn't actually merged for an earlier preview API version for redisEnterprise. And then refactoring the existing 'redis' type to take advantage of it, and to make sure validations happen.
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 API Review Board as defined in the Breaking Change Policy.
Please follow the link to find more details on PR review process.