-
Notifications
You must be signed in to change notification settings - Fork 5.3k
[Hub Generated] Review request for Microsoft.Security to add version preview/2023-09-01-preview #24384
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.Security to add version preview/2023-09-01-preview #24384
Conversation
Hi, @ivadim 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. [email protected] |
Swagger Validation Report
|
compared tags (via openapi-validator v2.1.4) | new version | base version |
---|---|---|
package-composite-v3 | package-composite-v3(6339728) | package-composite-v3(main) |
[must fix]The following errors/warnings are introduced by current PR:
Rule | Message | Related RPC [For API reviewers] |
---|---|---|
OperationId should contain the verb: 'listavailableazuredevopsorgs' in:'AzureDevOpsOrgs_ListAvailable'. Consider updating the operationId Location: Microsoft.Security/preview/2023-09-01-preview/securityConnectorsDevOps.json#L19 |
||
OperationId should contain the verb: 'listavailablegithubowners' in:'GitHubOwners_ListAvailable'. Consider updating the operationId Location: Microsoft.Security/preview/2023-09-01-preview/securityConnectorsDevOps.json#L1078 |
||
OperationId should contain the verb: 'listavailablegitlabgroups' in:'GitLabGroups_ListAvailable'. Consider updating the operationId Location: Microsoft.Security/preview/2023-09-01-preview/securityConnectorsDevOps.json#L1321 |
||
OperationId should contain the verb: 'listsubgroups' in:'GitLabSubgroups_List'. Consider updating the operationId Location: Microsoft.Security/preview/2023-09-01-preview/securityConnectorsDevOps.json#L1462 |
||
The resource AzureDevOpsOrg does not have a corresponding delete operation. Location: Microsoft.Security/preview/2023-09-01-preview/securityConnectorsDevOps.json#L1735 |
RPC-Delete-V1-05 | |
The resource AzureDevOpsProject does not have a corresponding delete operation. Location: Microsoft.Security/preview/2023-09-01-preview/securityConnectorsDevOps.json#L1814 |
RPC-Delete-V1-05 | |
The resource AzureDevOpsRepository does not have a corresponding delete operation. Location: Microsoft.Security/preview/2023-09-01-preview/securityConnectorsDevOps.json#L1902 |
RPC-Delete-V1-05 |
️⚠️
Avocado: 1 Warnings warning [Detail]
Rule | Message |
---|---|
The default tag contains multiple API versions swaggers. readme: specification/security/resource-manager/readme.md tag: specification/security/resource-manager/readme.md#tag-package-composite-v3 |
️️✔️
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
|
/azp run unifiedPipeline |
No pipelines are associated with this pull request. |
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
...resource-manager/Microsoft.Security/preview/2023-09-01-preview/securityConnectorsDevOps.json
Outdated
Show resolved
Hide resolved
...resource-manager/Microsoft.Security/preview/2023-09-01-preview/securityConnectorsDevOps.json
Show resolved
Hide resolved
...resource-manager/Microsoft.Security/preview/2023-09-01-preview/securityConnectorsDevOps.json
Outdated
Show resolved
Hide resolved
Please ensure to respond feedbacks from the ARM API reviewer. When you are ready to continue the ARM API review, please remove |
787e420
to
d4751f8
Compare
Hi @ivadim! 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. |
/azp run unifiedPipeline |
No pipelines are associated with this pull request. |
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
Automatic PR validation restarted. This comment will be populated with next steps to merge this PR once validation is completed. Please wait ⌛. |
Hi @ivadim, one or multiple validation error/warning suppression(s) is detected in your PR. Please follow the Swagger-Suppression-Process to get approval. |
If fixed RepeatedPathInfo and PutResponseSchemaDescription . Added others to suppressions list. Could you please approve the suppressions? |
Automatic PR validation restarted. This comment will be populated with next steps to merge this PR once validation is completed. Please wait ⌛. |
Automatic PR validation restarted. This comment will be populated with next steps to merge this PR once validation is completed. Please wait ⌛. |
/pr RequestMerge |
Automatic PR validation started. This comment will be populated with next steps to merge this PR once validation is completed. Please wait ⌛. |
Swagger pipeline restarted successfully, please wait for status update in this comment. |
This is a PR generated at OpenAPI Hub. You can view your work branch via this link.
ARM API Information (Control Plane)
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. Note that this doesn't apply if you are trying to merge a PR that was previously in the private repository.
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.