-
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
Support for CMK in azurerm_postgresql_flexible_server resource #19215
Comments
This comment was marked as duplicate.
This comment was marked as duplicate.
This comment was marked as duplicate.
This comment was marked as duplicate.
This comment was marked as duplicate.
This comment was marked as duplicate.
Support for MySQL Flexible has been just added #19842, waiting for postgresql : ) |
@AndrzejK-Atende when can we expect Support for CMK in azurerm_postgresql_flexible_server resource ? any approximate date ? |
I hope so! Is the last missing part for me. |
This functionality has been released in v3.41.0 of the Terraform Provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you! |
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
Description
Azure Database for PostgreSQL flexible servers now supports using a customer managed encryption key (CMK / CMEK) for encryption of databases and backups. The feature is currently in public preview (starting october 2022). Please add support for this feature in the azurerm provider. The docs for this feature can be found here:
https://learn.microsoft.com/en-us/azure/postgresql/flexible-server/concepts-data-encryption
Thanks!
New or Affected Resource(s)/Data Source(s)
azurerm_postgresql_flexible_server
Potential Terraform Configuration
References
The text was updated successfully, but these errors were encountered: