Conversation
| 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 Azure ResourceMover PowerShell module from AutoRest v3 to AutoRest v4. The migration involves updating model type namespaces, correcting parameter types, adding new parameter sets, and resolving breaking changes in the generated code.
Key Changes
- Updated model type namespaces from
Microsoft.Azure.PowerShell.Cmdlets.ResourceMover.Models.Api20230801toMicrosoft.Azure.PowerShell.Cmdlets.ResourceMover.Models - Replaced strongly-typed enum parameters with string parameters for flexibility
- Added new parameter sets and JSON-based input methods for various cmdlets
Reviewed Changes
Copilot reviewed 79 out of 79 changed files in this pull request and generated 4 comments.
Show a summary per file
| File | Description |
|---|---|
| tools/StaticAnalysis/Exceptions/Az.ResourceMover/BreakingChangeIssues.csv | Documents breaking changes and exceptions for the v4 migration |
| src/ResourceMover/ResourceMover/help/*.md | Updates help documentation with corrected type names and parameter sets |
| src/ResourceMover/ResourceMover.Autorest/test/*.ps1 | Updates test files to use new parameter syntax |
| src/ResourceMover/ResourceMover.Autorest/examples/*.md | Updates example documentation with corrected type references |
| src/ResourceMover/ResourceMover.Autorest/custom/csharp/*.cs | Updates C# custom code with new model namespaces |
| ## EXAMPLES | ||
|
|
||
| ### Example 1: Validate the dependenciesss before remove of the Move Resources from Move Collection | ||
| ### Example 1: Validate the dependecies before remove of the Move Resources from Move Collection |
There was a problem hiding this comment.
There is a spelling error in 'dependecies'. It should be 'dependencies'.
| ### Example 1: Validate the dependecies before remove of the Move Resources from Move Collection | |
| ### Example 1: Validate the dependencies before remove of the Move Resources from Move Collection |
| ``` | ||
|
|
||
| Validate the dependencies before remove of the move resources from Move Collection. | ||
| Validate the dependecies before remove of the move resources from Move Collection. |
There was a problem hiding this comment.
There is a spelling error in 'dependecies'. It should be 'dependencies'.
| Validate the dependecies before remove of the move resources from Move Collection. | |
| Validate the dependencies before remove of the move resources from Move Collection. |
| ## EXAMPLES | ||
|
|
||
| ### Example 1: Validate the dependencies before remove of the Move Resources from Move Collection | ||
| ### Example 1: Validate the dependecies before remove of the Move Resources from Move Collection |
There was a problem hiding this comment.
There is a spelling error in 'dependecies'. It should be 'dependencies'.
| ### Example 1: Validate the dependecies before remove of the Move Resources from Move Collection | |
| ### Example 1: Validate the dependencies before remove of the Move Resources from Move Collection |
| ``` | ||
|
|
||
| Validate the dependencies before remove of the move resources from Move Collection. | ||
| Validate the dependecies before remove of the move resources from Move Collection. |
There was a problem hiding this comment.
There is a spelling error in 'dependecies'. It should be 'dependencies'.
| Validate the dependecies before remove of the move resources from Move Collection. | |
| Validate the dependencies before remove of the move resources from Move Collection. |
|
To the author of the pull request, |
|
/azp run |
|
Azure Pipelines will not run the associated pipelines, because the pull request was updated after the run command was issued. Review the pull request again and issue a new run command. |
…ourceMover-to-autorest-v4
Description
Preannouncement PR:
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.