Enhance Get-AzMigrateServerMigrationStatus cmdlet to support -Expedit… #28529
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
…e parameter - Added new parameter -Expedite to expedite the operation of a replicating server. - Updated documentation to include usage examples for the -Expedite parameter. - Modified existing examples to reflect new project and resource group names. - Enhanced output formatting in examples to provide clearer information. - Added tests for the new -Expedite functionality. - Updated ChangeLog to document the addition of the -Expedite feature.
| Thanks for your contribution! The pull request validation has started. Please revisit this comment for updated status. |
|
Thank you for your contribution @ankitbaluni123! We will review the pull request and get back to you soon. |
There was a problem hiding this comment.
Pull Request Overview
This PR enhances the Get-AzMigrateServerMigrationStatus cmdlet by adding a new -Expedite parameter that provides detailed resource utilization analysis and recommendations for optimizing server migration performance. The enhancement allows users to identify bottlenecks and receive actionable suggestions to speed up migration operations.
Key Changes
- Added new
-Expediteparameter with dedicated parameter setGetByPrioritiseServer - Implemented comprehensive resource sharing analysis showing VMs that share appliances, ESXi hosts, or datastores
- Enhanced resource utilization reporting with status calculations and specific optimization recommendations
- Updated documentation with new examples and parameter descriptions
Reviewed Changes
Copilot reviewed 6 out of 6 changed files in this pull request and generated 3 comments.
Show a summary per file
| File | Description |
|---|---|
src/Migrate/Migrate/help/Get-AzMigrateServerMigrationStatus.md |
Updated help documentation with new parameter set syntax and comprehensive example for expedite functionality |
src/Migrate/Migrate/ChangeLog.md |
Added changelog entry documenting the new -Expedite parameter support |
src/Migrate/Migrate.Autorest/test/Get-AzMigrateServerMigrationStatus.Tests.ps1 |
Added placeholder test case for the new GetByPrioritiseServer parameter set |
src/Migrate/Migrate.Autorest/examples/Get-AzMigrateServerMigrationStatus.md |
Updated examples with new project/resource group names and added detailed expedite example |
src/Migrate/Migrate.Autorest/docs/Get-AzMigrateServerMigrationStatus.md |
Updated API documentation with new parameter syntax and examples |
src/Migrate/Migrate.Autorest/custom/Get-AzMigrateServerMigrationStatus.ps1 |
Implemented core expedite functionality with resource analysis, status calculations, and recommendation logic |
src/Migrate/Migrate.Autorest/custom/Get-AzMigrateServerMigrationStatus.ps1
Show resolved
Hide resolved
src/Migrate/Migrate.Autorest/custom/Get-AzMigrateServerMigrationStatus.ps1
Show resolved
Hide resolved
src/Migrate/Migrate.Autorest/custom/Get-AzMigrateServerMigrationStatus.ps1
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.
…e parameter
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.