Skip to content

[BC]MySQL Update Release Date to May 2026 #29120

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.

Sign up for GitHub

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

Open
JiaSeng-v wants to merge 1 commit into
base: main
Choose a base branch
from
Open

[BC]MySQL Update Release Date to May 2026 #29120

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions src/MySql/MySql.Autorest/Properties/AssemblyInfo.cs
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -20,7 +20,7 @@
[assembly: System.Reflection.AssemblyCopyrightAttribute("Copyright © Microsoft")]
[assembly: System.Reflection.AssemblyProductAttribute("Microsoft Azure PowerShell")]
[assembly: System.Reflection.AssemblyTitleAttribute("Microsoft Azure PowerShell - MySql")]
[assembly: System.Reflection.AssemblyFileVersionAttribute("1.5.0")]
[assembly: System.Reflection.AssemblyVersionAttribute("1.5.0")]
[assembly: System.Reflection.AssemblyFileVersionAttribute("1.5.1")]
[assembly: System.Reflection.AssemblyVersionAttribute("1.5.1")]
[assembly: System.Runtime.InteropServices.ComVisibleAttribute(false)]
[assembly: System.CLSCompliantAttribute(false)]
2 changes: 1 addition & 1 deletion src/MySql/MySql.Autorest/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -276,7 +276,7 @@ directive:
subject: ^FlexibleServer
set:
preview-announcement:
preview-message: "*****************************************************************************************\\r\\n* This cmdlet will undergo a breaking change in Az v15.0.0, to be released in May 2026. *\\r\\n* At least one change applies to this cmdlet. *\\r\\n* See all possible breaking changes at https://go.microsoft.com/fwlink/?linkid=2333486 *\\r\\n**************************************************************************************************"
preview-message: "*****************************************************************************************\\r\\n* This cmdlet will undergo a breaking change in Az v16.0.0, to be released in May 2026. *\\r\\n* At least one change applies to this cmdlet. *\\r\\n* See all possible breaking changes at https://go.microsoft.com/fwlink/?linkid=2333486 *\\r\\n**************************************************************************************************"
- where:
verb: Get|New|Update|Remove|Restart|Restore
subject: ^Configuration$|^FirewallRule$|^Replica$|^Server$|^VirtualNetworkRule$|ServerConfigurationsList
Expand Down
2 changes: 1 addition & 1 deletion src/MySql/MySql.Autorest/custom/Get-AzMySqlFlexibleServerConnectionString.ps1
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -23,7 +23,7 @@ function Get-AzMySqlFlexibleServerConnectionString {
[OutputType([System.String])]
[CmdletBinding(DefaultParameterSetName='Get', PositionalBinding=$false)]
[Microsoft.Azure.PowerShell.Cmdlets.MySql.Runtime.PreviewMessage("**********************************************************************************************`n
* This cmdlet will undergo a breaking change in Az v16.0.0, to be released on November 19th 2025. *`n
* This cmdlet will undergo a breaking change in Az v16.0.0, to be released on May 2026. *`n
Copy link

Copilot AI Jan 30, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Inconsistent date format: The message uses "to be released on May 2026" but the README.md directive uses "to be released in May 2026". The preposition should be consistent across all files. Since the original format was "November 19th 2025" with a specific day, using "on" with just a month creates grammatical awkwardness. Consider using "in May 2026" to match the README.md, or provide a specific date like "on May 1st 2026".

Suggested change
* This cmdlet will undergo a breaking change in Az v16.0.0, to be released on May 2026. *`n
* This cmdlet will undergo a breaking change in Az v16.0.0, to be released in May 2026. *`n

Copilot uses AI. Check for mistakes.
* At least one change applies to this cmdlet. *`n
* See all possible breaking changes at https://go.microsoft.com/fwlink/?linkid=2333486 *`n
***************************************************************************************************")]
Expand Down
2 changes: 1 addition & 1 deletion src/MySql/MySql.Autorest/custom/Get-AzMySqlFlexibleServerLocationBasedCapability.ps1
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -23,7 +23,7 @@ function Get-AzMySqlFlexibleServerLocationBasedCapability {
[OutputType([Microsoft.Azure.PowerShell.Cmdlets.MySql.Models.Api20210501.ICapabilityProperties])]
[CmdletBinding(DefaultParameterSetName='List', PositionalBinding=$false)]
[Microsoft.Azure.PowerShell.Cmdlets.MySql.Runtime.PreviewMessage("**********************************************************************************************`n
* This cmdlet will undergo a breaking change in Az v16.0.0, to be released on November 19th 2025. *`n
* This cmdlet will undergo a breaking change in Az v16.0.0, to be released on May 2026. *`n
Copy link

Copilot AI Jan 30, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Inconsistent date format: The message uses "to be released on May 2026" but the README.md directive uses "to be released in May 2026". The preposition should be consistent across all files. Since the original format was "November 19th 2025" with a specific day, using "on" with just a month creates grammatical awkwardness. Consider using "in May 2026" to match the README.md, or provide a specific date like "on May 1st 2026".

Suggested change
* This cmdlet will undergo a breaking change in Az v16.0.0, to be released on May 2026. *`n
* This cmdlet will undergo a breaking change in Az v16.0.0, to be released in May 2026. *`n

Copilot uses AI. Check for mistakes.
* At least one change applies to this cmdlet. *`n
* See all possible breaking changes at https://go.microsoft.com/fwlink/?linkid=2333486 *`n
***************************************************************************************************")]
Expand Down
2 changes: 1 addition & 1 deletion src/MySql/MySql.Autorest/custom/New-AzMySqlFlexibleServer.ps1
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -31,7 +31,7 @@ function New-AzMySqlFlexibleServer {
[CmdletBinding(DefaultParameterSetName='CreateExpanded', PositionalBinding=$false, SupportsShouldProcess, ConfirmImpact='Medium')]
[Microsoft.Azure.PowerShell.Cmdlets.MySql.Description('Creates a new MySQL flexible server.')]
[Microsoft.Azure.PowerShell.Cmdlets.MySql.Runtime.PreviewMessage("**********************************************************************************************`n
* This cmdlet will undergo a breaking change in Az v16.0.0, to be released on November 19th 2025. *`n
* This cmdlet will undergo a breaking change in Az v16.0.0, to be released on May 2026. *`n
Copy link

Copilot AI Jan 30, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Inconsistent date format: The message uses "to be released on May 2026" but the README.md directive uses "to be released in May 2026". The preposition should be consistent across all files. Since the original format was "November 19th 2025" with a specific day, using "on" with just a month creates grammatical awkwardness. Consider using "in May 2026" to match the README.md, or provide a specific date like "on May 1st 2026".

Suggested change
* This cmdlet will undergo a breaking change in Az v16.0.0, to be released on May 2026. *`n
* This cmdlet will undergo a breaking change in Az v16.0.0, to be released in May 2026. *`n

Copilot uses AI. Check for mistakes.
* At least one change applies to this cmdlet. *`n
* See all possible breaking changes at https://go.microsoft.com/fwlink/?linkid=2333486 *`n
***************************************************************************************************")]
Expand Down
2 changes: 1 addition & 1 deletion src/MySql/MySql.Autorest/custom/New-AzMySqlFlexibleServerFirewallRule.ps1
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -24,7 +24,7 @@ function New-AzMySqlFlexibleServerFirewallRule {
[OutputType([Microsoft.Azure.PowerShell.Cmdlets.MySql.Models.Api20171201.IFirewallRule])]
[CmdletBinding(DefaultParameterSetName='CreateExpanded', PositionalBinding=$false, SupportsShouldProcess, ConfirmImpact='Medium')]
[Microsoft.Azure.PowerShell.Cmdlets.MySql.Runtime.PreviewMessage("**********************************************************************************************`n
* This cmdlet will undergo a breaking change in Az v16.0.0, to be released on November 19th 2025. *`n
* This cmdlet will undergo a breaking change in Az v16.0.0, to be released on May 2026. *`n
Copy link

Copilot AI Jan 30, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Inconsistent date format: The message uses "to be released on May 2026" but the README.md directive uses "to be released in May 2026". The preposition should be consistent across all files. Since the original format was "November 19th 2025" with a specific day, using "on" with just a month creates grammatical awkwardness. Consider using "in May 2026" to match the README.md, or provide a specific date like "on May 1st 2026".

Suggested change
* This cmdlet will undergo a breaking change in Az v16.0.0, to be released on May 2026. *`n
* This cmdlet will undergo a breaking change in Az v16.0.0, to be released in May 2026. *`n

Copilot uses AI. Check for mistakes.
* At least one change applies to this cmdlet. *`n
* See all possible breaking changes at https://go.microsoft.com/fwlink/?linkid=2333486 *`n
***************************************************************************************************")]
Expand Down
2 changes: 1 addition & 1 deletion src/MySql/MySql.Autorest/custom/New-AzMySqlFlexibleServerReplica.ps1
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -25,7 +25,7 @@ function New-AzMySqlFlexibleServerReplica {
[CmdletBinding(DefaultParameterSetName='CreateExpanded', PositionalBinding=$false, SupportsShouldProcess, ConfirmImpact='Medium')]
[Microsoft.Azure.PowerShell.Cmdlets.MySql.Description('Creates a new replica from an existing database.')]
[Microsoft.Azure.PowerShell.Cmdlets.MySql.Runtime.PreviewMessage("**********************************************************************************************`n
* This cmdlet will undergo a breaking change in Az v16.0.0, to be released on November 19th 2025. *`n
* This cmdlet will undergo a breaking change in Az v16.0.0, to be released on May 2026. *`n
Copy link

Copilot AI Jan 30, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Inconsistent date format: The message uses "to be released on May 2026" but the README.md directive uses "to be released in May 2026". The preposition should be consistent across all files. Since the original format was "November 19th 2025" with a specific day, using "on" with just a month creates grammatical awkwardness. Consider using "in May 2026" to match the README.md, or provide a specific date like "on May 1st 2026".

Suggested change
* This cmdlet will undergo a breaking change in Az v16.0.0, to be released on May 2026. *`n
* This cmdlet will undergo a breaking change in Az v16.0.0, to be released in May 2026. *`n

Copilot uses AI. Check for mistakes.
* At least one change applies to this cmdlet. *`n
* See all possible breaking changes at https://go.microsoft.com/fwlink/?linkid=2333486 *`n
***************************************************************************************************")]
Expand Down
2 changes: 1 addition & 1 deletion src/MySql/MySql.Autorest/custom/Restore-AzMySqlFlexibleServer_GeoRestore.ps1
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -17,7 +17,7 @@ function Restore-AzMySqlFlexibleServer_GeoRestore {
[CmdletBinding(PositionalBinding = $false, SupportsShouldProcess, ConfirmImpact = 'Medium')]
[Microsoft.Azure.PowerShell.Cmdlets.MySql.Description('Restore a server from an existing backup using GeoRestore')]
[Microsoft.Azure.PowerShell.Cmdlets.MySql.Runtime.PreviewMessage("**********************************************************************************************`n
* This cmdlet will undergo a breaking change in Az v16.0.0, to be released on November 19th 2025. *`n
* This cmdlet will undergo a breaking change in Az v16.0.0, to be released on May 2026. *`n
Copy link

Copilot AI Jan 30, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Inconsistent date format: The message uses "to be released on May 2026" but the README.md directive uses "to be released in May 2026". The preposition should be consistent across all files. Since the original format was "November 19th 2025" with a specific day, using "on" with just a month creates grammatical awkwardness. Consider using "in May 2026" to match the README.md, or provide a specific date like "on May 1st 2026".

Suggested change
* This cmdlet will undergo a breaking change in Az v16.0.0, to be released on May 2026. *`n
* This cmdlet will undergo a breaking change in Az v16.0.0, to be released in May 2026. *`n

Copilot uses AI. Check for mistakes.
* At least one change applies to this cmdlet. *`n
* See all possible breaking changes at https://go.microsoft.com/fwlink/?linkid=2333486 *`n
***************************************************************************************************")]
Expand Down
2 changes: 1 addition & 1 deletion src/MySql/MySql.Autorest/custom/Restore-AzMySqlFlexibleServer_PointInTimeRestore.ps1
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -18,7 +18,7 @@ function Restore-AzMySqlFlexibleServer_PointInTimeRestore {
[CmdletBinding(PositionalBinding=$false, SupportsShouldProcess, ConfirmImpact='Medium')]
[Microsoft.Azure.PowerShell.Cmdlets.MySql.Description('Restore a server from an existing backup')]
[Microsoft.Azure.PowerShell.Cmdlets.MySql.Runtime.PreviewMessage("**********************************************************************************************`n
* This cmdlet will undergo a breaking change in Az v16.0.0, to be released on November 19th 2025. *`n
* This cmdlet will undergo a breaking change in Az v16.0.0, to be released on May 2026. *`n
Copy link

Copilot AI Jan 30, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Inconsistent date format: The message uses "to be released on May 2026" but the README.md directive uses "to be released in May 2026". The preposition should be consistent across all files. Since the original format was "November 19th 2025" with a specific day, using "on" with just a month creates grammatical awkwardness. Consider using "in May 2026" to match the README.md, or provide a specific date like "on May 1st 2026".

Suggested change
* This cmdlet will undergo a breaking change in Az v16.0.0, to be released on May 2026. *`n
* This cmdlet will undergo a breaking change in Az v16.0.0, to be released in May 2026. *`n

Copilot uses AI. Check for mistakes.
* At least one change applies to this cmdlet. *`n
* See all possible breaking changes at https://go.microsoft.com/fwlink/?linkid=2333486 *`n
***************************************************************************************************")]
Expand Down
2 changes: 1 addition & 1 deletion src/MySql/MySql.Autorest/custom/Test-AzMySqlFlexibleServerConnect.ps1
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -17,7 +17,7 @@ function Test-AzMySqlFlexibleServerConnect {
[CmdletBinding(DefaultParameterSetName = 'Test', PositionalBinding = $false)]
[Microsoft.Azure.PowerShell.Cmdlets.MySql.Description('Test out the connection to the database server')]
[Microsoft.Azure.PowerShell.Cmdlets.MySql.Runtime.PreviewMessage("**********************************************************************************************`n
* This cmdlet will undergo a breaking change in Az v16.0.0, to be released on November 19th 2025. *`n
* This cmdlet will undergo a breaking change in Az v16.0.0, to be released on May 2026. *`n
Copy link

Copilot AI Jan 30, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Inconsistent date format: The message uses "to be released on May 2026" but the README.md directive uses "to be released in May 2026". The preposition should be consistent across all files. Since the original format was "November 19th 2025" with a specific day, using "on" with just a month creates grammatical awkwardness. Consider using "in May 2026" to match the README.md, or provide a specific date like "on May 1st 2026".

Suggested change
* This cmdlet will undergo a breaking change in Az v16.0.0, to be released on May 2026. *`n
* This cmdlet will undergo a breaking change in Az v16.0.0, to be released in May 2026. *`n

Copilot uses AI. Check for mistakes.
* At least one change applies to this cmdlet. *`n
* See all possible breaking changes at https://go.microsoft.com/fwlink/?linkid=2333486 *`n
***************************************************************************************************")]
Expand Down
2 changes: 1 addition & 1 deletion src/MySql/MySql.Autorest/custom/Update-AzMySqlFlexibleServer.ps1
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -24,7 +24,7 @@ function Update-AzMySqlFlexibleServer {
[OutputType([Microsoft.Azure.PowerShell.Cmdlets.MySql.Models.Api20210501.IServerAutoGenerated])]
[CmdletBinding(DefaultParameterSetName='UpdateExpanded', PositionalBinding=$false, SupportsShouldProcess, ConfirmImpact='Medium')]
[Microsoft.Azure.PowerShell.Cmdlets.MySql.Runtime.PreviewMessage("**********************************************************************************************`n
* This cmdlet will undergo a breaking change in Az v16.0.0, to be released on November 19th 2025. *`n
* This cmdlet will undergo a breaking change in Az v16.0.0, to be released on May 2026. *`n
Copy link

Copilot AI Jan 30, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Inconsistent date format: The message uses "to be released on May 2026" but the README.md directive uses "to be released in May 2026". The preposition should be consistent across all files. Since the original format was "November 19th 2025" with a specific day, using "on" with just a month creates grammatical awkwardness. Consider using "in May 2026" to match the README.md, or provide a specific date like "on May 1st 2026".

Suggested change
* This cmdlet will undergo a breaking change in Az v16.0.0, to be released on May 2026. *`n
* This cmdlet will undergo a breaking change in Az v16.0.0, to be released in May 2026. *`n

Copilot uses AI. Check for mistakes.
* At least one change applies to this cmdlet. *`n
* See all possible breaking changes at https://go.microsoft.com/fwlink/?linkid=2333486 *`n
***************************************************************************************************")]
Expand Down
2 changes: 1 addition & 1 deletion src/MySql/MySql.Autorest/custom/Update-AzMySqlFlexibleServerConfiguration.ps1
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -24,7 +24,7 @@ function Update-AzMySqlFlexibleServerConfiguration {
[OutputType([Microsoft.Azure.PowerShell.Cmdlets.MySql.Models.Api20210501.IConfigurationAutoGenerated])]
[CmdletBinding(DefaultParameterSetName='UpdateExpanded', PositionalBinding=$false, SupportsShouldProcess, ConfirmImpact='Medium')]
[Microsoft.Azure.PowerShell.Cmdlets.MySql.Runtime.PreviewMessage("**********************************************************************************************`n
* This cmdlet will undergo a breaking change in Az v16.0.0, to be released on November 19th 2025. *`n
* This cmdlet will undergo a breaking change in Az v16.0.0, to be released on May 2026. *`n
Copy link

Copilot AI Jan 30, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Inconsistent date format: The message uses "to be released on May 2026" but the README.md directive uses "to be released in May 2026". The preposition should be consistent across all files. Since the original format was "November 19th 2025" with a specific day, using "on" with just a month creates grammatical awkwardness. Consider using "in May 2026" to match the README.md, or provide a specific date like "on May 1st 2026".

Suggested change
* This cmdlet will undergo a breaking change in Az v16.0.0, to be released on May 2026. *`n
* This cmdlet will undergo a breaking change in Az v16.0.0, to be released in May 2026. *`n

Copilot uses AI. Check for mistakes.
* At least one change applies to this cmdlet. *`n
* See all possible breaking changes at https://go.microsoft.com/fwlink/?linkid=2333486 *`n
***************************************************************************************************")]
Expand Down
2 changes: 1 addition & 1 deletion src/MySql/MySql.Autorest/custom/Update-AzMySqlFlexibleServerFirewallRule.ps1
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -23,7 +23,7 @@ function Update-AzMySqlFlexibleServerFirewallRule {
[OutputType([Microsoft.Azure.PowerShell.Cmdlets.MySql.Models.Api20210501.IFirewallRuleAutoGenerated])]
[CmdletBinding(DefaultParameterSetName='UpdateExpanded', PositionalBinding=$false, SupportsShouldProcess, ConfirmImpact='Medium')]
[Microsoft.Azure.PowerShell.Cmdlets.MySql.Runtime.PreviewMessage("**********************************************************************************************`n
* This cmdlet will undergo a breaking change in Az v16.0.0, to be released on November 19th 2025. *`n
* This cmdlet will undergo a breaking change in Az v16.0.0, to be released on May 2026. *`n
Copy link

Copilot AI Jan 30, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Inconsistent date format: The message uses "to be released on May 2026" but the README.md directive uses "to be released in May 2026". The preposition should be consistent across all files. Since the original format was "November 19th 2025" with a specific day, using "on" with just a month creates grammatical awkwardness. Consider using "in May 2026" to match the README.md, or provide a specific date like "on May 1st 2026".

Suggested change
* This cmdlet will undergo a breaking change in Az v16.0.0, to be released on May 2026. *`n
* This cmdlet will undergo a breaking change in Az v16.0.0, to be released in May 2026. *`n

Copilot uses AI. Check for mistakes.
* At least one change applies to this cmdlet. *`n
* See all possible breaking changes at https://go.microsoft.com/fwlink/?linkid=2333486 *`n
***************************************************************************************************")]
Expand Down
2 changes: 1 addition & 1 deletion src/MySql/MySql.Autorest/docs/Az.MySql.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
---
Module Name: Az.MySql
Module Guid: 6bef555e-dc8a-435e-a876-be02a28513d7
Module Guid: e8b03446-c97b-44b2-828e-564e06e212f5
Download Help Link: https://learn.microsoft.com/powershell/module/az.mysql
Help Version: 1.0.0.0
Locale: en-US
Expand Down
2 changes: 1 addition & 1 deletion src/MySql/MySql.Autorest/generate-info.json
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,3 +1,3 @@
{
"generate_Id": "38c8887a-4aab-412b-9b14-0e5cace59548"
"generate_Id": "727775ec-65b1-47ae-943e-4ef965d9150d"
}
28 changes: 14 additions & 14 deletions src/MySql/MySql.sln
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -21,7 +21,7 @@ Project("{FAE04EC0-301F-11D3-BF4B-00C04F79EFBC}") = "MySql", "MySql\MySql.csproj
EndProject
Project("{2150E333-8FDC-42A3-9474-1A3956D46DE8}") = "MySql.Autorest", "MySql.Autorest", "{3FAB33A8-DCB3-1E46-A31E-A4F2684A642B}"
EndProject
Project("{FAE04EC0-301F-11D3-BF4B-00C04F79EFBC}") = "Az.MySql", "..\..\generated\MySql\MySql.Autorest\Az.MySql.csproj", "{C65E79D1-E7C5-4484-A8D0-21A993C44309}"
Project("{FAE04EC0-301F-11D3-BF4B-00C04F79EFBC}") = "Az.MySql", "..\..\generated\MySql\MySql.Autorest\Az.MySql.csproj", "{1ED8DB5F-B55B-423F-AC15-AB549EBFAADC}"
EndProject
Global
GlobalSection(SolutionConfigurationPlatforms) = preSolution
Expand Down Expand Up @@ -117,18 +117,18 @@ Global
{286CC291-268F-4E04-85A8-1794BAAAF876}.Release|x64.Build.0 = Release|Any CPU
{286CC291-268F-4E04-85A8-1794BAAAF876}.Release|x86.ActiveCfg = Release|Any CPU
{286CC291-268F-4E04-85A8-1794BAAAF876}.Release|x86.Build.0 = Release|Any CPU
{C65E79D1-E7C5-4484-A8D0-21A993C44309}.Debug|Any CPU.ActiveCfg = Debug|Any CPU
{C65E79D1-E7C5-4484-A8D0-21A993C44309}.Debug|Any CPU.Build.0 = Debug|Any CPU
{C65E79D1-E7C5-4484-A8D0-21A993C44309}.Debug|x64.ActiveCfg = Debug|Any CPU
{C65E79D1-E7C5-4484-A8D0-21A993C44309}.Debug|x64.Build.0 = Debug|Any CPU
{C65E79D1-E7C5-4484-A8D0-21A993C44309}.Debug|x86.ActiveCfg = Debug|Any CPU
{C65E79D1-E7C5-4484-A8D0-21A993C44309}.Debug|x86.Build.0 = Debug|Any CPU
{C65E79D1-E7C5-4484-A8D0-21A993C44309}.Release|Any CPU.ActiveCfg = Release|Any CPU
{C65E79D1-E7C5-4484-A8D0-21A993C44309}.Release|Any CPU.Build.0 = Release|Any CPU
{C65E79D1-E7C5-4484-A8D0-21A993C44309}.Release|x64.ActiveCfg = Release|Any CPU
{C65E79D1-E7C5-4484-A8D0-21A993C44309}.Release|x64.Build.0 = Release|Any CPU
{C65E79D1-E7C5-4484-A8D0-21A993C44309}.Release|x86.ActiveCfg = Release|Any CPU
{C65E79D1-E7C5-4484-A8D0-21A993C44309}.Release|x86.Build.0 = Release|Any CPU
{1ED8DB5F-B55B-423F-AC15-AB549EBFAADC}.Debug|Any CPU.ActiveCfg = Debug|Any CPU
{1ED8DB5F-B55B-423F-AC15-AB549EBFAADC}.Debug|Any CPU.Build.0 = Debug|Any CPU
{1ED8DB5F-B55B-423F-AC15-AB549EBFAADC}.Debug|x64.ActiveCfg = Debug|Any CPU
{1ED8DB5F-B55B-423F-AC15-AB549EBFAADC}.Debug|x64.Build.0 = Debug|Any CPU
{1ED8DB5F-B55B-423F-AC15-AB549EBFAADC}.Debug|x86.ActiveCfg = Debug|Any CPU
{1ED8DB5F-B55B-423F-AC15-AB549EBFAADC}.Debug|x86.Build.0 = Debug|Any CPU
{1ED8DB5F-B55B-423F-AC15-AB549EBFAADC}.Release|Any CPU.ActiveCfg = Release|Any CPU
{1ED8DB5F-B55B-423F-AC15-AB549EBFAADC}.Release|Any CPU.Build.0 = Release|Any CPU
{1ED8DB5F-B55B-423F-AC15-AB549EBFAADC}.Release|x64.ActiveCfg = Release|Any CPU
{1ED8DB5F-B55B-423F-AC15-AB549EBFAADC}.Release|x64.Build.0 = Release|Any CPU
{1ED8DB5F-B55B-423F-AC15-AB549EBFAADC}.Release|x86.ActiveCfg = Release|Any CPU
{1ED8DB5F-B55B-423F-AC15-AB549EBFAADC}.Release|x86.Build.0 = Release|Any CPU
EndGlobalSection
GlobalSection(SolutionProperties) = preSolution
HideSolutionNode = FALSE
Expand All @@ -140,6 +140,6 @@ Global
{BA5D2B5D-7F4D-4A92-B035-8F737578F3BC} = {2FFC8559-B8D4-4C7B-8B15-AEECEFA2F290}
{9AD18BB2-11C1-419A-91EA-1EA71A275200} = {2FFC8559-B8D4-4C7B-8B15-AEECEFA2F290}
{A5A6C5E0-EC4D-44BA-8C5A-2D6CAC21D861} = {2FFC8559-B8D4-4C7B-8B15-AEECEFA2F290}
{C65E79D1-E7C5-4484-A8D0-21A993C44309} = {3FAB33A8-DCB3-1E46-A31E-A4F2684A642B}
{1ED8DB5F-B55B-423F-AC15-AB549EBFAADC} = {3FAB33A8-DCB3-1E46-A31E-A4F2684A642B}
EndGlobalSection
EndGlobal
12 changes: 6 additions & 6 deletions src/MySql/MySql/Az.MySql.psd1
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3,7 +3,7 @@
#
# Generated by: Microsoft Corporation
#
# Generated on: 11/11/2025
# Generated on: 1/30/2026
#

@{
Expand Down Expand Up @@ -51,16 +51,16 @@ DotNetFrameworkVersion = '4.7.2'
# ProcessorArchitecture = ''

# Modules that must be imported into the global environment prior to importing this module
RequiredModules = @(@{ModuleName = 'Az.Accounts'; ModuleVersion = '5.3.1'; })
RequiredModules = @(@{ModuleName = 'Az.Accounts'; ModuleVersion = '5.3.2'; })

# Assemblies that must be loaded prior to importing this module
RequiredAssemblies = 'MySql.Autorest/bin/Az.MySql.private.dll'

# Script files (.ps1) that are run in the caller's environment prior to importing this module.
# ScriptsToProcess = @()
ScriptsToProcess = @()

# Type files (.ps1xml) to be loaded when importing this module
# TypesToProcess = @()
TypesToProcess = @()

# Format files (.ps1xml) to be loaded when importing this module
FormatsToProcess = 'MySql.Autorest/Az.MySql.format.ps1xml'
Expand Down Expand Up @@ -123,7 +123,7 @@ PrivateData = @{
PSData = @{

# Tags applied to this module. These help with module discovery in online galleries.
Tags = 'Azure','ResourceManager','ARM','PSModule','MySql'
Tags = 'Azure', 'ResourceManager', 'ARM', 'PSModule', 'MySql'

# A URL to the license for this module.
LicenseUri = 'https://aka.ms/azps-license'
Expand All @@ -149,7 +149,7 @@ PrivateData = @{

} # End of PSData hashtable

} # End of PrivateData hashtable
} # End of PrivateData hashtable

# HelpInfo URI of this module
# HelpInfoURI = ''
Expand Down
Loading