Enhance Restore-AzMySqlFlexibleServer functionality with GeoRestore support #27729
+495
−39
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…upport - Updated documentation for Restore-AzMySqlFlexibleServer to include GeoRestore syntax and parameters. - Added new parameters for GeoRestore: -Location, -Sku, -Tag, and -UseGeoRestore. - Modified existing parameters to specify their applicability to PointInTimeRestore or GeoRestore. - Updated help files to reflect changes in command usage and examples. - Changed versioning in generate-info.json and updated Az.MySql.psd1 to require Az.Accounts version 4.2.0. - Refactored New-AzMySqlFlexibleServer and New-AzMySqlServer examples to use a sample password. - Created a new PowerShell script for GeoRestore functionality. - Added AssemblyInfo.cs for versioning and metadata. - Introduced README.md in resources directory for module organization.
| Thanks for your contribution! The pull request validation has started. Please revisit this comment for updated status. |
|
/azp run |
|
Azure Pipelines successfully started running 3 pipeline(s). |
|
Please update the |
|
This PR was labeled "needs-revision" because it has unresolved review comments or CI failures. |
…e-AzMySqlFlexibleServer
Thanks, changelog updated |
|
/azp run |
|
Azure Pipelines successfully started running 3 pipeline(s). |
wyunchi-ms
reviewed
May 15, 2025
Comment on lines
20
to
+24
| ## Upcoming Release | ||
|
|
||
| ## Version 1.3.1 | ||
| - Enhanced `Restore-AzMySqlFlexibleServer` functionality with GeoRestore support | ||
|
|
There was a problem hiding this comment.
Suggested change
| ## Upcoming Release | |
| ## Version 1.3.1 | |
| - Enhanced `Restore-AzMySqlFlexibleServer` functionality with GeoRestore support | |
| ## Upcoming Release | |
| - Enhanced `Restore-AzMySqlFlexibleServer` functionality with GeoRestore support | |
Not necessary to bump version manually. The tools will bump them up automaticlly during the release process.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.