-
Notifications
You must be signed in to change notification settings - Fork 9.2k
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
Added timeouts to QLDB ledger #29635
Added timeouts to QLDB ledger #29635
Conversation
Community NoteVoting for Prioritization
For Submitters
|
Thank you for your contribution! 🚀 Please note that typically Go dependency changes are handled in this repository by dependabot or the maintainers. This is to prevent pull request merge conflicts and further delay reviews of contributions. Remove any changes to the Additional details:
|
Could a maintainer please look at this? |
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=TestAccQLDBLedger_' PKG=qldb
==> Checking that code complies with gofmt requirements...
TF_ACC=1 go test ./internal/service/qldb/... -v -count 1 -parallel 20 -run=TestAccQLDBLedger_ -timeout 180m
--- PASS: TestAccQLDBLedger_kmsKey (322.94s)
--- PASS: TestAccQLDBLedger_disappears (326.60s)
--- PASS: TestAccQLDBLedger_update (328.12s)
--- PASS: TestAccQLDBLedger_nameGenerated (328.40s)
--- PASS: TestAccQLDBLedger_tags (341.92s)
--- PASS: TestAccQLDBLedger_basic (586.11s)
PASS
ok github.com/hashicorp/terraform-provider-aws/internal/service/qldb 589.094s
@bjernie thanks for the contribution? 🎉 |
This functionality has been released in v4.59.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 timeouts for
aws_qldb_ledger
Relations
Closes #28231