Closed ben-dov closed 1 month ago
Voting for Prioritization
Volunteering to Work on This Issue
I will work on it and I will raise PR.
[!WARNING] This issue has been closed, meaning that any additional comments are hard for our team to see. Please assume that the maintainers will not see them.
Ongoing conversations amongst community members are welcome, however, the issue will be locked after 30 days. Moving conversations to another venue, such as the AWS Provider forum, is recommended. If you have additional concerns, please open a new issue, referencing this one where needed.
This functionality has been released in v5.63.0 of the Terraform AWS 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. 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.
Documentation Link
https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/rds_cluster_instance#db_subnet_group_name
Description
Copied from hashicorp/terraform#35353 The document page mistakenly asserts that
db_subnet_group_name
is required ifpublicly_accessible = false
(which is the default), but it seems in the cli:So unless I am misunderstanding the docs, it seems like this section should be changed.
References
https://docs.aws.amazon.com/cli/latest/reference/rds/create-db-instance.html
Would you like to implement a fix?
No