Add Dynamics365 data connector#14214
Add Dynamics365 data connector#14214alfeldsh wants to merge 2 commits intoAzure:masterfrom alfeldsh:feature/alfeldsh/Dynamics365StableAPI
Conversation
|
Hi, @alfeldsh 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. vsswagger@microsoft.com |
|
[Call for Action] To better understand Azure service dev/test scenario, and support Azure service developer better on Swagger and REST API related tests in early phase, please help to fill in with this survey https://aka.ms/SurveyForEarlyPhase. It will take 5 to 10 minutes. If you already complete survey, please neglect this comment. Thanks. |
Swagger Validation Report
|
| Rule | Message |
|---|---|
R4017 - TopLevelResourcesListBySubscription |
The top-level resource 'AlertRule' does not have list by subscription operation, please add it. Location: Microsoft.SecurityInsights/stable/2020-01-01/SecurityInsights.json#L1505 |
R4017 - TopLevelResourcesListBySubscription |
The top-level resource 'AlertRuleTemplate' does not have list by subscription operation, please add it. Location: Microsoft.SecurityInsights/stable/2020-01-01/SecurityInsights.json#L1575 |
R4017 - TopLevelResourcesListBySubscription |
The top-level resource 'Bookmark' does not have list by subscription operation, please add it. Location: Microsoft.SecurityInsights/stable/2020-01-01/SecurityInsights.json#L1792 |
R4017 - TopLevelResourcesListBySubscription |
The top-level resource 'DataConnector' does not have list by subscription operation, please add it. Location: Microsoft.SecurityInsights/stable/2020-01-01/SecurityInsights.json#L1934 |
R4017 - TopLevelResourcesListBySubscription |
The top-level resource 'Incident' does not have list by subscription operation, please add it. Location: Microsoft.SecurityInsights/stable/2020-01-01/SecurityInsights.json#L2248 |
R4018 - OperationsApiResponseSchema |
The response schema of operations API '/providers/Microsoft.SecurityInsights/operations' does not match the ARM specification. Please standardize the schema. Location: Microsoft.SecurityInsights/stable/2020-01-01/SecurityInsights.json#L37 |
| The child tracked resource, 'actions' with immediate parent 'AlertRule', must have a list by immediate parent operation. Location: Microsoft.SecurityInsights/stable/2020-01-01/SecurityInsights.json#L1308 |
|
| The child tracked resource, 'comments' with immediate parent 'Incident', must have a list by immediate parent operation. Location: Microsoft.SecurityInsights/stable/2020-01-01/SecurityInsights.json#L1308 |
|
| Guid used in model definition 'ClientInfo' for property 'objectId'. Usage of Guid is not recommanded. If GUIDs are absolutely required in your service, please get sign off from the Azure API review board. Location: Microsoft.SecurityInsights/stable/2020-01-01/SecurityInsights.json#L1912 |
|
| Guid used in model definition 'IncidentOwnerInfo' for property 'objectId'. Usage of Guid is not recommanded. If GUIDs are absolutely required in your service, please get sign off from the Azure API review board. Location: Microsoft.SecurityInsights/stable/2020-01-01/SecurityInsights.json#L2433 |
️️✔️Avocado succeeded [Detail] [Expand]
Validation passes for Avocado.
️️✔️ModelValidation succeeded [Detail] [Expand]
Validation passes for ModelValidation.
️️✔️SemanticValidation succeeded [Detail] [Expand]
Validation passes for SemanticValidation.
️️✔️Cross Version BreakingChange (Base on preview version) succeeded [Detail] [Expand]
There are no breaking changes.
️️✔️Cross Version BreakingChange (Base on stable version) succeeded [Detail] [Expand]
There are no breaking changes.
️️✔️CredScan succeeded [Detail] [Expand]
There is no credential detected.
️⚠️[Staging] SDK Track2 Validation: 0 Warnings warning [Detail]
- The following tags are being changed in this PR
|:speech_balloon: AutorestCore/Exception|"readme":"securityinsights/resource-manager/readme.md",
"tag":"package-2020-01",
"details":"> Installing AutoRest extension '@microsoft.azure/openapi-validator' (1.8.0)"|
|:speech_balloon: AutorestCore/Exception|"readme":"securityinsights/resource-manager/readme.md",
"tag":"package-2020-01",
"details":"> Installed AutoRest extension '@microsoft.azure/openapi-validator' (1.8.0->1.8.0)"|
The following errors/warnings exist before current PR submission:
| Rule | Message |
|---|---|
| "readme":"securityinsights/resource-manager/readme.md", "tag":"package-2020-01", "details":"Schema 'MCASDataConnectorDataTypes' has a property 'alerts' that is already declared the parent schema 'AlertsDataTypeOfDataConnector' but isn't significantly different. The property has been removed from MCASDataConnectorDataTypes" |
|
| 💬 AutorestCore/Exception | "readme":"securityinsights/resource-manager/readme.md", "tag":"package-2020-01", "details":"> Loading AutoRest extension '@autorest/modelerfour' (4.15.456->4.15.456)" |
️️✔️[Staging] PrettierCheck succeeded [Detail] [Expand]
Validation passes for PrettierCheck.
️️✔️[Staging] SpellCheck succeeded [Detail] [Expand]
Validation passes for SpellCheck.
|
Thank you for your contribution alfeldsh! We will review the pull request and get back to you soon. |
Swagger Generation Artifacts
|
|
Hi @alfeldsh pls help loop some other swagger owner or guys familiar with the swagger to review approve it. |
|
Hi @zhenglaizhang, it seems that no one is assigned as an owner of /specification/securityinsights/ directory in the CODEOWNERS file. Do you know who can I assign as a reviewer? |
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.