-
Notifications
You must be signed in to change notification settings - Fork 5.1k
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
dev-Sentinel-2022-06-01-preview #19222
Merged
Merged
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
…w/2022-05-01-preview to version 2022-06-01-preview
…te connect body (#19074) * update connect body * update connect body * add example refernce Co-authored-by: Haim Rubinstein <harubins@microsoft.com>
Hi, @anat-gilenson 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
|
Rule | Message |
---|---|
R2018 - XmsEnumValidation |
The enum types should have x-ms-enum type extension set with appropriate options. Location: Microsoft.SecurityInsights/preview/2022-06-01-preview/EntityQueries.json#L484 |
R2018 - XmsEnumValidation |
The enum types should have x-ms-enum type extension set with appropriate options. Location: Microsoft.SecurityInsights/preview/2022-06-01-preview/EntityQueryTemplates.json#L292 |
R4041 - XmsIdentifierValidation |
Missing identifier id in array item property Location: Microsoft.SecurityInsights/preview/2022-06-01-preview/Bookmarks.json#L566 |
R4041 - XmsIdentifierValidation |
Missing identifier id in array item property Location: Microsoft.SecurityInsights/preview/2022-06-01-preview/EntityQueryTemplates.json#L234 |
R4041 - XmsIdentifierValidation |
Missing identifier id in array item property Location: Microsoft.SecurityInsights/preview/2022-06-01-preview/Incidents.json#L1020 |
R4041 - XmsIdentifierValidation |
Missing identifier id in array item property Location: Microsoft.SecurityInsights/preview/2022-06-01-preview/Incidents.json#L1119 |
R4041 - XmsIdentifierValidation |
Missing identifier id in array item property Location: Microsoft.SecurityInsights/preview/2022-06-01-preview/Metadata.json#L581 |
R4041 - XmsIdentifierValidation |
Missing identifier id in array item property Location: Microsoft.SecurityInsights/preview/2022-06-01-preview/operations.json#L83 |
Since operation 'Entities_Queries' response has model definition 'array', it should be of the form '_list'. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change. Location: Microsoft.SecurityInsights/preview/2022-06-01-preview/Entities.json#L291 |
|
Since operation 'Entities_GetInsights' response has model definition 'array', it should be of the form '_list'. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change. Location: Microsoft.SecurityInsights/preview/2022-06-01-preview/Entities.json#L339 |
|
Since operation 'ThreatIntelligenceIndicator_QueryIndicators' response has model definition 'x-ms-pageable', it should be of the form '_list'. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change. Location: Microsoft.SecurityInsights/preview/2022-06-01-preview/ThreatIntelligence.json#L296 |
|
'GET' operation 'Entities_Queries' should use method name 'Get' or Method name start with 'List'. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change. Location: Microsoft.SecurityInsights/preview/2022-06-01-preview/Entities.json#L291 |
|
'PUT' operation 'ProductSettings_Update' should use method name 'Create'. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change. Location: Microsoft.SecurityInsights/preview/2022-06-01-preview/Settings.json#L176 |
|
Consider using x-ms-client-flatten to provide a better end user experience Location: Microsoft.SecurityInsights/preview/2022-06-01-preview/Entities.json#L1114 |
|
Consider using x-ms-client-flatten to provide a better end user experience Location: Microsoft.SecurityInsights/preview/2022-06-01-preview/ThreatIntelligence.json#L1037 |
|
Based on the response model schema, operation 'Entities_Queries' might be pageable. Consider adding the x-ms-pageable extension. Location: Microsoft.SecurityInsights/preview/2022-06-01-preview/Entities.json#L281 |
|
Based on the response model schema, operation 'SentinelOnboardingStates_List' might be pageable. Consider adding the x-ms-pageable extension. Location: Microsoft.SecurityInsights/preview/2022-06-01-preview/OnboardingStates.json#L178 |
|
Based on the response model schema, operation 'ProductSettings_List' might be pageable. Consider adding the x-ms-pageable extension. Location: Microsoft.SecurityInsights/preview/2022-06-01-preview/Settings.json#L38 |
|
Based on the response model schema, operation 'ThreatIntelligenceIndicatorMetrics_List' might be pageable. Consider adding the x-ms-pageable extension. Location: Microsoft.SecurityInsights/preview/2022-06-01-preview/ThreatIntelligence.json#L334 |
|
OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'BookmarkModel'. Consider using the plural form of 'Bookmark' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change. Location: Microsoft.SecurityInsights/preview/2022-06-01-preview/Bookmarks.json#L291 |
|
OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'DataConnectorsCheckRequirementsModel'. Consider using the plural form of 'DataConnectorsCheckRequirements' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change. Location: Microsoft.SecurityInsights/preview/2022-06-01-preview/dataConnectors.json#L458 |
|
OperationId has a noun that conflicts with one of the model names in definitions section. The model name will be disambiguated to 'SourceControlModel'. Consider using the plural form of 'SourceControl' to avoid this. Note: If you have already shipped an SDK on top of this spec, fixing this warning may introduce a breaking change. Location: Microsoft.SecurityInsights/preview/2022-06-01-preview/SourceControls.json#L48 |
|
OperationId should contain the verb: 'dataconnectorscheckrequirements' in:'DataConnectorsCheckRequirements_Post'. Consider updating the operationId Location: Microsoft.SecurityInsights/preview/2022-06-01-preview/dataConnectors.json#L458 |
|
OperationId should contain the verb: 'gettimeline' in:'EntitiesGetTimeline_list'. Consider updating the operationId Location: Microsoft.SecurityInsights/preview/2022-06-01-preview/Entities.json#L243 |
|
The child tracked resource, 'relations' with immediate parent 'Bookmark', must have a list by immediate parent operation. Location: preview/2022-06-01-preview/common/RelationTypes.json#L30 |
|
The child tracked resource, 'relations' with immediate parent 'Entity', must have a list by immediate parent operation. Location: preview/2022-06-01-preview/common/RelationTypes.json#L30 |
|
The child tracked resource, 'relations' with immediate parent 'Incident', must have a list by immediate parent operation. Location: preview/2022-06-01-preview/common/RelationTypes.json#L30 |
|
The child tracked resource, 'comments' with immediate parent 'Incident', must have a list by immediate parent operation. Location: Microsoft.SecurityInsights/preview/2022-06-01-preview/Incidents.json#L942 |
|
The child tracked resource, 'watchlistItems' with immediate parent 'Watchlist', must have a list by immediate parent operation. Location: Microsoft.SecurityInsights/preview/2022-06-01-preview/Watchlists.json#L612 |
|
Guid used in model definition 'ManualTriggerRequestBody' for property 'tenantId'. 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/preview/2022-06-01-preview/AutomationRules.json#L1041 |
️️✔️
Avocado succeeded [Detail] [Expand]
Validation passes for Avocado.
️️✔️
ApiReadinessCheck succeeded [Detail] [Expand]
️️✔️
ModelValidation succeeded [Detail] [Expand]
Validation passes for ModelValidation.
️️✔️
SemanticValidation succeeded [Detail] [Expand]
Validation passes for SemanticValidation.
️⚠️
Cross-Version Breaking Changes: 7 Warnings warning [Detail]
- Compared Swaggers (Based on Oad v0.9.5)
- current:preview/2022-06-01-preview/AlertRules.json compared with base:stable/2021-10-01/AlertRules.json
- current:preview/2022-06-01-preview/AlertRules.json compared with base:preview/2022-05-01-preview/AlertRules.json
- current:preview/2022-06-01-preview/AutomationRules.json compared with base:stable/2021-10-01/AutomationRules.json
- current:preview/2022-06-01-preview/AutomationRules.json compared with base:preview/2022-05-01-preview/AutomationRules.json
- current:preview/2022-06-01-preview/Bookmarks.json compared with base:stable/2021-10-01/Bookmarks.json
- current:preview/2022-06-01-preview/Bookmarks.json compared with base:preview/2022-05-01-preview/Bookmarks.json
- current:preview/2022-06-01-preview/Enrichment.json compared with base:preview/2022-05-01-preview/Enrichment.json
- current:preview/2022-06-01-preview/Entities.json compared with base:preview/2022-05-01-preview/Entities.json
- current:preview/2022-06-01-preview/EntityQueries.json compared with base:preview/2022-05-01-preview/EntityQueries.json
- current:preview/2022-06-01-preview/EntityQueryTemplates.json compared with base:preview/2022-05-01-preview/EntityQueryTemplates.json
- current:preview/2022-06-01-preview/Incidents.json compared with base:stable/2021-10-01/Incidents.json
- current:preview/2022-06-01-preview/Incidents.json compared with base:preview/2022-05-01-preview/Incidents.json
- current:preview/2022-06-01-preview/Metadata.json compared with base:preview/2022-05-01-preview/Metadata.json
- current:preview/2022-06-01-preview/OfficeConsents.json compared with base:preview/2022-05-01-preview/OfficeConsents.json
- current:preview/2022-06-01-preview/OnboardingStates.json compared with base:stable/2021-10-01/OnboardingStates.json
- current:preview/2022-06-01-preview/OnboardingStates.json compared with base:preview/2022-05-01-preview/OnboardingStates.json
- current:preview/2022-06-01-preview/SecurityMLAnalyticsSettings.json compared with base:preview/2022-05-01-preview/SecurityMLAnalyticsSettings.json
- current:preview/2022-06-01-preview/Settings.json compared with base:preview/2022-05-01-preview/Settings.json
- current:preview/2022-06-01-preview/SourceControls.json compared with base:preview/2022-05-01-preview/SourceControls.json
- current:preview/2022-06-01-preview/ThreatIntelligence.json compared with base:stable/2021-10-01/ThreatIntelligence.json
- current:preview/2022-06-01-preview/ThreatIntelligence.json compared with base:preview/2022-05-01-preview/ThreatIntelligence.json
- current:preview/2022-06-01-preview/Watchlists.json compared with base:stable/2021-10-01/Watchlists.json
- current:preview/2022-06-01-preview/Watchlists.json compared with base:preview/2022-05-01-preview/Watchlists.json
- current:2022-06-01-preview/common/AlertTypes.json compared with base:2021-10-01/common/AlertTypes.json
- current:2022-06-01-preview/common/AlertTypes.json compared with base:2022-05-01-preview/common/AlertTypes.json
- current:2022-06-01-preview/common/EntityTypes.json compared with base:2021-10-01/common/EntityTypes.json
- current:2022-06-01-preview/common/EntityTypes.json compared with base:2022-05-01-preview/common/EntityTypes.json
- current:2022-06-01-preview/common/IncidentTypes.json compared with base:2021-10-01/common/IncidentTypes.json
- current:2022-06-01-preview/common/IncidentTypes.json compared with base:2022-05-01-preview/common/IncidentTypes.json
- current:2022-06-01-preview/common/RelationTypes.json compared with base:2022-05-01-preview/common/RelationTypes.json
- current:2022-06-01-preview/common/ThreatIntelligenceTypes.json compared with base:2022-05-01-preview/common/ThreatIntelligenceTypes.json
- current:preview/2022-06-01-preview/dataConnectors.json compared with base:preview/2022-05-01-preview/dataConnectors.json
- current:preview/2022-06-01-preview/operations.json compared with base:stable/2021-10-01/operations.json
- current:preview/2022-06-01-preview/operations.json compared with base:preview/2022-05-01-preview/operations.json
️️✔️
CredScan succeeded [Detail] [Expand]
There is no credential detected.
️❌
PoliCheck: 0 Errors, 0 Warnings failed [Detail]
️️✔️
SDK Track2 Validation succeeded [Detail] [Expand]
Validation passes for SDKTrack2Validation
- The following tags are being changed in this PR
️️✔️
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).
Swagger Generation Artifacts
|
This was referenced May 25, 2022
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
dw511214992
approved these changes
Jun 6, 2022
This was referenced Jun 6, 2022
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.
Please note all PRs to this branch have already been reviewed and approved by Swagger team and ARM. No need for addition ARM review.