You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Looks like this was added to aws_rds_db_instance in #1041. It would be good to have this exposed for the aws_rds_cluster / aws_rds_cluster_instance resources as well. However it looks like both CreateDBCluster and CreateDBInstance methods have a StorageEncrypted flag, and I'm not clear on how those are supposed to interact. Ideally, the user would specify storage_encrypted on the aws_rds_cluster resource, and then any instances attached to that cluster would have that value computed.
The text was updated successfully, but these errors were encountered:
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.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
ghost
locked and limited conversation to collaborators
Apr 27, 2020
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Looks like this was added to
aws_rds_db_instance
in #1041. It would be good to have this exposed for theaws_rds_cluster
/aws_rds_cluster_instance
resources as well. However it looks like both CreateDBCluster and CreateDBInstance methods have a StorageEncrypted flag, and I'm not clear on how those are supposed to interact. Ideally, the user would specifystorage_encrypted
on theaws_rds_cluster
resource, and then any instances attached to that cluster would have that value computed.The text was updated successfully, but these errors were encountered: