[DMS] Merging pg mysql from extension into core#15746
Conversation
|
DataMigration |
|
@yonzhan This is now ready for review. Please let me know if there are any questions or concerns. |
|
@evelyn-ys will help you with this PR. |
|
This pr may need more approvals. @Juliehzl Could you help review? |
|
I am not the code owner. My approval is not useful. Please add codeowner in .github and then this PR could be merged. |
|
|
||
| class ScenarioType(Enum): | ||
|
|
||
| def create_sql_connection_info(connection_info_json, prompt_prefix): |
There was a problem hiding this comment.
This was refactored into custom.create_connection.
|
Hi @temandr, may I know which extension is used for these commands previously? We may need to suppress the extension usage after migration. |
https://github.com/Azure/azure-cli-extensions/tree/master/src/dms-preview |
|
@msyyc as you are the code owner, we need your approval to merge the PR. |
Description
Testing Guide
No new tests added. Modified existing tests to test the scenario inputs for the MySQL and PostgreSQL scenarios.
History Notes
[DMS] BREAKING CHANGE: az dms project task create: Added mandatory task type parameter to help distinguish if a scenario is an online migration or an offline migration.
[DMS] az dms project task cutover: add new command which allows tasks with an online migration task type to cutover and end the migration.
[DMS] az dms project create/az dms project task create: Enable MySQL and PostgreSQL projects/tasks to be created.
This checklist is used to make sure that common guidelines for a pull request are followed.
The PR title and description has followed the guideline in Submitting Pull Requests.
I adhere to the Command Guidelines.