-
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.ContainerRegistry to add version preview/2023-08-01-preview #25345
[Hub Generated] Review request for Microsoft.ContainerRegistry to add version preview/2023-08-01-preview #25345
Conversation
…ew/2023-06-01-preview to version 2023-07-01-preview
…into AntonioVT-containerregistry-Microsoft.ContainerRegistry-2023-07-01-preview
Next Steps to Merge |
Swagger Validation Report
|
compared swaggers (via Oad v0.10.4)] | new version | base version |
---|---|---|
containerregistry.json | 2023-08-01-preview(f9821dd) | 2023-07-01(main) |
containerregistry.json | 2023-08-01-preview(f9821dd) | 2023-06-01-preview(main) |
The following breaking changes are detected by comparison with the latest preview version:
️🔄
CredScan inProgress [Detail]
️⚠️
LintDiff: 0 Warnings warning [Detail]
compared tags (via openapi-validator v2.1.4) | new version | base version |
---|---|---|
package-2023-08-preview | package-2023-08-preview(f9821dd) | default(main) |
The following errors/warnings exist before current PR submission:
Only 30 items are listed, please refer to log for more details.
Rule | Message |
---|---|
RequiredDefaultResponse |
The response is defined but without a default error response implementation.Consider adding it.' Location: Microsoft.ContainerRegistry/preview/2023-08-01-preview/containerregistry.json#L1648 |
RequiredDefaultResponse |
The response is defined but without a default error response implementation.Consider adding it.' Location: Microsoft.ContainerRegistry/preview/2023-08-01-preview/containerregistry.json#L1902 |
RequiredDefaultResponse |
The response is defined but without a default error response implementation.Consider adding it.' Location: Microsoft.ContainerRegistry/preview/2023-08-01-preview/containerregistry.json#L1944 |
RequiredDefaultResponse |
The response is defined but without a default error response implementation.Consider adding it.' Location: Microsoft.ContainerRegistry/preview/2023-08-01-preview/containerregistry.json#L2198 |
RequiredDefaultResponse |
The response is defined but without a default error response implementation.Consider adding it.' Location: Microsoft.ContainerRegistry/preview/2023-08-01-preview/containerregistry.json#L2240 |
RequiredDefaultResponse |
The response is defined but without a default error response implementation.Consider adding it.' Location: Microsoft.ContainerRegistry/preview/2023-08-01-preview/containerregistry.json#L2286 |
RequiredDefaultResponse |
The response is defined but without a default error response implementation.Consider adding it.' Location: Microsoft.ContainerRegistry/preview/2023-08-01-preview/containerregistry.json#L2338 |
RequiredDefaultResponse |
The response is defined but without a default error response implementation.Consider adding it.' Location: Microsoft.ContainerRegistry/preview/2023-08-01-preview/containerregistry.json#L2380 |
RequiredDefaultResponse |
The response is defined but without a default error response implementation.Consider adding it.' Location: Microsoft.ContainerRegistry/preview/2023-08-01-preview/containerregistry.json#L2416 |
RequiredDefaultResponse |
The response is defined but without a default error response implementation.Consider adding it.' Location: Microsoft.ContainerRegistry/preview/2023-08-01-preview/containerregistry.json#L2455 |
RequiredDefaultResponse |
The response is defined but without a default error response implementation.Consider adding it.' Location: Microsoft.ContainerRegistry/preview/2023-08-01-preview/containerregistry.json#L2498 |
RequiredDefaultResponse |
The response is defined but without a default error response implementation.Consider adding it.' Location: Microsoft.ContainerRegistry/preview/2023-08-01-preview/containerregistry.json#L2550 |
RequiredDefaultResponse |
The response is defined but without a default error response implementation.Consider adding it.' Location: Microsoft.ContainerRegistry/preview/2023-08-01-preview/containerregistry.json#L2605 |
RequiredDefaultResponse |
The response is defined but without a default error response implementation.Consider adding it.' Location: Microsoft.ContainerRegistry/preview/2023-08-01-preview/containerregistry.json#L2656 |
RequiredDefaultResponse |
The response is defined but without a default error response implementation.Consider adding it.' Location: Microsoft.ContainerRegistry/preview/2023-08-01-preview/containerregistry.json#L2692 |
RequiredDefaultResponse |
The response is defined but without a default error response implementation.Consider adding it.' Location: Microsoft.ContainerRegistry/preview/2023-08-01-preview/containerregistry.json#L2776 |
RequiredDefaultResponse |
The response is defined but without a default error response implementation.Consider adding it.' Location: Microsoft.ContainerRegistry/preview/2023-08-01-preview/containerregistry.json#L2821 |
RequiredDefaultResponse |
The response is defined but without a default error response implementation.Consider adding it.' Location: Microsoft.ContainerRegistry/preview/2023-08-01-preview/containerregistry.json#L2857 |
RequiredDefaultResponse |
The response is defined but without a default error response implementation.Consider adding it.' Location: Microsoft.ContainerRegistry/preview/2023-08-01-preview/containerregistry.json#L2899 |
RequiredDefaultResponse |
The response is defined but without a default error response implementation.Consider adding it.' Location: Microsoft.ContainerRegistry/preview/2023-08-01-preview/containerregistry.json#L2945 |
RequiredDefaultResponse |
The response is defined but without a default error response implementation.Consider adding it.' Location: Microsoft.ContainerRegistry/preview/2023-08-01-preview/containerregistry.json#L3000 |
RequiredDefaultResponse |
The response is defined but without a default error response implementation.Consider adding it.' Location: Microsoft.ContainerRegistry/preview/2023-08-01-preview/containerregistry.json#L3058 |
RequiredDefaultResponse |
The response is defined but without a default error response implementation.Consider adding it.' Location: Microsoft.ContainerRegistry/preview/2023-08-01-preview/containerregistry.json#L3730 |
RequiredDefaultResponse |
The response is defined but without a default error response implementation.Consider adding it.' Location: Microsoft.ContainerRegistry/preview/2023-08-01-preview/containerregistry.json#L3772 |
RequiredDefaultResponse |
The response is defined but without a default error response implementation.Consider adding it.' Location: Microsoft.ContainerRegistry/preview/2023-08-01-preview/containerregistry.json#L3818 |
RequiredDefaultResponse |
The response is defined but without a default error response implementation.Consider adding it.' Location: Microsoft.ContainerRegistry/preview/2023-08-01-preview/containerregistry.json#L3870 |
RequiredDefaultResponse |
The response is defined but without a default error response implementation.Consider adding it.' Location: Microsoft.ContainerRegistry/preview/2023-08-01-preview/containerregistry.json#L3928 |
RequiredDefaultResponse |
The response is defined but without a default error response implementation.Consider adding it.' Location: Microsoft.ContainerRegistry/preview/2023-08-01-preview/containerregistry.json#L3982 |
RequiredDefaultResponse |
The response is defined but without a default error response implementation.Consider adding it.' Location: Microsoft.ContainerRegistry/preview/2023-08-01-preview/containerregistry.json#L4021 |
RequiredDefaultResponse |
The response is defined but without a default error response implementation.Consider adding it.' Location: Microsoft.ContainerRegistry/preview/2023-08-01-preview/containerregistry.json#L4063 |
️⚠️
Avocado: 1 Warnings warning [Detail]
Rule | Message |
---|---|
The default tag contains multiple API versions swaggers. readme: specification/containerregistry/resource-manager/readme.md tag: specification/containerregistry/resource-manager/readme.md#tag-package-2023-08-preview |
️️✔️
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 inProgress [Detail]
️️✔️
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
|
Automatic PR validation restarted. This comment will be populated with next steps to merge this PR once validation is completed. Please wait ⌛. |
@ ARM-reviewer, this PR is adding new API version The reason for this is that Azure Policy will use the latest released API, and some built-in policies use preview features. In order to not break Azure Policy, we bundle/ship two APIs together (stable and preview). In the past PR we have defined multiple workitems to fix the issues. These should be fixed by the next API version, which we have planned for ~November 2023. |
@raych1 Regarding Breaking Change in Go, these were approved in our past stable API PR, we are essentially moving from our defined ErrorResponse to the one defined in common-types/v5. Could you help me review/validate again, please? |
Automatic PR validation restarted. This comment will be populated with next steps to merge this PR once validation is completed. Please wait ⌛. |
Updated preview API version name from "2023-07-01-preview" to "2023-08-01-preview" due to conflict with Azure Policy and ARG. |
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.
…into AntonioVT-containerregistry-Microsoft.ContainerRegistry-2023-07-01-preview
/pr RequestMerge |
Swagger pipeline restarted successfully, please wait for status update in this comment. |
… version preview/2023-08-01-preview (#25345) * Adds base for updating Microsoft.ContainerRegistry from version preview/2023-06-01-preview to version 2023-07-01-preview * Updates readme * Updates API version in new specs and examples * Update swagger, examples and readmes * Rename 2023-07-01-preview to 2023-08-01-preview * Rename 2023-07-01-preview to 2023-08-01-preview folder * Add supression rules * suppression from update
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
ARMChangesRequested
is removed from your PR. This should cause the label
WaitForARMFeedback
to 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 help
section 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)
ARMReview
label.Getting help
and https://aka.ms/ci-fix.