resource/rds_cluster_endpoint: add Create Timeout

[anGie44]

Community Note

• Please vote on this pull request by adding a 👍 reaction to the original pull request comment to help the community and maintainers prioritize this request
• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for pull request followers and do not help prioritize the request

Closes #14570

Release note for CHANGELOG:

resource/rds_cluster_endpoint: increase Create Timeout to 30 minutes

Output from acceptance testing:

--- PASS: TestAccAWSRDSClusterEndpoint_basic (1160.15s)
--- PASS: TestAccAWSRDSClusterEndpoint_tags (1218.53s)

[bflad]

@anGie44 is the creation time dependent on something practitioners manage (e.g. database size)? Typically we want to avoid providing customizable timeouts when operators have no influence/need to adjust it.

[anGie44]

good question @bflad! as far as i could tell the cluster/instance specs don't directly affect this creation time. as part of the issue's task, I interpreted the 2nd bullet point as if this timeout should be customizable by users but since there's no overall effect, will remove the Timeout from the resource schema 👍

[bflad]

@anGie44 oh that's my bad on that second bullet point in the issue -- copypasta from another issue 🍝 😖

[bflad]

Looks great 🚀

Output from acceptance testing:

--- PASS: TestAccAWSRDSClusterEndpoint_basic (1119.73s)
--- PASS: TestAccAWSRDSClusterEndpoint_tags (1120.53s)

[ghost]

This has been released in version 3.5.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 for triage. Thanks!

[ghost]

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 feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks!