Review request for Microsoft.DBforPostgreSQL to add stable release of version 2024-08-01

[nasc17]

ARM (Control Plane) API Specification Update Pull Request

PR review workflow diagram

Please understand this diagram before proceeding. It explains how to get your PR approved & merged.

Purpose of this PR

What's the purpose of this PR? Check the specific option that applies. This is mandatory!

• [X ] New API version for an existing resource provider. (If API spec is not defined in TypeSpec, the PR should have been created in adherence to OpenAPI specs PR creation guidance).

Due diligence checklist

To merge this PR, you must go through the following checklist and confirm you understood and followed the instructions by checking all the boxes:

• [ X] I confirm this PR is modifying Azure Resource Manager (ARM) related specifications, and not data plane related specifications.
• [X ] I have reviewed following Resource Provider guidelines, including ARM resource provider contract and REST guidelines (estimated time: 4 hours).
  I understand this is required before I can proceed to the diagram Step 2, "ARM API changes review", for this PR.

Additional information

Viewing API changes

Added new GA API version 2024-08-01 This stable version introduces following: 1. Geo + CMK - Revive Dropped 2. Storage auto growth 3. IOPS scaling 4. New location capability api 5. Long Term Retention Backup 6. Server Logs 7. Migrations 8. Migration Pre-validation 9. Read replicas - Switchover (Site swap) 10. Read replicas - Virtual Endpoints 11. Private Endpoints 12. Azure Defender / Threat Protection APIs 13. PG 16 support 14. PremiumV2_LRS storage type support 15. Location capability changes for SSDv2 16. Migration Roles 17. Migration Instance Resource Id to support Private endpoint Migrations 18. On-demand backup

Suppressing failures

If one or multiple validation error/warning suppression(s) is detected in your PR, please follow the [suppressions guide](https://aka.ms/azsdk/pr-suppressions) to get approval.

Getting help

• First, please carefully read through this PR description, from top to bottom. Please fill out the Purpose of this PR and Due diligence checklist.
• If you don't have permissions to remove or add labels to the PR, request write access per aka.ms/azsdk/access#request-access-to-rest-api-or-sdk-repositories
• To understand what you must do next to merge this PR, see the Next Steps to Merge comment. It will appear within few minutes of submitting this PR and will continue to be up-to-date with current PR state.
• For guidance on fixing this PR CI check failures, see the hyperlinks provided in given failure and https://aka.ms/ci-fix.
• For help with ARM review (PR workflow diagram Step 2), see https://aka.ms/azsdk/pr-arm-review.
• If the PR CI checks appear to be stuck in queued state, please add a comment with contents /azp run. This should result in a new comment denoting a PR validation pipeline has started and the checks should be updated after few minutes.
• If the help provided by the previous points is not enough, post to https://aka.ms/azsdk/support/specreview-channel and link to this PR.

[openapi-pipeline-app[bot]]

Next Steps to Merge

Next steps that must be taken to merge this PR:

• ❌ This is the public specs repo main branch which is not intended for iterative development.
  You must acknowledge that you understand that after this PR is merged, you won't be able to stop your changes from being published to Azure customers.
  If this is what you intend, add PublishToCustomers label to your PR.
  Otherwise, retarget this PR onto a feature branch, i.e. with prefix release- (see aka.ms/azsdk/api-versions#release--branches).
• ❌ The required check named Automated merging requirements met has failed. This is the final check that must pass. Refer to the check in the PR's 'Checks' tab for details on how to fix it and consult the aka.ms/ci-fix guide. In addition, refer to step 4 in the PR workflow diagram

[openapi-pipeline-app[bot]]

Generated ApiView

Language	Package Name	ApiView Link
Go	sdk/resourcemanager/postgresql/armpostgresql	There is no API change compared with the previous version
Go	sdk/resourcemanager/postgresql/armpostgresqlflexibleservers	https://apiview.dev/Assemblies/Review/af578fe7418c4c5b9155096b33a0d480?revisionId=8d992b9571304a52ac470efc1ac88946
Java	azure-resourcemanager-postgresqlflexibleserver	https://apiview.dev/Assemblies/Review/21a61d731117447dbd7223467d7cfa42?revisionId=0204f6df161d418383cebf9958a8e0e2

[nasc17]

Hi @mikekistler These changes were approved in pr #30433 but I abandoned to redo here.

Breaking changes previously reviewed and approved in https://github.com/Azure/azure-rest-api-specs/pull/29295

[nasc17]

/azp run

[azure-pipelines[bot]]

Azure Pipelines successfully started running 3 pipeline(s).