-
Notifications
You must be signed in to change notification settings - Fork 5.6k
VI stable/2024-01-01 - AMSless accounts #25440
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
…22-07-20-preview to version 2024-01-01
Next Steps to Merge✔️ All automated merging requirements have been met! Refer to step 4 in the PR workflow diagram (even if your PR is for data plane, not ARM). |
Swagger Validation Report
|
| compared swaggers (via Oad v0.10.4)] | new version | base version |
|---|---|---|
| vi.json | 2024-01-01(63e0e4f) | 2022-08-01(main) |
| vi.json | 2024-01-01(63e0e4f) | 2022-07-20-preview(main) |
The following breaking changes are detected by comparison with the latest stable version:
| Rule | Message |
|---|---|
1005 - RemovedPath |
The new version is missing a path that was found in the old version. Was path '/providers/Microsoft.VideoIndexer/locations/{location}/userClassicAccounts' removed or restructured? Old: Microsoft.VideoIndexer/stable/2022-08-01/vi.json#L490:5 |
1005 - RemovedPath |
The new version is missing a path that was found in the old version. Was path '/providers/Microsoft.VideoIndexer/locations/{location}/classicAccounts/{accountName}' removed or restructured? Old: Microsoft.VideoIndexer/stable/2022-08-01/vi.json#L536:5 |
1006 - RemovedDefinition |
The new version is missing a definition that was found in the old version. Was 'MediaServicesForPutRequest' removed or renamed? New: Microsoft.VideoIndexer/stable/2024-01-01/vi.json#L528:3 Old: Microsoft.VideoIndexer/stable/2022-08-01/vi.json#L710:3 |
1006 - RemovedDefinition |
The new version is missing a definition that was found in the old version. Was 'MediaServicesForPatchRequest' removed or renamed? New: Microsoft.VideoIndexer/stable/2024-01-01/vi.json#L528:3 Old: Microsoft.VideoIndexer/stable/2022-08-01/vi.json#L710:3 |
1007 - RemovedClientParameter |
The new version is missing a client parameter that was found in the old version. Was 'LocationParameter' removed or renamed? New: Microsoft.VideoIndexer/stable/2024-01-01/vi.json#L1015:3 Old: Microsoft.VideoIndexer/stable/2022-08-01/vi.json#L1268:3 |
1011 - AddingResponseCode |
The new version adds a response code '201'. New: Microsoft.VideoIndexer/stable/2024-01-01/vi.json#L331:11 |
1033 - RemovedProperty |
The new version is missing a property found in the old version. Was 'mediaServices' renamed or removed? New: Microsoft.VideoIndexer/stable/2024-01-01/vi.json#L595:7 Old: Microsoft.VideoIndexer/stable/2022-08-01/vi.json#L777:7 |
1033 - RemovedProperty |
The new version is missing a property found in the old version. Was 'mediaServices' renamed or removed? New: Microsoft.VideoIndexer/stable/2024-01-01/vi.json#L647:7 Old: Microsoft.VideoIndexer/stable/2022-08-01/vi.json#L829:7 |
The following breaking changes are detected by comparison with the latest preview version:
| Rule | Message |
|---|---|
| The new version is missing a path that was found in the old version. Was path '/providers/Microsoft.VideoIndexer/locations/{location}/userClassicAccounts' removed or restructured? Old: Microsoft.VideoIndexer/preview/2022-07-20-preview/vi.json#L490:5 |
|
| The new version is missing a path that was found in the old version. Was path '/providers/Microsoft.VideoIndexer/locations/{location}/classicAccounts/{accountName}' removed or restructured? Old: Microsoft.VideoIndexer/preview/2022-07-20-preview/vi.json#L536:5 |
|
| The new version is missing a definition that was found in the old version. Was 'MediaServicesForPutRequest' removed or renamed? New: Microsoft.VideoIndexer/stable/2024-01-01/vi.json#L528:3 Old: Microsoft.VideoIndexer/preview/2022-07-20-preview/vi.json#L794:3 |
|
| The new version is missing a definition that was found in the old version. Was 'MediaServicesForPatchRequest' removed or renamed? New: Microsoft.VideoIndexer/stable/2024-01-01/vi.json#L528:3 Old: Microsoft.VideoIndexer/preview/2022-07-20-preview/vi.json#L794:3 |
|
| The new version is missing a client parameter that was found in the old version. Was 'LocationParameter' removed or renamed? New: Microsoft.VideoIndexer/stable/2024-01-01/vi.json#L1015:3 Old: Microsoft.VideoIndexer/preview/2022-07-20-preview/vi.json#L1383:3 |
|
| The new version adds a response code '201'. New: Microsoft.VideoIndexer/stable/2024-01-01/vi.json#L331:11 |
|
| The new version is missing a property found in the old version. Was 'mediaServices' renamed or removed? New: Microsoft.VideoIndexer/stable/2024-01-01/vi.json#L595:7 Old: Microsoft.VideoIndexer/preview/2022-07-20-preview/vi.json#L861:7 |
|
| The new version is missing a property found in the old version. Was 'mediaServices' renamed or removed? New: Microsoft.VideoIndexer/stable/2024-01-01/vi.json#L647:7 Old: Microsoft.VideoIndexer/preview/2022-07-20-preview/vi.json#L913:7 |
️️✔️CredScan succeeded [Detail] [Expand]
There is no credential detected.
️⚠️LintDiff: 4 Warnings warning [Detail]
| compared tags (via openapi-validator v2.1.6) | new version | base version |
|---|---|---|
| package-2024-01 | package-2024-01(63e0e4f) | 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: 'generaterestrictedvieweraccesstoken' in:'Generate_RestrictedViewerAccessToken'. Consider updating the operationId Location: Microsoft.VideoIndexer/stable/2024-01-01/vi.json#L475 |
||
| Use the latest version v5 of types.json. Location: Microsoft.VideoIndexer/stable/2024-01-01/vi.json#L490 |
||
| Use the latest version v5 of types.json. Location: Microsoft.VideoIndexer/stable/2024-01-01/vi.json#L493 |
||
| Use the latest version v5 of types.json. Location: Microsoft.VideoIndexer/stable/2024-01-01/vi.json#L499 |
The following errors/warnings exist before current PR submission:
Only 30 items are listed, please refer to log for more details.
️❌Avocado: 2 Errors, 0 Warnings failed [Detail]
| Rule | Message |
|---|---|
MISSING_APIS_IN_DEFAULT_TAG |
The default tag should contain all APIs. The API path /providers/Microsoft.VideoIndexer/locations/{}/userClassicAccounts is not in the default tag. Please make sure the missing API swaggers are in the default tag.readme: specification/vi/resource-manager/readme.md json: Microsoft.VideoIndexer/stable/2022-08-01/vi.json |
MISSING_APIS_IN_DEFAULT_TAG |
The default tag should contain all APIs. The API path /providers/Microsoft.VideoIndexer/locations/{}/classicAccounts/{} is not in the default tag. Please make sure the missing API swaggers are in the default tag.readme: specification/vi/resource-manager/readme.md json: Microsoft.VideoIndexer/stable/2022-08-01/vi.json |
️️✔️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
|
2. Remove Error Codes from examples and swagger.
|
Hi @dazilb! 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 address or respond to feedback from the ARM API reviewer. |
|
Hi, @dazilb. Your PR has no update for 14 days and it is marked as stale PR. If no further update for over 14 days, the bot will close the PR. If you want to refresh the PR, please remove |
1 similar comment
|
Hi, @dazilb. Your PR has no update for 14 days and it is marked as stale PR. If no further update for over 14 days, the bot will close the PR. If you want to refresh the PR, please remove |
|
Hi, @dazilb. Your PR has no update for 14 days and it is marked as stale PR. If no further update for over 14 days, the bot will close the PR. If you want to refresh the PR, please remove |
3 similar comments
|
Hi, @dazilb. Your PR has no update for 14 days and it is marked as stale PR. If no further update for over 14 days, the bot will close the PR. If you want to refresh the PR, please remove |
|
Hi, @dazilb. Your PR has no update for 14 days and it is marked as stale PR. If no further update for over 14 days, the bot will close the PR. If you want to refresh the PR, please remove |
|
Hi, @dazilb. Your PR has no update for 14 days and it is marked as stale PR. If no further update for over 14 days, the bot will close the PR. If you want to refresh the PR, please remove |
|
/azp run |
|
Azure Pipelines successfully started running 3 pipeline(s). |
|
checks are queued. Will merge it after they pass |
|
Swagger pipeline restarted successfully, please wait for status update in this comment. |
* Adds base for updating Microsoft.VideoIndexer from version preview/2022-07-20-preview to version 2024-01-01 * Updates readme * Updates API version in new specs and examples * 1. Change media services to storage services. 2. Remove Error Codes from examples and swagger. * fix missing example * fix date of examples * fix example dates * fix user assigned identity * add 201 response code --------- Co-authored-by: Omer Haimovich <[email protected]>
* Adds base for updating Microsoft.VideoIndexer from version preview/2022-07-20-preview to version 2024-01-01 * Updates readme * Updates API version in new specs and examples * 1. Change media services to storage services. 2. Remove Error Codes from examples and swagger. * fix missing example * fix date of examples * fix example dates * fix user assigned identity * add 201 response code --------- Co-authored-by: Omer Haimovich <[email protected]>
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] ARM review queue (for merge queues, see [4])
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 (for ARM review queue, [1])
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.Viewing API changes
For convenient view of the API changes made by this PR, refer to the URLs provided in the table
in the
Generated ApiViewcomment added to this PR. You can use ApiView to show API versions diff.Suppressing failures
If one or multiple validation error/warning suppression(s) is detected in your PR, please follow the
Swagger-Suppression-Process
to get approval.
Getting help
and https://aka.ms/ci-fix.