[PS] Migrate SecurityInsights module to autorest v4 #28447
Conversation
This file contains hidden or 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
| Thanks for your contribution! The pull request validation has started. Please revisit this comment for updated status. |
There was a problem hiding this comment.
Pull Request Overview
This PR migrates the SecurityInsights module from AutoRest v3 to v4, updating API models and cmdlet structure. The migration involves significant changes to parameter types, output types, and method signatures to align with the newer AutoRest framework.
Key Changes
- Type simplification from strongly-typed enums to string parameters for improved flexibility
- Output type namespace updates from versioned API models to unversioned ones
- Addition of new parameter sets and JSON-based input methods for cmdlets
Reviewed Changes
Copilot reviewed 150 out of 151 changed files in this pull request and generated 3 comments.
| File | Description |
|---|---|
tools/StaticAnalysis/Exceptions/Az.SecurityInsights/BreakingChangeIssues.csv |
Documents expected breaking changes from the AutoRest v4 migration |
| Multiple help markdown files | Updated parameter types, output types, and documentation to reflect API changes |
tools/StaticAnalysis/Exceptions/Az.SecurityInsights/BreakingChangeIssues.csv
Show resolved
Hide resolved
src/SecurityInsights/SecurityInsights/help/New-AzSentinelAlertRule.md
Outdated
Show resolved
Hide resolved
src/SecurityInsights/SecurityInsights/help/New-AzSentinelIncidentTeam.md
Outdated
Show resolved
Hide resolved
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.
Description
Mandatory Checklist
Please choose the target release of Azure PowerShell. (⚠️ Target release is a different concept from API readiness. Please click below links for details.)
Check this box to confirm: I have read the Submitting Changes section of
CONTRIBUTING.mdand reviewed the following information:ChangeLog.mdfile(s) appropriatelysrc/{{SERVICE}}/{{SERVICE}}/ChangeLog.md.## Upcoming Releaseheader in the past tense.ChangeLog.mdif no new release is required, such as fixing test case only.