resource/aws_rds_cluster_endpoint: Increase Default Create Timeout

[bflad]

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue 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 issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

Description

Given fairly consistent daily acceptance testing failures such as:

=== CONT  TestAccAWSRDSClusterEndpoint_tags
TestAccAWSRDSClusterEndpoint_tags: testing.go:684: Step 0 error: errors during apply:
Error: Error waiting for RDS Cluster Endpoint (reader-7926473369288959707) to be ready: timeout while waiting for state to become 'available' (last state: 'creating', timeout: 20m0s)

It appears the default Create timeout needs to be increased in the aws_rds_cluster_endpoint resource.

Affected Resource(s)

• aws_rds_cluster_endpoint

Definition of Done

• Default timeout(s) updated in aws/resource_aws_rds_cluster_endpoint.go
• Timeout documentation updated in website/docs/r/aws_rds_cluster_endpoint.html.markdown
• TestAccAWSRDSClusterEndpoint_ testing passes

References

• Technical Debt Theme: Resolve Acceptance Test Failures (RDS) #14384

[anGie44]

The timeout fix has been merged and will release with v3.5.0 of the Terraform AWS Provider, expected out next Thurs.

[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!