-
Notifications
You must be signed in to change notification settings - Fork 9.1k
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
Enhancement: add configurable timeouts to r/aws_rds_cluster_role_association
#31015
Enhancement: add configurable timeouts to r/aws_rds_cluster_role_association
#31015
Conversation
Community NoteVoting for Prioritization
For Submitters
|
aws_rds_cluster_role_association
aws_rds_cluster_role_association
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM 🚀.
% make testacc TESTARGS='-run=TestAccRDSClusterRoleAssociation_basic$$' PKG=rds
==> Checking that code complies with gofmt requirements...
TF_ACC=1 go test ./internal/service/rds/... -v -count 1 -parallel 20 -run=TestAccRDSClusterRoleAssociation_basic$ -timeout 180m
=== RUN TestAccRDSClusterRoleAssociation_basic
=== PAUSE TestAccRDSClusterRoleAssociation_basic
=== CONT TestAccRDSClusterRoleAssociation_basic
--- PASS: TestAccRDSClusterRoleAssociation_basic (254.30s)
PASS
ok github.com/hashicorp/terraform-provider-aws/internal/service/rds 259.886s
@tamiros Thanks for the contribution 🎉 👏. |
This functionality has been released in v4.66.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 pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. |
Description
Added configurable timeouts for the resource
aws_rds_cluster_role_association
.The default for Create and Delete operations is still 10 minutes (there is no Update operation for the resource).
Also, omitted the
backup_retention_period
andpreferred_backup_window
which caused the acceptance testTestAccRDSClusterRoleAssociation_basic
to try and delete the associated IAM Role while the cluster was in "backing-up" state:Now the cluster resource itself in that particular acceptance test matches the one in the test
testAccClusterConfig_basic
in the filecluster_test.go
.Relations
Closes #30868
References
Output from Acceptance Testing