Adding Workspace Manager Members#21276
Conversation
|
Hi, @rheabansal 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 tags (via openapi-validator v2.0.0) | new version | base version |
|---|---|---|
| package-preview-2023-03 | package-preview-2023-03(4e8c22f) | package-preview-2023-03(release-securityinsights-Microsoft.SecurityInsights-2023-03-01-preview) |
[must fix]The following errors/warnings are introduced by current PR:
| Rule | Message | Related RPC [For API reviewers] |
|---|---|---|
ResourceNameRestriction |
The resource name parameter 'workspaceName' should be defined with a 'pattern' restriction. Location: Microsoft.SecurityInsights/preview/2023-03-01-preview/WorkspaceManagerMembers.json#L37 |
RPC-V2-URI-5 |
ResourceNameRestriction |
The resource name parameter 'workspaceName' should be defined with a 'pattern' restriction. Location: Microsoft.SecurityInsights/preview/2023-03-01-preview/WorkspaceManagerMembers.json#L91 |
RPC-V2-URI-5 |
ResourceNameRestriction |
The resource name parameter 'workspaceManagerMemberName' should be defined with a 'pattern' restriction. Location: Microsoft.SecurityInsights/preview/2023-03-01-preview/WorkspaceManagerMembers.json#L91 |
RPC-V2-URI-5 |
️️✔️Avocado succeeded [Detail] [Expand]
Validation passes for Avocado.
️❌~[Staging] SwaggerAPIView: 0 Errors, 0 Warnings failed [Detail]
️️✔️ModelValidation succeeded [Detail] [Expand]
Validation passes for ModelValidation.
️️✔️SemanticValidation succeeded [Detail] [Expand]
Validation passes for SemanticValidation.
️❌PrettierCheck: 3 Errors, 0 Warnings failed [Detail]
| Rule | Message |
|---|---|
HowToFix |
Code style issues found path: 2023-03-01-preview/examples/workspaceManagerMembers/CreateOrUpdateWorkspaceManagerMember.json |
HowToFix |
Code style issues found path: 2023-03-01-preview/examples/workspaceManagerMembers/GetAllWorkspaceManagerMembers.json |
HowToFix |
Code style issues found path: 2023-03-01-preview/examples/workspaceManagerMembers/GetWorkspaceManagerMember.json |
️️✔️SpellCheck succeeded [Detail] [Expand]
Validation passes for SpellCheck.
️️✔️CadlValidation succeeded [Detail] [Expand]
Validation passes for CadlValidation.
️️✔️PR Summary succeeded [Detail] [Expand]
Validation passes for Summary.
Swagger Generation Artifacts
|
Generated ApiView
|
|
Hi, @rheabansal your PR are labelled with WaitForARMFeedback. A notification email will be sent out shortly afterwards to notify ARM review board(armapireview@microsoft.com). |
|
Hi! We initially had these reviewed in the private repo for a different date. Please see the already approved swagger from the PR in the private repo for the Workspace Manager Members here: https://github.com/Azure/azure-rest-api-specs-pr/pull/9049 |
Signed off based on this |
|
Hi, @rheabansal. 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 |
|
This PR was signed off by ARM previously (see history above). We had to add one more property and are reopening for review. Nothing else in the swagger has changed. |
| "description": "The workspace manager member properties", | ||
| "properties": { | ||
| "targetWorkspaceId": { | ||
| "description": "Fully qualified resource ID of the target Sentinel workspace joining the given Sentinel workspace manager", |
There was a problem hiding this comment.
I've seen something about an arm-id format you can use not sure if it is working right now though.
https://azure.github.io/autorest/extensions/#x-ms-arm-id-details
| "properties": { | ||
| "nextLink": { | ||
| "description": "URL to fetch the next set of workspace manager members", | ||
| "readOnly": true, |
|
Hi, @rheabansal. 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, @rheabansal. The PR will be closed since the PR has no update for 28 days. If you still need the PR review to proceed, please reopen it and @ mention PR assignee. |
ARM API Information (Control Plane)
MSFT employees can try out our new experience at OpenAPI Hub - one location for using our validation tools and finding your workflow.
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.