-
Notifications
You must be signed in to change notification settings - Fork 9.3k
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
Cleaning up some resource retries for cloudwatch functions #9065
Conversation
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.
Some minor changes needed below then we can retest this. 👍
Co-Authored-By: Brian Flad <bflad417@gmail.com>
|
||
err = resource.Retry(1*time.Minute, func() *resource.RetryError { |
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.
Not sure how I missed this the first lookthrough, but the addition of this new resource.Retry()
is extraneous here and will never pass after retries. The original intention of the retry logic was to treat completely a missing policy and a policy missing the new statement as the same for retries. This logic should all be contained in one big retry function as it was originally or split into its own function so the isResourceTimeoutError()
implementation is easier. 👍
@bflad any other changes you'd like to see to 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.
Looks good! Thanks for sticking through this one. 🚀
--- PASS: TestAccAWSCloudWatchEventPermission_Action (9.19s)
--- PASS: TestAccAWSCloudWatchEventPermission_Basic (17.05s)
--- PASS: TestAccAWSCloudWatchEventPermission_Condition (14.73s)
--- PASS: TestAccAWSCloudWatchEventPermission_Disappears (69.44s)
--- PASS: TestAccAWSCloudWatchEventPermission_Multiple (14.49s)
--- PASS: TestAccAWSCloudWatchEventRule_basic (19.15s)
--- PASS: TestAccAWSCloudWatchEventRule_enable (26.67s)
--- PASS: TestAccAWSCloudWatchEventRule_full (12.55s)
--- PASS: TestAccAWSCloudWatchEventRule_importBasic (14.36s)
--- PASS: TestAccAWSCloudWatchEventRule_prefix (11.59s)
--- PASS: TestAccAWSCloudWatchEventRule_tags (29.49s)
--- PASS: TestAccAWSCloudwatchLogDestination_basic (101.51s)
--- PASS: TestAccAWSCloudwatchLogDestination_importBasic (107.48s)
--- PASS: TestAccAWSCloudwatchLogSubscriptionFilter_basic (36.08s)
--- PASS: TestAccAWSCloudwatchLogSubscriptionFilter_disappears (33.58s)
--- PASS: TestAccAWSCloudwatchLogSubscriptionFilter_disappears_LogGroup (33.42s)
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! |
Community Note
Related #7873
Release note for CHANGELOG:
Output from acceptance testing: