Added SQL DB Retry, SQLVM Delete and SQLMI Delete commands

[amarjeetkr]

---

Released the first stable version with three new commands.

• [NEW COMMAND] az data-migration sql-db retry - Retry on going migration for the database.
• [NEW COMMAND] data-migration sql-managed-instance delete - Delete SQL MI Database Migration resource.
• [NEW COMMAND] data-migration sql-vm delete - Delete SQL VM Database Migration resource.

Related command

• az datamigration get-assessment
• az datamigration performance-data-collection
• az datamigration get-sku-recommendation
• az datamigration tde-migration

General Guidelines

• Have you run azdev style <YOUR_EXT> locally? (pip install azdev required)
• Have you run python scripts/ci/test_index.py -q locally? (pip install wheel==0.30.0 required)
• My extension version conforms to the Extension version schema

For new extensions:

• My extension description/summary conforms to the Extension Summary Guidelines.

About Extension Publish

There is a pipeline to automatically build, upload and publish extension wheels.
Once your pull request is merged into main branch, a new pull request will be created to update src/index.json automatically.
You only need to update the version information in file setup.py and historical information in file HISTORY.rst in your PR but do not modify src/index.json.

[azure-client-tools-bot-prd]

⚠️Azure CLI Extensions Breaking Change Test

⚠️datamigration

rule	cmd_name	rule_message	suggest_message
⚠️ 1011 - SubgroupAdd	data-migration	sub group data-migration added

[azure-client-tools-bot-prd]

Hi @amarjeetkr,
Please write the description of changes which can be perceived by customers into HISTORY.rst.
If you want to release a new extension version, please update the version in setup.py as well.

[yonzhan]

Thank you for your contribution! We will review the pull request and get back to you soon.

[github-actions]

The git hooks are available for azure-cli and azure-cli-extensions repos. They could help you run required checks before creating the PR.

Please sync the latest code with latest dev branch (for azure-cli) or main branch (for azure-cli-extensions).
After that please run the following commands to enable git hooks:

pip install azdev --upgrade
azdev setup -c <your azure-cli repo path> -r <your azure-cli-extensions repo path>

[Copilot]

Pull Request Overview

This PR adds new Data Migration commands for Azure CLI including SQL DB retry, SQL VM delete, and SQL Managed Instance delete operations. The changes also update the minimum CLI core version requirement to support the new functionality.

• Adds retry command for SQL Database migration operations
• Adds delete commands for SQL VM and SQL Managed Instance database migrations
• Updates minimum CLI core version to 2.75.0

Reviewed Changes

Copilot reviewed 15 out of 15 changed files in this pull request and generated 1 comment.

File	Description
azext_metadata.json	Updates minimum CLI core version from 2.15.0 to 2.75.0
aaz/ directory	Adds new AAZ-generated command modules for data migration operations
__init__.py	Integrates AAZ command loading into the extension

[Copilot]

The example description is incorrect. It says 'Create or Update' but this is a delete command. Should be 'Delete Database Migration resource with Minimum parameters.'

Suggested change

	:example: Create or Update Database Migration resource with Minimum parameters.
	:example: Delete Database Migration resource with Minimum parameters.

[github-actions]

CodeGen Tools Feedback Collection

Thank you for using our CodeGen tool. We value your feedback, and we would like to know how we can improve our product. Please take a few minutes to fill our codegen survey

[github-actions]

Hi @amarjeetkr

⚠️ Release Requirements

Module: datamigration

• ⚠️ Please update VERSION to be 1.0.0b7 in src/datamigration/setup.py
• ⚠️ Set azext.isPreview to true in azext_metadata.json for datamigration

Notes

• For more info about extension versioning, please refer to Extension version schema

[necusjz]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 2 pipeline(s).