[DataMigration] SDK generation for stable API version 2025-06-30 #52227
Conversation
amarjeetkr
requested review from
ArcturusZhang,
ArthurMa1978,
jsquire and
a team
as code owners
There was a problem hiding this comment.
Pull Request Overview
This PR publishes a stable API version 2025-06-30 for Azure Data Migration Service (DMS) APIs, transitioning from beta to stable release. The changes introduce new API operations for database migration management and add support for deletion and retry operations.
Key changes:
- Release of stable version 1.0.0 for API version 2025-06-30
- Added three new operations: Retry API for Database Migration, Delete API for SQL Database Migration, and Delete API for SQL VM Migration
- Introduction of new project configuration for SQL Migration Management Client
Reviewed Changes
Copilot reviewed 2 out of 21 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| CHANGELOG.md | Documents the stable release 1.0.0 with new API operations and version support |
| SqlMigrationManagementClient.csproj | New project file configuration for SQL Migration Management Client with dependencies |
amarjeetkr
force-pushed
the
amakum/stable-dmsapi-sdk-upgrade
branch
from
a1d3fa2 to
9d40a3e
Compare
|
@jsquire |
jsquire
dismissed
their stale review
Confirmed that non-library files have been revereted.
|
@ArthurMa1978 |
There was a problem hiding this comment.
It seems the code changes weren’t generated from the spec, as there’s no update to the autorest.md file indicating a new spec version. Since the mgmt. plane SDK is generated from the Swagger spec, please follow the doc to update the SDK accordingly.
Contributing to the Azure SDK
Published the stable API version 2025-06-30 for DMS APIs.
Added Retry API for Database Migration.
Introduced Delete API for SQL Database Migration.
Introduced Delete API for SQL VM Migration.
Please see our CONTRIBUTING.md if you are not familiar with contributing to this repository or have questions.
For specific information about pull request etiquette and best practices, see this section.