NeonPostgres PS cmdlets 2024-08-01-preview

[almasak]

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

  • General release
  • Public preview
  • Private preview
  • Engineering build
  • No need for a release

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

️✔️Build

️✔️PowerShell Core - Windows

️✔️Breaking Change Check

️✔️PowerShell Core - Windows

⚠️Signature Check

⚠️PowerShell Core - Windows

Type	Cmdlet	Description	Remediation
⚠️	Get-AzNeonPostgresOrganization	Get-AzNeonPostgresOrganization 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-AzNeonPostgresOrganization	Get-AzNeonPostgresOrganization 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.NeonPostgres.	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]

@almasak Hi, we have frozen the code for this release(2024-11-11). Your pr would be reviewed and merged in our next public release, which would be (2024-11-19)

[almasak]

@almasak Hi, we have frozen the code for this release(2024-11-11). Your pr would be reviewed and merged in our next public release, which would be (2024-11-19)

Sure, no problem.

[vidai-msft]

@almasak Please fill in the examples and test cases. The test coverage for a module should be no less than 80%.

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

[almasak]

@almasak Please fill in the examples and test cases. The test coverage for a module should be no less than 80%.

Added the examples

[vidai-msft]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 3 pipeline(s).

[almasak]

/azp run

[azure-pipelines]

Commenter does not have sufficient privileges for PR 26492 in repo Azure/azure-powershell

[vidai-msft]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 3 pipeline(s).

[vidai-msft]

/azp run license/cla

[azure-pipelines]

No pipelines are associated with this pull request.

[vidai-msft]

@almasak Please write test cases for the new cmdlets and then record them

[almasak]

@almasak Please write test cases for the new cmdlets and then record them

Added!

[vidai-msft]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 3 pipeline(s).

[vidai-msft]

LGTM