Feature standbypool powershell init

[fangru2023]

Description

ChangeLog: release version: Version 1.0.0, general available for Standby Pool service.
Target release date: 04-28-2024

Mandatory Checklist

• Please choose the target release of Azure PowerShell

  • General release
  • Public preview
  • Private preview
  • Engineering build
  • N/A

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

[azure-client-tools-bot-prd]

️✔️Az.Accounts

️✔️Build

️✔️PowerShell Core - Windows

⚠️Az.StandbyPool

️✔️Build

️✔️PowerShell Core - Windows

️✔️Breaking Change Check

️✔️PowerShell Core - Windows

⚠️Signature Check

⚠️PowerShell Core - Windows

Type	Cmdlet	Description	Remediation
⚠️	Get-AzStandbyContainerGroupPool	Get-AzStandbyContainerGroupPool Changes the ConfirmImpact but does not set the SupportsShouldProcess property to true in the cmdlet attribute.	Determine if the cmdlet should implement ShouldProcess and if so determine if it should implement Force / ShouldContinue
⚠️	Get-AzStandbyContainerGroupPool	Get-AzStandbyContainerGroupPool changes the confirm impact. Please ensure that the change in ConfirmImpact is justified	Verify that ConfirmImpact is changed appropriately by the cmdlet. It is very rare for a cmdlet to change the ConfirmImpact.
⚠️	Get-AzStandbyVMPool	Get-AzStandbyVMPool Changes the ConfirmImpact but does not set the SupportsShouldProcess property to true in the cmdlet attribute.	Determine if the cmdlet should implement ShouldProcess and if so determine if it should implement Force / ShouldContinue
⚠️	Get-AzStandbyVMPool	Get-AzStandbyVMPool changes the confirm impact. Please ensure that the change in ConfirmImpact is justified	Verify that ConfirmImpact is changed appropriately by the cmdlet. It is very rare for a cmdlet to change the ConfirmImpact.
⚠️	Get-AzStandbyVMPoolVM	Get-AzStandbyVMPoolVM Changes the ConfirmImpact but does not set the SupportsShouldProcess property to true in the cmdlet attribute.	Determine if the cmdlet should implement ShouldProcess and if so determine if it should implement Force / ShouldContinue
⚠️	Get-AzStandbyVMPoolVM	Get-AzStandbyVMPoolVM changes the confirm impact. Please ensure that the change in ConfirmImpact is justified	Verify that ConfirmImpact is changed appropriately by the cmdlet. It is very rare for a cmdlet to change the ConfirmImpact.

️✔️Help Example Check

️✔️PowerShell Core - Windows

️✔️Help File Existence Check

️✔️PowerShell Core - Windows

⚠️File Change Check

⚠️PowerShell Core - Windows

Type	Cmdlet	Description	Remediation
⚠️		It is required to update ChangeLog.md if you want to release a new version for Az.StandbyPool.	Add a changelog record under Upcoming Release section with past tense.

️✔️UX Metadata Check

️✔️PowerShell Core - Windows

️✔️Test

️✔️PowerShell Core - Linux

️✔️PowerShell Core - MacOS

️✔️PowerShell Core - Windows

[Nickcandy]

Hi @fangru2023, here is the error of the pipeline check. Please try to fix the parameter issue:
` "Module","ClassName","Target","Severity","ProblemId","Description","Remediation"
"Az.StandbyPool","New-AzStandbyContainerPool","New-AzStandbyContainerPool","1","8410","Parameter SubnetIds of cmdlet New-AzStandbyContainerPool does not follow the enforced naming convention of using a singular noun for a parameter name.","Consider using a singular noun for the parameter name."
"Az.StandbyPool","Update-AzStandbyContainerPool","Update-AzStandbyContainerPool","1","8410","Parameter SubnetIds of cmdlet Update-AzStandbyContainerPool does not follow the enforced naming convention of using a singular noun for a parameter name.","Consider using a singular noun for the parameter name."

`

[github-actions]

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.

[fangru2023]

Hi @Nickcandy thanks for heads up, fix these CI failures.

[fangru2023]

Also, I have a question, if we want to release our sdk, should we run "Sync Module From Generation Branch To Main" and create another PR to check-in to main branch?

[Nickcandy]

Also, I have a question, if we want to release our sdk, should we run "Sync Module From Generation Branch To Main" and create another PR to check-in to main branch?

Hi @fangru2023, you don't need to create pr or run sync. We would help you sync to main branch.

[fangru2023]

package version will be Az.StandbyPool.0.1.0.nupkg