Migrate Resources from generation to release-2024-11-11

[azure-pipelines]

Description

Migrate Resources from generation to release-2024-11-11
The last commit of src/Resources in generation is:
commit 14423bf Author: skadhiresan [email protected] Date: Tue Oct 29 23:15:20 2024 -0700 [ARM] New cmdlets for DataBoundaries (#26158) * intial cmdlets * tests * examples * testing * updated readme * fixing build * remove update files * removing update command * examples edit * naming * formatting * fix error * examples fix * description * example update * updated docs * default issue * optional * revert * Create UXMetadataIssues.csv * Update UXMetadataIssues.csv --------- Co-authored-by: NanxiangLiu [email protected]

Checklist

• Check this box to confirm: I have read the Submitting Changes section of CONTRIBUTING.md and reviewed the following information:

• SHOULD select appropriate branch. Cmdlets from Autorest.PowerShell should go to generation branch.
• SHOULD make the title of PR clear and informative, and in the present imperative tense.
• SHOULD update ChangeLog.md file(s) appropriately
  • For any service, the ChangeLog.md file can be found at 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. Add changelog in description section if PR goes into generation branch.
  • Should not change ChangeLog.md if no new release is required, such as fixing test case only.
• SHOULD have approved design review for the changes in this repository (Microsoft internal only) with following situations
  • Create new module from scratch
  • Create new resource types which are not easy to conform to Azure PowerShell Design Guidelines
  • Create new resource type which name doesn't use module name as prefix
  • Have design question before implementation
• SHOULD regenerate markdown help files if there is cmdlet API change. Instruction
• SHOULD have proper test coverage for changes in pull request.
• SHOULD NOT introduce breaking changes in Az minor release except preview version.
• SHOULD NOT adjust version of module manually in pull request

[azure-client-tools-bot-prd]

️✔️Az.Accounts

️✔️Build

️✔️PowerShell Core - Windows

️✔️Windows PowerShell - Windows

⚠️Az.Blueprint

️✔️Build

️✔️PowerShell Core - Windows

️✔️Windows PowerShell - Windows

⚠️Test

⚠️ - Linux

Type	Title	Current Coverage	Description
⚠️	Test Coverage Less Than 50%	23.08 %	Test coverage for the module cannot be lower than 50%.

⚠️ - MacOS

Type	Title	Current Coverage	Description
⚠️	Test Coverage Less Than 50%	23.08%	Test coverage for the module cannot be lower than 50%.

⚠️PowerShell Core - Windows

Type	Title	Current Coverage	Description
⚠️	Test Coverage Less Than 50%	23.08%	Test coverage for the module cannot be lower than 50%.

⚠️Windows PowerShell - Windows

Type	Title	Current Coverage	Description
⚠️	Test Coverage Less Than 50%	23.08%	Test coverage for the module cannot be lower than 50%.

️✔️Az.CosmosDB

️✔️Build

️✔️PowerShell Core - Windows

️✔️Windows PowerShell - Windows

️✔️Test

️✔️ - Linux

️✔️ - MacOS

️✔️PowerShell Core - Windows

️✔️Windows PowerShell - Windows

️✔️Az.KeyVault

️✔️Build

️✔️PowerShell Core - Windows

️✔️Windows PowerShell - Windows

⚠️Az.MachineLearning

️✔️Build

️✔️PowerShell Core - Windows

️✔️Windows PowerShell - Windows

⚠️Test

⚠️ - Linux

Type	Title	Current Coverage	Description
⚠️	Test Coverage Less Than 50%	0.00 %	Test coverage for the module cannot be lower than 50%.

⚠️ - MacOS

Type	Title	Current Coverage	Description
⚠️	Test Coverage Less Than 50%	0.00%	Test coverage for the module cannot be lower than 50%.

⚠️PowerShell Core - Windows

Type	Title	Current Coverage	Description
⚠️	Test Coverage Less Than 50%	0.00%	Test coverage for the module cannot be lower than 50%.

⚠️Windows PowerShell - Windows

Type	Title	Current Coverage	Description
⚠️	Test Coverage Less Than 50%	0.00%	Test coverage for the module cannot be lower than 50%.

️✔️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

⚠️Az.Resources

️✔️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

⚠️Test

⚠️ - Linux

Type	Title	Current Coverage	Description
⚠️	Test Coverage Less Than 50%	49.76 %	Test coverage for the module cannot be lower than 50%.

⚠️ - MacOS

Type	Title	Current Coverage	Description
⚠️	Test Coverage Less Than 50%	49.76%	Test coverage for the module cannot be lower than 50%.

⚠️PowerShell Core - Windows

Type	Title	Current Coverage	Description
⚠️	Test Coverage Less Than 50%	49.76%	Test coverage for the module cannot be lower than 50%.

⚠️Windows PowerShell - Windows

Type	Title	Current Coverage	Description
⚠️	Test Coverage Less Than 50%	49.76%	Test coverage for the module cannot be lower than 50%.

[microsoft-github-policy-service]

Thank you for your contribution azure-pipelines[bot]! We will review the pull request and get back to you soon.

[Nickcandy]

/azp run azure-powershell - security-tools

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).