-
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
Add retry for MWAA CreateEnvironment on ValidationException
#27031
Add retry for MWAA CreateEnvironment on ValidationException
#27031
Conversation
Community NoteVoting for Prioritization
For Submitters
|
Can you advise on the right use of If I'm interpreting correctly, it's used to trigger cleanup when the timeout occurs. MWAA environments have a blocking status. If the Environment is in CREATING then DeleteEnvironment cannot be called. Should the |
ValidationException
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 🚀.
% ACCTEST_TIMEOUT=360m make testacc TESTARGS='-run=TestAccMWAAEnvironment_' PKG=mwaa ACCTEST_PARALLELISM=2
==> Checking that code complies with gofmt requirements...
TF_ACC=1 go test ./internal/service/mwaa/... -v -count 1 -parallel 2 -run=TestAccMWAAEnvironment_ -timeout 360m
=== RUN TestAccMWAAEnvironment_basic
=== PAUSE TestAccMWAAEnvironment_basic
=== RUN TestAccMWAAEnvironment_disappears
=== PAUSE TestAccMWAAEnvironment_disappears
=== RUN TestAccMWAAEnvironment_airflowOptions
=== PAUSE TestAccMWAAEnvironment_airflowOptions
=== RUN TestAccMWAAEnvironment_log
=== PAUSE TestAccMWAAEnvironment_log
=== RUN TestAccMWAAEnvironment_full
=== PAUSE TestAccMWAAEnvironment_full
=== RUN TestAccMWAAEnvironment_pluginsS3ObjectVersion
=== PAUSE TestAccMWAAEnvironment_pluginsS3ObjectVersion
=== CONT TestAccMWAAEnvironment_basic
=== CONT TestAccMWAAEnvironment_log
--- PASS: TestAccMWAAEnvironment_basic (2314.28s)
=== CONT TestAccMWAAEnvironment_airflowOptions
--- PASS: TestAccMWAAEnvironment_log (2990.47s)
=== CONT TestAccMWAAEnvironment_disappears
--- PASS: TestAccMWAAEnvironment_disappears (2505.37s)
=== CONT TestAccMWAAEnvironment_pluginsS3ObjectVersion
--- PASS: TestAccMWAAEnvironment_airflowOptions (3730.01s)
=== CONT TestAccMWAAEnvironment_full
--- PASS: TestAccMWAAEnvironment_full (2338.81s)
--- PASS: TestAccMWAAEnvironment_pluginsS3ObjectVersion (3079.22s)
PASS
ok github.com/hashicorp/terraform-provider-aws/internal/service/mwaa 8580.178s
@dhegberg Thanks for the contribution 🎉 👏. |
This functionality has been released in v4.34.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. |
Handles scenario where IAM permission used in validation are slow to propagate.
Description
Introduce a retry on ValidationException & InternalServiceException
InternalServiceException is a general service 500 that can be retried.
ValidationException will include the case where an recently created IAM role is experiencing permission propagation delay. This retry is currently internal to the CreateEnvironment API, but will be removed in an upcoming release.
Relations
Relates #26429
References
Output from Acceptance Testing
Acceptance tests fail, but the same tests on the previous commit also fail.
Verified MWAA Environment creation does succeed. Tested triggering ValidationError and verified multiple retries occurred.