Added a new resource type for RP - Microsoft.SecurityAndCompliance #13323
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Hi, @fangsu-dccore 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
|
| Rule | Message |
|---|---|
| Based on the response model schema, operation 'PrivateLinkResourcesForMIPPolicySync_ListByService' might be pageable. Consider adding the x-ms-pageable extension. Location: Microsoft.SecurityAndCompliance/stable/2021-03-08/privateLinkServicesForMIPPolicySync.json#L536 |
|
| The child tracked resource, 'privateEndpointConnections' with immediate parent 'PrivateLinkServicesForEDMUploadDescription', must have a list by immediate parent operation. Location: Microsoft.SecurityAndCompliance/stable/2021-03-08/privateLinkServicesForMIPPolicySync.json#L627 |
|
| The child tracked resource, 'privateLinkResources' with immediate parent 'PrivateLinkServicesForEDMUploadDescription', must have a list by immediate parent operation. Location: Microsoft.SecurityAndCompliance/stable/2021-03-08/privateLinkServicesForMIPPolicySync.json#L627 |
|
| The child tracked resource, 'privateEndpointConnections' with immediate parent 'PrivateLinkServicesForM365ComplianceCenterDescription', must have a list by immediate parent operation. Location: Microsoft.SecurityAndCompliance/stable/2021-03-08/privateLinkServicesForMIPPolicySync.json#L627 |
|
| The child tracked resource, 'privateLinkResources' with immediate parent 'PrivateLinkServicesForM365ComplianceCenterDescription', must have a list by immediate parent operation. Location: Microsoft.SecurityAndCompliance/stable/2021-03-08/privateLinkServicesForMIPPolicySync.json#L627 |
|
| The child tracked resource, 'privateEndpointConnections' with immediate parent 'PrivateLinkServicesForM365SecurityCenterDescription', must have a list by immediate parent operation. Location: Microsoft.SecurityAndCompliance/stable/2021-03-08/privateLinkServicesForMIPPolicySync.json#L627 |
|
| The child tracked resource, 'privateLinkResources' with immediate parent 'PrivateLinkServicesForM365SecurityCenterDescription', must have a list by immediate parent operation. Location: Microsoft.SecurityAndCompliance/stable/2021-03-08/privateLinkServicesForMIPPolicySync.json#L627 |
|
| The child tracked resource, 'privateEndpointConnections' with immediate parent 'PrivateLinkServicesForO365ManagementActivityAPIDescription', must have a list by immediate parent operation. Location: Microsoft.SecurityAndCompliance/stable/2021-03-08/privateLinkServicesForMIPPolicySync.json#L627 |
|
| The child tracked resource, 'privateLinkResources' with immediate parent 'PrivateLinkServicesForO365ManagementActivityAPIDescription', must have a list by immediate parent operation. Location: Microsoft.SecurityAndCompliance/stable/2021-03-08/privateLinkServicesForMIPPolicySync.json#L627 |
|
| The child tracked resource, 'privateEndpointConnections' with immediate parent 'PrivateLinkServicesForSCCPowershellDescription', must have a list by immediate parent operation. Location: Microsoft.SecurityAndCompliance/stable/2021-03-08/privateLinkServicesForMIPPolicySync.json#L627 |
️️✔️Avocado succeeded [Detail] [Expand]
Validation passes for Avocado.
️️✔️ModelValidation succeeded [Detail] [Expand]
Validation passes for ModelValidation.
️️✔️SemanticValidation succeeded [Detail] [Expand]
Validation passes for SemanticValidation.
️️✔️[Staging] Cross Version BreakingChange (Base on preview version) succeeded [Detail] [Expand]
There are no breaking changes.
️️✔️[Staging] Cross Version BreakingChange (Base on stable version) succeeded [Detail] [Expand]
There are no breaking changes.
- Compared Swaggers (Based on Oad v0.8.6)
- original: stable/2021-01-11/common-types.json <---> new: stable/2021-03-08/common-types.json
- original: stable/2021-01-11/privateLinkServicesForEDMUpload.json <---> new: stable/2021-03-08/privateLinkServicesForEDMUpload.json
- original: stable/2021-01-11/privateLinkServicesForM365ComplianceCenter.json <---> new: stable/2021-03-08/privateLinkServicesForM365ComplianceCenter.json
- original: stable/2021-01-11/privateLinkServicesForM365SecurityCenter.json <---> new: stable/2021-03-08/privateLinkServicesForM365SecurityCenter.json
- original: stable/2021-01-11/privateLinkServicesForO365ManagementActivityAPI.json <---> new: stable/2021-03-08/privateLinkServicesForO365ManagementActivityAPI.json
- original: stable/2021-01-11/privateLinkServicesForSCCPowershell.json <---> new: stable/2021-03-08/privateLinkServicesForSCCPowershell.json
️️✔️CredScan succeeded [Detail] [Expand]
There is no credential detected.
️⚠️[Staging] SDK Track2 Validation: 26 Warnings warning [Detail]
Only 10 items are listed, please refer to log for more details.
- The following tags are being changed in this PR
| Rule | Message |
|---|---|
| "readme":"securityandcompliance/resource-manager/readme.md", "tag":"package-2021-01-11", "details":"The schema 'ServiceAccessPolicyEntry' with an undefined type and decalared properties is a bit ambigious. This has been auto-corrected to 'type:object'" |
|
| "readme":"securityandcompliance/resource-manager/readme.md", "tag":"package-2021-01-11", "details":"The schema 'ServicesResource' with an undefined type and decalared properties is a bit ambigious. This has been auto-corrected to 'type:object'" |
|
| "readme":"securityandcompliance/resource-manager/readme.md", "tag":"package-2021-01-11", "details":"The schema 'PrivateEndpoint' with an undefined type and decalared properties is a bit ambigious. This has been auto-corrected to 'type:object'" |
|
| "readme":"securityandcompliance/resource-manager/readme.md", "tag":"package-2021-01-11", "details":"The schema 'PrivateEndpointConnection' with an undefined type and decalared properties is a bit ambigious. This has been auto-corrected to 'type:object'" |
|
| "readme":"securityandcompliance/resource-manager/readme.md", "tag":"package-2021-01-11", "details":"The schema 'PrivateEndpointConnectionProperties' with an undefined type and decalared properties is a bit ambigious. This has been auto-corrected to 'type:object'" |
|
| "readme":"securityandcompliance/resource-manager/readme.md", "tag":"package-2021-01-11", "details":"The schema 'PrivateLinkServiceConnectionState' with an undefined type and decalared properties is a bit ambigious. This has been auto-corrected to 'type:object'" |
|
| "readme":"securityandcompliance/resource-manager/readme.md", "tag":"package-2021-01-11", "details":"The schema 'PrivateLinkResource' with an undefined type and decalared properties is a bit ambigious. This has been auto-corrected to 'type:object'" |
|
| "readme":"securityandcompliance/resource-manager/readme.md", "tag":"package-2021-01-11", "details":"The schema 'PrivateLinkResourceProperties' with an undefined type and decalared properties is a bit ambigious. This has been auto-corrected to 'type:object'" |
|
| "readme":"securityandcompliance/resource-manager/readme.md", "tag":"package-2021-01-11", "details":"The schema 'PrivateEndpointConnectionListResult' with an undefined type and decalared properties is a bit ambigious. This has been auto-corrected to 'type:object'" |
|
| "readme":"securityandcompliance/resource-manager/readme.md", "tag":"package-2021-01-11", "details":"The schema 'PrivateLinkResourceListResult' with an undefined type and decalared properties is a bit ambigious. This has been auto-corrected to 'type:object'" |
️️✔️[Staging] PrettierCheck succeeded [Detail] [Expand]
Validation passes for PrettierCheck.
️️✔️[Staging] SpellCheck succeeded [Detail] [Expand]
Validation passes for SpellCheck.
openapi-workflow-bot
bot
added
the
WaitForARMFeedback
Swagger Generation Artifacts
|
|
Hi, @fangsu-dccore your PR are labelled with WaitForARMFeedback. A notification email will be sent out shortly afterwards to notify ARM review board([email protected]). cc @ |
|
Hi @fangsu-dccore, Your PR has some issues. Please fix the CI sequentially by following the order of
|
This was referenced Mar 8, 2021
This was referenced Mar 8, 2021
openapi-pipeline-app
bot
added
CI-FixRequiredOnFailure
and removed
CI-FixRequiredOnFailure
labels
|
Hi, @fangsu-dccore your PR are labelled with WaitForARMFeedback. A notification email will be sent out shortly afterwards to notify ARM review board([email protected]). cc @chunyu3 |
openapi-pipeline-app
bot
added
CI-FixRequiredOnFailure
and removed
CI-BreakingChange-Python
labels
openapi-pipeline-app
bot
added
CI-BreakingChange-Python
and removed
CI-FixRequiredOnFailure
labels
Comment on lines
28
to
31
| ``` yaml $(go) && $(multiapi) | ||
| batch: | ||
| - tag: package-2021-03-08 | ||
| ``` |
There was a problem hiding this comment.
Could we remove this and add this entry to the batch section above on line 15?
There was a problem hiding this comment.
Do you mean like this?:
batch:
- tag: package-2021-01-11
- tag: package-2021-03-08Check(I think it is Fix-SemanticValidation-Error) failed after I change it to this.
There was a problem hiding this comment.
That should be irrelevant. Let us try this first
There was a problem hiding this comment.
I do not really understand it, can you be more specific? and give me an example?
There was a problem hiding this comment.
but it will throw exceptions if I move this entry up, Updated readme.md file · 4da7043 (github.com)
chunyu3
approved these changes
Mar 9, 2021
This was referenced Mar 9, 2021
Closed
mkarmark
pushed a commit
to mkarmark/azure-rest-api-specs
that referenced
this pull request
Jul 21, 2021
…zure#13323) * Added a new api version on Mar 8th * Added apis for /MIPPolicySync * Updated readme.md file * Updated readme.md file * Fixed check failures * updated author's name * updated default tag * updated readme * add title and description in readme.md * fix readme.go.md * Fixed typo Co-authored-by: ArcturusZhang <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
MSFT employees can try out our new experience at OpenAPI Hub - one location for using our validation tools and finding your workflow.
Changelog
Please ensure to add changelog with this PR by answering the following questions.
Contribution checklist:
If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist
Ensure to check this box if one of the following scenarios meet updates in the PR, so that label “WaitForARMFeedback” will be added automatically to involve ARM API Review. Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs, all “removals” and “adding a new property” no more require ARM API review.
Please 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 there are following updates in the PR, ensure to request an approval from Breaking Change Review Board as defined in the Breaking Change Policy.
Action: to initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Addition details on the process and office hours are on the Breaking change Wiki.
Please follow the link to find more details on PR review process.