-
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
fix: add iam retry to eks access entry #35535
fix: add iam retry to eks access entry #35535
Conversation
Community NoteVoting for Prioritization
For Submitters
|
e28a9fa
to
4da2e2b
Compare
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=TestAccEKSAccessEntry_eventualConsistency\|TestAccEKSAccessEntry_basic' PKG=eks
==> Checking that code complies with gofmt requirements...
TF_ACC=1 go test ./internal/service/eks/... -v -count 1 -parallel 20 -run=TestAccEKSAccessEntry_eventualConsistency\|TestAccEKSAccessEntry_basic -timeout 360m
=== RUN TestAccEKSAccessEntry_basic
=== PAUSE TestAccEKSAccessEntry_basic
=== RUN TestAccEKSAccessEntry_eventualConsistency
=== PAUSE TestAccEKSAccessEntry_eventualConsistency
=== CONT TestAccEKSAccessEntry_basic
=== CONT TestAccEKSAccessEntry_eventualConsistency
--- PASS: TestAccEKSAccessEntry_basic (552.72s)
--- PASS: TestAccEKSAccessEntry_eventualConsistency (645.22s)
PASS
ok github.com/hashicorp/terraform-provider-aws/internal/service/eks 655.765s
@iandrewt Thanks for the contribution 🎉 👏. |
This functionality has been released in v5.35.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
If an EKS Access Entry is made in the same Terraform apply as the IAM role associated with it, it may fail due to eventual consistency with IAM. This PR adds a retry to handle this case.
The existing tests would not have triggered this as the IAM role resource did not depend on the cluster resource, so the role would have been made early, with plenty of time for consistency to catch up by the time the cluster was ready to accept access entry resources.
Relations
N/A
References
N/A
Output from Acceptance Testing