-
Notifications
You must be signed in to change notification settings - Fork 5.6k
Change for AKS vault tier restore #25264
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
…2023-04-01-preview to version 2023-06-01-preview
|
Hi, @soumyapattnaik! 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 |
|---|---|---|
| dataprotection.json | 2023-06-01-preview(0b3bf4b) | 2023-05-01(main) |
| dataprotection.json | 2023-06-01-preview(0b3bf4b) | 2023-04-01-preview(main) |
The following breaking changes are detected by comparison with the latest preview version:
| Rule | Message |
|---|---|
| The '$ref' property points to different models in the old and new versions. New: Microsoft.DataProtection/preview/2023-06-01-preview/dataprotection.json#L6119:11 Old: Microsoft.DataProtection/preview/2023-04-01-preview/dataprotection.json#L5920:11 |
|
| The new version has a different format than the previous one. New: common-types/resource-management/v4/managedidentity.json#L27:9 Old: Microsoft.DataProtection/preview/2023-04-01-preview/dataprotection.json#L5932:9 |
|
| The new version has a different format than the previous one. New: common-types/resource-management/v4/managedidentity.json#L21:9 Old: Microsoft.DataProtection/preview/2023-04-01-preview/dataprotection.json#L5937:9 |
️️✔️CredScan succeeded [Detail] [Expand]
There is no credential detected.
️⚠️LintDiff: 3 Warnings warning [Detail]
| compared tags (via openapi-validator v2.1.4) | new version | base version |
|---|---|---|
| package-preview-2023-06 | package-preview-2023-06(0b3bf4b) | default(main) |
[must fix]The following errors/warnings are introduced by current PR:
| Rule | Message | Related RPC [For API reviewers] |
|---|---|---|
| OperationId should contain the verb: 'fetchsecondaryrecoverypoints' in:'SecondaryRPs_Fetch'. Consider updating the operationId Location: Microsoft.DataProtection/preview/2023-06-01-preview/dataprotection.json#L1543 |
||
| OperationId should contain the verb: 'fetchcrossregionrestorejob' in:'CrossRegionRestoreJob_Get'. Consider updating the operationId Location: Microsoft.DataProtection/preview/2023-06-01-preview/dataprotection.json#L1773 |
||
| OperationId should contain the verb: 'fetchcrossregionrestorejobs' in:'CrossRegionRestoreJobs_List'. Consider updating the operationId Location: Microsoft.DataProtection/preview/2023-06-01-preview/dataprotection.json#L1829 |
The following errors/warnings exist before current PR submission:
| Rule | Message |
|---|---|
ParametersOrder |
The parameters:operationId,location should be kept in the same order as they present in the path. Location: Microsoft.DataProtection/preview/2023-06-01-preview/dataprotection.json#L64 |
MissingTypeObject |
The schema 'AzureBackupFindRestorableTimeRangesRequestResource' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.DataProtection/preview/2023-06-01-preview/dataprotection.json#L4446 |
MissingTypeObject |
The schema 'AzureBackupFindRestorableTimeRangesResponseResource' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.DataProtection/preview/2023-06-01-preview/dataprotection.json#L4477 |
MissingTypeObject |
The schema 'AzureBackupRecoveryPointResource' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.DataProtection/preview/2023-06-01-preview/dataprotection.json#L4792 |
MissingTypeObject |
The schema 'BackupInstanceResource' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.DataProtection/preview/2023-06-01-preview/dataprotection.json#L5235 |
MissingTypeObject |
The schema 'BackupVaultResource' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.DataProtection/preview/2023-06-01-preview/dataprotection.json#L5423 |
MissingTypeObject |
The schema 'BaseBackupPolicyResource' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.DataProtection/preview/2023-06-01-preview/dataprotection.json#L5483 |
MissingTypeObject |
The schema 'CloudError' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.DataProtection/preview/2023-06-01-preview/dataprotection.json#L5719 |
MissingTypeObject |
The schema 'Error' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.DataProtection/preview/2023-06-01-preview/dataprotection.json#L6369 |
MissingTypeObject |
The schema 'ErrorAdditionalInfo' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.DataProtection/preview/2023-06-01-preview/dataprotection.json#L6407 |
MissingTypeObject |
The schema 'additionalDetails' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.DataProtection/preview/2023-06-01-preview/dataprotection.json#L6673 |
MissingTypeObject |
The schema 'additionalDetails' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.DataProtection/preview/2023-06-01-preview/dataprotection.json#L6730 |
| The x-ms-code-generation-setting extension is being deprecated. Please remove it and move settings to readme file for code generation. Location: Microsoft.DataProtection/preview/2023-06-01-preview/dataprotection.json#L6 |
|
| Do not have duplicate name of x-ms-example, make sure every x-ms-example name unique. Duplicate x-ms-example: Get OperationStatus Location: Microsoft.DataProtection/preview/2023-06-01-preview/dataprotection.json#L228 |
|
| Do not have duplicate name of x-ms-example, make sure every x-ms-example name unique. Duplicate x-ms-example: Get OperationStatus Location: Microsoft.DataProtection/preview/2023-06-01-preview/dataprotection.json#L276 |
|
| OperationId should contain the verb: 'validaterestore' in:'BackupInstances_ValidateForRestore'. Consider updating the operationId Location: Microsoft.DataProtection/preview/2023-06-01-preview/dataprotection.json#L2418 |
|
| OperationId should contain the verb: 'findrestorabletimeranges' in:'RestorableTimeRanges_Find'. Consider updating the operationId Location: Microsoft.DataProtection/preview/2023-06-01-preview/dataprotection.json#L2544 |
|
| OperationId should contain the verb: 'exportbackupjobs' in:'ExportJobs_Trigger'. Consider updating the operationId Location: Microsoft.DataProtection/preview/2023-06-01-preview/dataprotection.json#L2769 |
|
| Do not have duplicate name of x-ms-example, make sure every x-ms-example name unique. Duplicate x-ms-example: List OperationsRequestObject Location: Microsoft.DataProtection/preview/2023-06-01-preview/dataprotection.json#L3431 |
|
| Do not have duplicate name of x-ms-example, make sure every x-ms-example name unique. Duplicate x-ms-example: List OperationsRequestObject Location: Microsoft.DataProtection/preview/2023-06-01-preview/dataprotection.json#L3483 |
|
| Do not have duplicate name of x-ms-example, make sure every x-ms-example name unique. Duplicate x-ms-example: List OperationsRequestObject Location: Microsoft.DataProtection/preview/2023-06-01-preview/dataprotection.json#L3535 |
|
| Do not have duplicate name of x-ms-example, make sure every x-ms-example name unique. Duplicate x-ms-example: List OperationsRequestObject Location: Microsoft.DataProtection/preview/2023-06-01-preview/dataprotection.json#L3587 |
|
| Do not have duplicate name of x-ms-example, make sure every x-ms-example name unique. Duplicate x-ms-example: List OperationsRequestObject Location: Microsoft.DataProtection/preview/2023-06-01-preview/dataprotection.json#L3639 |
|
| Do not have duplicate name of x-ms-example, make sure every x-ms-example name unique. Duplicate x-ms-example: Get DefaultOperationsRequestObject Location: Microsoft.DataProtection/preview/2023-06-01-preview/dataprotection.json#L3749 |
|
| Do not have duplicate name of x-ms-example, make sure every x-ms-example name unique. Duplicate x-ms-example: Get DefaultOperationsRequestObject Location: Microsoft.DataProtection/preview/2023-06-01-preview/dataprotection.json#L3804 |
|
| Do not have duplicate name of x-ms-example, make sure every x-ms-example name unique. Duplicate x-ms-example: Get DefaultOperationsRequestObject Location: Microsoft.DataProtection/preview/2023-06-01-preview/dataprotection.json#L3859 |
|
| Do not have duplicate name of x-ms-example, make sure every x-ms-example name unique. Duplicate x-ms-example: Get DefaultOperationsRequestObject Location: Microsoft.DataProtection/preview/2023-06-01-preview/dataprotection.json#L3914 |
|
| Do not have duplicate name of x-ms-example, make sure every x-ms-example name unique. Duplicate x-ms-example: Get DefaultOperationsRequestObject Location: Microsoft.DataProtection/preview/2023-06-01-preview/dataprotection.json#L3969 |
️️✔️Avocado succeeded [Detail] [Expand]
Validation passes for Avocado.
️❌SwaggerAPIView: 0 Errors, 0 Warnings failed [Detail]
️️✔️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
|
|
Thank you for your contribution soumyapattnaik! We will review the pull request and get back to you soon. |
|
Hi @soumyapattnaik! Your PR has some issues. Please fix the CI issues, if present, in following order:
If you need further help, please reach out on the Teams channel aka.ms/azsdk/support/specreview-channel. |
|
Hi @soumyapattnaik! For review efficiency consideration, when creating a new API version, it is required to place API specs of the base version in the first commit, and push new version updates into successive commits. You can use OpenAPIHub to initialize the PR for adding a new version. |
|
Please fill in the PR template/questionnaire like purpose of the PR and due diligence. |
|
Please also review the linter errors and address any that you can: especially those under [must fix]The following errors/warnings are introduced by current PR: |
|
Please address or respond to feedback from the ARM API reviewer. |
Next Steps to Merge
|
|
There appear to be some typos to fix there |
This is not something i am changing currently. It is from older swagger 2023-04-01-preview.
fixed typos as part of commit 8480723 |
Job cancelation, in progress and correctness fix
|
Please address the swagger linter errors In reply to: 1684837331 |
@sjanamma I don't see any linter errors now. can you pls recheck |
x-ms-long-running-operation-options wasn't added in this PR. It is present in latest stable - https://github.com/Azure/azure-rest-api-specs/pull/24715/files Also this PR is targetting management plane APIs and not control plane APIs |
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.