Powershell: Publishing DMS APIs stable version #28453
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 publishes the stable API version 2025-06-30 for Azure Database Migration Service (DMS) APIs, replacing the preview version 2025-03-15-preview. It introduces new retry and delete operations for database migrations.
- Updates the API version from preview (2025-03-15-preview) to stable (2025-06-30)
- Adds new Retry API for Database Migration to SQL Database
- Introduces Delete APIs for SQL Database Migration and SQL VM Migration
Reviewed Changes
Copilot reviewed 26 out of 26 changed files in this pull request and generated 8 comments.
Show a summary per file
| File | Description |
|---|---|
| src/DataMigration/DataMigration.Autorest/readme.azure.noprofile.md | New AutoRest configuration file for generating PowerShell cmdlets |
| src/DataMigration/DataMigration.Autorest/test/*.Tests.ps1 | New test files for the retry and delete cmdlets with placeholder implementations |
| src/DataMigration/DataMigration.Autorest/examples/*.md | Example documentation files with placeholder content for new cmdlets |
| src/DataMigration/DataMigration.Autorest/docs/*.md | Updated documentation files with new API version references and new cmdlet documentation |
| src/DataMigration/DataMigration.Autorest/UX/*.json | Updated API version references and new UX metadata for retry operation |
Comments suppressed due to low confidence (2)
| ### Example 1: {{ Add title here }} | ||
| ```powershell | ||
| {{ Add code here }} | ||
| ``` | ||
|
|
||
| ```output | ||
| {{ Add output here }} | ||
| ``` | ||
|
|
||
| {{ Add description here }} | ||
|
|
||
| ### Example 2: {{ Add title here }} | ||
| ```powershell | ||
| {{ Add code here }} | ||
| ``` | ||
|
|
||
| ```output | ||
| {{ Add output here }} | ||
| ``` | ||
|
|
||
| {{ Add description here }} | ||
|
|
There was a problem hiding this comment.
The example documentation contains only placeholder content. Real examples should be provided showing how to use the Remove-AzDataMigrationToSqlVM cmdlet with actual parameter values and expected outputs.
| ### Example 1: {{ Add title here }} | |
| ```powershell | |
| {{ Add code here }} | |
| ``` | |
| ```output | |
| {{ Add output here }} | |
| ``` | |
| {{ Add description here }} | |
| ### Example 2: {{ Add title here }} | |
| ```powershell | |
| {{ Add code here }} | |
| ``` | |
| ```output | |
| {{ Add output here }} | |
| ``` | |
| {{ Add description here }} | |
| ### Example 1: Remove a Data Migration to SQL VM by Name | |
| ```powershell | |
| Remove-AzDataMigrationToSqlVM -ResourceGroupName "MyResourceGroup" -SqlVirtualMachineName "MySqlVM" -Name "MyMigration" |
True
This example removes the data migration named "MyMigration" from the SQL virtual machine "MySqlVM" in the resource group "MyResourceGroup". The command returns True if the operation succeeds.
Example 2: Remove a Data Migration to SQL VM using the Input Object
$migration = Get-AzDataMigrationToSqlVM -ResourceGroupName "MyResourceGroup" -SqlVirtualMachineName "MySqlVM" -Name "MyMigration"
Remove-AzDataMigrationToSqlVM -InputObject $migrationTrue
This example retrieves the data migration object and then removes it using the -InputObject parameter. This is useful when you want to pipe or work with objects directly.
Copilot uses AI. Check for mistakes.
amarjeetkr
changed the title
|
/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. |
|
/azp run |
|
Azure Pipelines successfully started running 3 pipeline(s). |
| @@ -0,0 +1,47 @@ | |||
| # Azure PowerShell AutoRest Configuration | |||
There was a problem hiding this comment.
please do not add this file
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.