[Hub Generated] Review request for Microsoft.PolicyInsights to add version stable/2022-09-01#20557
Conversation
|
Hi, @samarthlakhotia 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. vscswagger@microsoft.com |
Swagger Validation Report
|
| compared swaggers (via Oad v0.9.7)] | new version | base version |
|---|---|---|
| attestations.json | 2022-09-01(034b542) | 2021-01-01(main) |
️️✔️CredScan succeeded [Detail] [Expand]
There is no credential detected.
️️✔️LintDiff succeeded [Detail]
| compared tags (via openapi-validator v1.13.0) | new version | base version |
|---|---|---|
| package-2022-09 | package-2022-09(034b542) | default(main) |
The following errors/warnings exist before current PR submission:
| Rule | Message |
|---|---|
R4037 - MissingTypeObject |
The schema 'AttestationListResult' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.PolicyInsights/stable/2022-09-01/attestations.json#L545 |
R4037 - MissingTypeObject |
The schema 'Attestation' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.PolicyInsights/stable/2022-09-01/attestations.json#L563 |
R4037 - MissingTypeObject |
The schema 'AttestationProperties' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.PolicyInsights/stable/2022-09-01/attestations.json#L587 |
R4037 - MissingTypeObject |
The schema 'AttestationEvidence' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.PolicyInsights/stable/2022-09-01/attestations.json#L671 |
R4037 - MissingTypeObject |
The schema 'ErrorResponse' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.PolicyInsights/stable/2022-09-01/attestations.json#L684 |
R4037 - MissingTypeObject |
The schema 'ErrorDefinition' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.PolicyInsights/stable/2022-09-01/attestations.json#L693 |
R4037 - MissingTypeObject |
The schema 'TypedErrorInfo' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.PolicyInsights/stable/2022-09-01/attestations.json#L731 |
️⚠️Avocado: 1 Warnings warning [Detail]
| Rule | Message |
|---|---|
| The default tag contains multiple API versions swaggers. readme: specification/policyinsights/resource-manager/readme.md tag: specification/policyinsights/resource-manager/readme.md#tag-package-2022-09 |
️️✔️ApiReadinessCheck succeeded [Detail] [Expand]
️❌~[Staging] ServiceAPIReadinessTest: 0 Errors, 0 Warnings failed [Detail]
Tag package-2022-09; Prod region: Not deployed; Canary region: Not deployed
️❌~[Staging] TrafficValidation: 0 Errors, 0 Warnings failed [Detail]
Tag package-2022-09; Prod region: Not deployed; Canary region: Not deployed
️️✔️ModelValidation succeeded [Detail] [Expand]
Validation passes for ModelValidation.
️️✔️SemanticValidation succeeded [Detail] [Expand]
Validation passes for SemanticValidation.
️️✔️PoliCheck succeeded [Detail] [Expand]
Validation passed for PoliCheck.
️❌SDK Track2 Validation: 5 Errors, 0 Warnings failed [Detail]
- The following tags are being changed in this PR
- "https://github.com/Azure/azure-rest-api-specs/blob/034b542ef74705dfa05b35b7f28cb5d2ece26de2/specification/policyinsights/resource-manager/readme.md#tag-package-2022-09">policyinsights/resource-manager/readme.md#package-2022-09
| Rule | Message |
|---|---|
PreCheck/DuplicateSchema |
"readme":"policyinsights/resource-manager/readme.md", "tag":"package-2022-09", "details":"Duplicate Schema named 'ErrorResponse' (1 differences):\n - properties.error.$ref: "#/components/schemas/schemas:65" => "#/components/schemas/schemas:298"; This error can be temporarily avoided by using the 'modelerfour.lenient-model-deduplication' setting. NOTE: This setting will be removed in a future version of @autorest/modelerfour; schemas should be updated to fix this issue sooner than that." |
PreCheck/DuplicateSchema |
"readme":"policyinsights/resource-manager/readme.md", "tag":"package-2022-09", "details":"Duplicate Schema named 'ErrorResponse' (1 differences):\n - properties.error.$ref: "#/components/schemas/schemas:65" => "#/components/schemas/schemas:362"; This error can be temporarily avoided by using the 'modelerfour.lenient-model-deduplication' setting. NOTE: This setting will be removed in a future version of @autorest/modelerfour; schemas should be updated to fix this issue sooner than that." |
PreCheck/DuplicateSchema |
"readme":"policyinsights/resource-manager/readme.md", "tag":"package-2022-09", "details":"Duplicate Schema named 'ErrorDefinition' (1 differences):\n - properties.details.$ref: "#/components/schemas/schemas:69" => "#/components/schemas/schemas:302"; This error can be temporarily avoided by using the 'modelerfour.lenient-model-deduplication' setting. NOTE: This setting will be removed in a future version of @autorest/modelerfour; schemas should be updated to fix this issue sooner than that." |
PreCheck/DuplicateSchema |
"readme":"policyinsights/resource-manager/readme.md", "tag":"package-2022-09", "details":"Duplicate Schema named 'ErrorDefinition' (1 differences):\n - properties.details.$ref: "#/components/schemas/schemas:69" => "#/components/schemas/schemas:366"; This error can be temporarily avoided by using the 'modelerfour.lenient-model-deduplication' setting. NOTE: This setting will be removed in a future version of @autorest/modelerfour; schemas should be updated to fix this issue sooner than that." |
|
"readme":"policyinsights/resource-manager/readme.md", "tag":"package-2022-09", "details":"Error: 4 errors occured -- cannot continue." |
️️✔️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).
️️✔️CadlValidation succeeded [Detail] [Expand]
Validation passes for CadlValidation.
️️✔️PR Summary succeeded [Detail] [Expand]
Validation passes for Summary.
Swagger Generation Artifacts
|
Generated ApiView
|
…yInsights-2022-09-01
|
Hi, @samarthlakhotia your PR are labelled with WaitForARMFeedback. A notification email will be sent out shortly afterwards to notify ARM review board(armapireview@microsoft.com). |
…-01' of https://github.com/samarthlakhotia/azure-rest-api-specs into release-policyinsights-Microsoft.PolicyInsights-2022-09-01
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
Hi @samarthlakhotia please help to confirm if ARM manifest is updated and all the api has been deployed |
|
|
@leni-msft could you help to take a look at the api readiness check, Samarth confirmed that the apis has been deployed to prod. |
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
This is a PR generated at OpenAPI Hub. You can view your work branch via this link.
ARM API Information (Control Plane)
Azure 1st Party Service can try out the Shift Left experience to initiate API design review from ADO code repo. If you are interested, may request engineering support by filling in with the form https://aka.ms/ShiftLeftSupportForm.
Changelog
Add a changelog entry for this PR by answering the following questions:
Contribution checklist (MS Employees Only):
If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist
Otherwise your PR may be subject to ARM review requirements. Complete the following:
Check this box if any of the following apply to the PR so that the label "ARMReview" and "WaitForARMFeedback" will be added by bot to kick off ARM API Review. Missing to check this box in the following scenario may result in delays to the ARM manifest review and deployment.
-[ ] To review changes efficiently, ensure you copy the existing version into the new directory structure for first commit and then push new changes, including version updates, in separate commits. You can use OpenAPIHub to initialize the PR for adding a new version. For more details refer to the wiki.
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 you have any breaking changes as defined in the Breaking Change Policy, request approval from the Breaking Change Review Board.
Action: to initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Additional details on the process and office hours are on the Breaking Change Wiki.
NOTE: To update API(s) in public preview for over 1 year (refer to Retirement of Previews)
Please follow the link to find more details on PR review process.