-
Notifications
You must be signed in to change notification settings - Fork 4.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
PostgreSQL Flexible Server - CMKNotSupportedForGeoRedundantBackupEnabledServer #25138
Comments
Thanks for raising this issue. Seems I can't reproduce this issue on my local with below tf config. Could you try below tf config to see if the issue still exists? Thanks. tf config:
|
@neil-yechenwei , sorry for the noise, following your example I was able to figure out the issue in our code base. thank you for the time and the exhaustive example. |
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. |
Is there an existing issue for this?
Community Note
Terraform Version
1.7.3
AzureRM Provider Version
3.94.0
Affected Resource(s)/Data Source(s)
azurerm_postgresql_flexible_server
Terraform Configuration Files
Debug Output/Panic Output
Expected Behaviour
PostgreSQL Server is created with CMK configured and geo-redundant backup.
Actual Behaviour
Error on apply:
│ Error: creating Flexible Server (Subscription: ""
│ Resource Group Name: "rg-infr-dev-weu"
│ Flexible Server Name: "psqlflex-infr-dev-weu-1"): polling after Create: polling failed: the Azure API returned the following error:
│
│ Status: "CMKNotSupportedForGeoRedundantBackupEnabledServer"
│ Code: ""
│ Message: "Customer Managed Key encryption is not supported for Geo redundant backup enabled server."
Similar issue existed #20750 , was fixed by updating API version to 2023-03-01-preview, now the API version is 2023-06-01-preview. Seems there is an issue with the current API versionl.
Steps to Reproduce
No response
Important Factoids
No response
References
No response
The text was updated successfully, but these errors were encountered: