-
Notifications
You must be signed in to change notification settings - Fork 5.6k
[Hub Generated] Review request for Microsoft.Cache to add version stable/2023-08-01 #25215
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
Conversation
…1-preview to version 2023-08-01
|
Hi, @koderjoker! Thank you for your pull request. To help get your PR merged: Generated ApiView comment added to this PR. You can use ApiView to show API versions diff. |
Swagger Validation Report
|
| compared swaggers (via Oad v0.10.4)] | new version | base version |
|---|---|---|
| redis.json | 2023-08-01(9f2ed77) | 2023-04-01(main) |
| redis.json | 2023-08-01(9f2ed77) | 2023-05-01-preview(main) |
The following breaking changes are detected by comparison with the latest stable version:
️️✔️CredScan succeeded [Detail] [Expand]
There is no credential detected.
️⚠️LintDiff: 4 Warnings warning [Detail]
| compared tags (via openapi-validator v2.1.4) | new version | base version |
|---|---|---|
| package-2023-08 | package-2023-08(9f2ed77) | default(main) |
[must fix]The following errors/warnings are introduced by current PR:
| Rule | Message | Related RPC [For API reviewers] |
|---|---|---|
| The response of operation:'AccessPolicy_CreateUpdate' is defined without 'systemData'. Consider adding the systemData to the response. Location: Microsoft.Cache/stable/2023-08-01/redis.json#L1778 |
||
| The response of operation:'AccessPolicy_Get' is defined without 'systemData'. Consider adding the systemData to the response. Location: Microsoft.Cache/stable/2023-08-01/redis.json#L1894 |
||
| The response of operation:'AccessPolicyAssignment_CreateUpdate' is defined without 'systemData'. Consider adding the systemData to the response. Location: Microsoft.Cache/stable/2023-08-01/redis.json#L1986 |
||
| The response of operation:'AccessPolicyAssignment_Get' is defined without 'systemData'. Consider adding the systemData to the response. Location: Microsoft.Cache/stable/2023-08-01/redis.json#L2102 |
The following errors/warnings exist before current PR submission:
Only 30 items are listed, please refer to log for more details.
| Rule | Message |
|---|---|
PathResourceTypeNameCamelCase |
Resource type naming must follow camel case. Path: '/subscriptions/{subscriptionId}/providers/Microsoft.Cache/CheckNameAvailability' Location: Microsoft.Cache/stable/2023-08-01/redis.json#L73 |
MissingTypeObject |
The schema 'Sku' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.Cache/stable/2023-08-01/redis.json#L2195 |
MissingTypeObject |
The schema 'RedisCommonProperties' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.Cache/stable/2023-08-01/redis.json#L2235 |
MissingTypeObject |
The schema 'RedisCreateProperties' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.Cache/stable/2023-08-01/redis.json#L2392 |
MissingTypeObject |
The schema 'RedisUpdateProperties' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.Cache/stable/2023-08-01/redis.json#L2424 |
MissingTypeObject |
The schema 'RedisProperties' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.Cache/stable/2023-08-01/redis.json#L2439 |
MissingTypeObject |
The schema 'RedisCreateParameters' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.Cache/stable/2023-08-01/redis.json#L2523 |
MissingTypeObject |
The schema 'RedisUpdateParameters' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.Cache/stable/2023-08-01/redis.json#L2563 |
MissingTypeObject |
The schema 'RedisAccessKeys' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.Cache/stable/2023-08-01/redis.json#L2584 |
MissingTypeObject |
The schema 'RedisFirewallRule' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.Cache/stable/2023-08-01/redis.json#L2599 |
MissingTypeObject |
The schema 'RedisFirewallRuleProperties' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.Cache/stable/2023-08-01/redis.json#L2625 |
MissingTypeObject |
The schema 'RedisFirewallRuleListResult' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.Cache/stable/2023-08-01/redis.json#L2642 |
MissingTypeObject |
The schema 'RedisResource' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.Cache/stable/2023-08-01/redis.json#L2659 |
MissingTypeObject |
The schema 'RedisInstanceDetails' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.Cache/stable/2023-08-01/redis.json#L2688 |
MissingTypeObject |
The schema 'RedisListResult' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.Cache/stable/2023-08-01/redis.json#L2726 |
MissingTypeObject |
The schema 'RedisRegenerateKeyParameters' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.Cache/stable/2023-08-01/redis.json#L2743 |
MissingTypeObject |
The schema 'RedisRebootParameters' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.Cache/stable/2023-08-01/redis.json#L2763 |
IntegerTypeMustHaveFormat |
The integer type does not have a format, please add it. Location: Microsoft.Cache/stable/2023-08-01/redis.json#L2785 |
MissingTypeObject |
The schema 'ExportRDBParameters' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.Cache/stable/2023-08-01/redis.json#L2793 |
MissingTypeObject |
The schema 'ImportRDBParameters' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.Cache/stable/2023-08-01/redis.json#L2822 |
MissingTypeObject |
The schema 'ScheduleEntry' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.Cache/stable/2023-08-01/redis.json#L2849 |
MissingTypeObject |
The schema 'ScheduleEntries' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.Cache/stable/2023-08-01/redis.json#L2887 |
MissingTypeObject |
The schema 'RedisPatchSchedule' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.Cache/stable/2023-08-01/redis.json#L2904 |
TrackedResourcePatchOperation |
Tracked resource 'RedisPatchSchedule' must have patch operation that at least supports the update of tags. Location: Microsoft.Cache/stable/2023-08-01/redis.json#L2904 |
MissingTypeObject |
The schema 'RedisPatchScheduleListResult' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.Cache/stable/2023-08-01/redis.json#L2927 |
MissingTypeObject |
The schema 'RedisForceRebootResponse' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.Cache/stable/2023-08-01/redis.json#L2944 |
MissingTypeObject |
The schema 'RedisLinkedServer' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.Cache/stable/2023-08-01/redis.json#L2954 |
MissingTypeObject |
The schema 'RedisLinkedServerWithProperties' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.Cache/stable/2023-08-01/redis.json#L2964 |
MissingTypeObject |
The schema 'RedisLinkedServerProperties' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.Cache/stable/2023-08-01/redis.json#L2979 |
MissingTypeObject |
The schema 'RedisLinkedServerWithPropertiesList' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.Cache/stable/2023-08-01/redis.json#L2994 |
️️✔️Avocado succeeded [Detail] [Expand]
Validation passes for Avocado.
️️✔️SwaggerAPIView succeeded [Detail] [Expand]
️️✔️TypeSpecAPIView 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.
️️✔️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).
️️✔️PR Summary succeeded [Detail] [Expand]
Validation passes for Summary.
️️✔️Automated merging requirements met succeeded [Detail] [Expand]
Swagger Generation Artifacts
|
Generated ApiView
|
|
Hi @koderjoker! The automation detected breaking changes in this pull request. As a result, it added the
|
* add flush operation to 2023-08-01 redis api version * Add "x-ms-long-running-operation-options" and "headers" properties * remove OperationStatusResult * remove 200 response code * Revert "remove 200 response code" This reverts commit 1f9c78f. * empty body for 200 response * add schema ref * use CacheNameParameter * "name" -> "cacheName" * add cacheName to flush example --------- Co-authored-by: Austin Tolani <austintolani@microsoft.com>
Next Steps to Merge |
|
Question for those reviewing this PR: In this PR we add a new |
Adds UpdateChannel property to Redis-API
|
Automatic PR validation restarted. This comment will be populated with next steps to merge this PR once validation is completed. Please wait ⌛. |
|
Breaking changes previously reviewed and approved in #23745 |
This is due to how SDKs are implemented currently, so that SDKs can deserialize the final response that location header will return at the end. This mandate will go away in future once final-state-schema property is implemented and consumed by all sdks. |
samsaha-ms
left a comment
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.
LGTM.
|
/azp run |
|
Automatic PR validation restarted. This comment will be populated with next steps to merge this PR once validation is completed. Please wait ⌛. |
|
Azure Pipelines successfully started running 2 pipeline(s). |
|
Hi @koderjoker , these names are not friendly to users, these are caused by duplicate schema name, please remove |
|
@Alancere would love to get more context on this.
cc. @austintolani for swagger changes regarding OperationStatusResult |
|
Yes there are different $ref "../../../../../common-types/resource-management/v5/types.json#/definitions/OperationStatusResult" and ”../../ ../../../common-types/resource-management/v3/types.json#/definitions/OperationStatusResult" and others, which will cause duplicate schema, lenient-model-deduplication config will avoid duplicate schema name, but this will have a user-unfriendly |
|
@Alancere Do you mean that it is best practice RPs to always unify on latest version of common-type, and get any breaking change that causes approved, even for GA RPs? |
|
@TimLovellSmith , from SDK perspective it doesn't allow to have duplicated schema otherwise the code generated isn't easy to be consumed by end user. Regarding how to avoid the duplicated schema, there're different approaches. Either consolidating the common-types reference to one version or adding the duplicated schema in local swagger rather than referencing from common-types if the former consolidation approach would cause breaking change on REST api. |
@raych1, I have one query, does it cause any SDK issue if we use different common-type versions for different models but same version for same common-type across swagger? |
specification/redis/resource-manager/Microsoft.Cache/stable/2023-08-01/redis.json
Show resolved
Hide resolved
|
/pr RequestMerge |
…ble/2023-08-01 (#25215) * Adds base for updating Microsoft.Cache from version preview/2023-05-01-preview to version 2023-08-01 * Updates readme * Updates API version in new specs and examples * Add flush operation to 2023-08-01 Redis API version (#25298) * add flush operation to 2023-08-01 redis api version * Add "x-ms-long-running-operation-options" and "headers" properties * remove OperationStatusResult * remove 200 response code * Revert "remove 200 response code" This reverts commit 1f9c78f. * empty body for 200 response * add schema ref * use CacheNameParameter * "name" -> "cacheName" * add cacheName to flush example --------- Co-authored-by: Austin Tolani <austintolani@microsoft.com> * Adds UpdateChannel property to Redis-API (#25379) Adds UpdateChannel property to Redis-API * use v3 for OperationStatusResult * remove lenient-model-deduplication in readme.go.md * Update ErrorResponse to v3 --------- Co-authored-by: Austin Tolani <46536757+austintolani@users.noreply.github.com> Co-authored-by: Austin Tolani <austintolani@microsoft.com> Co-authored-by: Oscar Barbosa Aquino <32723476+Darfeikus@users.noreply.github.com>

This is a PR generated at OpenAPI Hub. You can view your work branch via this link.
ARM (Control Plane) API Specification Update Pull Request
PR review workflow diagram
Please understand this diagram before proceeding. It explains how to get your PR approved & merged.
[1] public repo review queue, private repo review queue
The PRs are processed by time opened, ascending. Your PR may show up on 2nd or later page.
If you addressed Step 1 from the diagram and your PR is not showing up in the queue, ensure the label
ARMChangesRequestedis removed from your PR. This should cause the label
WaitForARMFeedbackto be added.[2] https://aka.ms/azsdk/support/specreview-channel
[3] List of SDK breaking changes approvers in pinned Teams announcement
[4] public repo merge queue, private repo merge queue
If you need further help with anything, see
Getting helpsection below.Purpose of this PR
What's the purpose of this PR? Check all that apply. This is mandatory!
Due diligence checklist
To merge this PR, you must go through the following checklist and confirm you understood
and followed the instructions by checking all the boxes:
ARM resource provider contract and
REST guidelines (estimated time: 4 hours).
I understand this is required before I can proceed to Step 2, "ARM Review", for this PR.
Breaking changes review (Step 1)
you must follow the breaking changes process.
IMPORTANT This applies even if:
Such claims must be reviewed, and the process is the same.
ARM API changes review (Step 2)
ARMReviewlabel.Getting help
and https://aka.ms/ci-fix.