azure-powershell
azure-powershell copied to clipboard
[SQL DB] Added parameters to enable Manual Cutover feature for Migration for azure sql Sterling database to azure sql hyperscale db
Description
Changes are done In order to support manual cutover for migration from azure sql sterling database to azure sql hyperscale databases through Powershell ,The changes include the following sub changes-
1- Authored Manaual Cutover/ Perform Cutover parameters to Set-AzSqlDatabase cmdlet , the changes were already part of 2023-02-01-preview/Databases API 2- Added OperationPhaseDetails parameter to Get-AzSqlDatabaseActivity cmdlet , the changes also include the version update of DatabaseOperations.json API from 2021-02-01-preview to 2022-11-01-preview within src/Sql/Sql.Management.Sdk/README.md file
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.)
- [x] General release
- [ ] Public preview
- [ ] Private preview
- [ ] Engineering build
- [ ] No need for a release
-
[ ] Check this box to confirm: I have read the Submitting Changes section of
CONTRIBUTING.md
and reviewed the following information:
-
SHOULD update
ChangeLog.md
file(s) appropriately- For SDK-based development mode, update
src/{{SERVICE}}/{{SERVICE}}/ChangeLog.md
.- A snippet outlining the change(s) made in the PR should be written under the
## Upcoming Release
header in the past tense.
- A snippet outlining the change(s) made in the PR should be written under the
- For autorest-based development mode, include the changelog in the PR description.
- Should not change
ChangeLog.md
if no new release is required, such as fixing test case only.
- For SDK-based development mode, update
- SHOULD regenerate markdown help files if there is cmdlet API change. Instruction
- SHOULD have proper test coverage for changes in pull request.
- SHOULD NOT adjust version of module manually in pull request
️✔️Az.Accounts
️✔️Build
️✔️PowerShell Core - Windows
️✔️Windows PowerShell - Windows
️✔️Az.Compute
️✔️Build
️✔️PowerShell Core - Windows
️✔️Windows PowerShell - Windows
️✔️Az.EventHub
️✔️Build
️✔️PowerShell Core - Windows
️✔️Windows PowerShell - Windows
️✔️Az.KeyVault
️✔️Build
️✔️PowerShell Core - Windows
️✔️Windows PowerShell - Windows
️✔️Az.ManagedServiceIdentity
️✔️Build
️✔️PowerShell Core - Windows
️✔️Windows PowerShell - Windows
️✔️Az.Monitor
️✔️Build
️✔️PowerShell Core - Windows
️✔️Windows PowerShell - Windows
️✔️Az.Network
️✔️Build
️✔️PowerShell Core - Windows
️✔️Windows PowerShell - Windows
️✔️Test
️✔️ - Linux
️✔️PowerShell Core - MacOS
️✔️PowerShell Core - Windows
️✔️Windows PowerShell - Windows
️✔️Az.OperationalInsights
️✔️Build
️✔️PowerShell Core - Windows
️✔️Windows PowerShell - Windows
️✔️Az.PrivateDns
️✔️Build
️✔️PowerShell Core - Windows
️✔️Windows PowerShell - Windows
⚠️Az.Sql
️✔️Build
️✔️PowerShell Core - Windows
️✔️Windows PowerShell - Windows
️✔️Breaking Change Check
️✔️PowerShell Core - Windows
️✔️Windows PowerShell - Windows
️✔️Signature Check
️✔️PowerShell Core - Windows
️✔️Windows PowerShell - Windows
️✔️Help Example Check
️✔️PowerShell Core - Windows
️✔️Windows PowerShell - Windows
️✔️Help File Existence Check
️✔️PowerShell Core - Windows
️✔️Windows PowerShell - Windows
️✔️File Change Check
️✔️PowerShell Core - Windows
️✔️Windows PowerShell - Windows
️✔️UX Metadata Check
️✔️PowerShell Core - Windows
️✔️Windows PowerShell - Windows
️✔️Generated Sdk Check
️✔️PowerShell Core - Windows
️✔️Windows PowerShell - Windows
⚠️Test
⚠️ - Linux
Type Title Current Coverage Last Coverage Description ⚠️ Test Coverage Less Than 80% 54.92 % 62.22% Test coverage cannot be lower than the number of the last release. ️✔️PowerShell Core - MacOS
️✔️PowerShell Core - Windows
️✔️Windows PowerShell - Windows
️✔️Az.Storage
️✔️Build
️✔️PowerShell Core - Windows
️✔️Windows PowerShell - Windows
Thank you for your contribution guptaayush007! We will review the pull request and get back to you soon.
Hi reviewers, @dingmeng-xue @vidai-msft @mykolian
1-getting azure-powershell - powershell-core Failing after 60m — Build #20240506.14 failed - failing due to following error -- 'West Europe' is not accepting creation of new Windows Azure SQL Database servers at this time
2- How to decide the milestone , for now i want my changes to get merge as early as possible and so have selected the very next milestone , not sure if i should not pick it since it mentions breaking changes with alert signals ?
/azp run
/azp run azure-powershell - security-tools
Azure Pipelines successfully started running 1 pipeline(s).
Hi @guptaayush007, please update the changelog.
This PR was labeled "needs-revision" because it has unresolved review comments or CI failures. Please resolve all open review comments and make sure all CI checks are green. Refer to our guide to troubleshoot common CI failures.
/azp run azure-powershell - security-tools
Azure Pipelines successfully started running 1 pipeline(s).
/azp run azure-powershell - security-tools
Commenter does not have sufficient privileges for PR 24796 in repo Azure/azure-powershell