Postgresql Flexible Server should support geoBackupKeyURI and geoBackupUserAssignedIdentityId when geoRedundantBackup is enabled and CMK is set

[neil-yechenwei]

Hi team,
When geoRedundantBackup is enabled and CMK is set, geoBackupKeyURI and geoBackupUserAssignedIdentityId also need to be set. But unfortunately, seems these two properties haven't been supported by API. So does it make sense to support them in azure rest api spec?

The related API spec: https://github.com/Azure/azure-rest-api-specs/blob/main/specification/postgresql/resource-manager/Microsoft.DBforPostgreSQL/stable/2022-12-01/FlexibleServers.json#L762

[ghost]

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @sunilagarwal, @lfittl-msft, @sr-msft, @niklarin.

Issue Details

---

Hi team,
When geoRedundantBackup is enabled and CMK is set, geoBackupKeyURI and geoBackupUserAssignedIdentityId also need to be set. But unfortunately, seems these two properties haven't been supported by API. So does it make sense to support them in azure rest api spec?

The related API spec: https://github.com/Azure/azure-rest-api-specs/blob/main/specification/postgresql/resource-manager/Microsoft.DBforPostgreSQL/stable/2022-12-01/FlexibleServers.json#L762

Author:	neil-yechenwei
Assignees:	-
Labels:	PostgreSQL, Service Attention, needs-triage
Milestone:	-

[nilpferd21]

There is a new version of the API: 2023-03-01-preview

[neil-yechenwei]

Hi service team , I have some questions about this new preview API version. Could you take a look since we have to take action according to your more information? Thanks.

Question 1:
May I ask whether this preview API version is in public preview?

Question 2:
Could you double confirm whether there is no breaking change between current preview API and previous/future stable version API for forward/backward compatibility?

Question 3:
May I ask when will this feature be released to stable API version?