Skip to content

Enhance Restore-AzMySqlFlexibleServer functionality with GeoRestore support #27729

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 4 commits into from
May 20, 2025

Conversation

ShawnXxy
Copy link
Contributor

@ShawnXxy ShawnXxy commented May 11, 2025

  • 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.

Description

Mandatory Checklist

  • SHOULD update ChangeLog.md file(s) appropriately
    • 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.
    • Should not change ChangeLog.md if no new release is required, such as fixing test case only.
  • 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

…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.
Copy link

Thanks for your contribution! The pull request validation has started. Please revisit this comment for updated status.

@wyunchi-ms
Copy link
Contributor

/azp run

Copy link
Contributor

Azure Pipelines successfully started running 3 pipeline(s).

@wyunchi-ms
Copy link
Contributor

Please update the src/{{SERVICE}}/{{SERVICE}}/ChangeLog.md

Copy link

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.

@ShawnXxy
Copy link
Contributor Author

Please update the src/{{SERVICE}}/{{SERVICE}}/ChangeLog.md

Thanks, changelog updated

@wyunchi-ms
Copy link
Contributor

/azp run

Copy link
Contributor

Azure Pipelines successfully started running 3 pipeline(s).

Co-authored-by: Yunchi Wang <54880216+wyunchi-ms@users.noreply.github.com>
@msJinLei
Copy link
Contributor

/azp run

Copy link
Contributor

Azure Pipelines successfully started running 3 pipeline(s).

@msJinLei
Copy link
Contributor

/azp run

Copy link
Contributor

Azure Pipelines successfully started running 3 pipeline(s).

@vidai-msft vidai-msft merged commit ab58e35 into Azure:main May 20, 2025
13 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants