-
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
Contributing Documentation: Add section on error handling #15792
Comments
Since this is similar to other in progress provider documentation I'm already working on, picking this up as well. Most likely this will make sense as its own page, since there could be a lot of content that does not fit well with the existing information architecture of the contributing guide. |
Reference: #12844 Reference: #15792 Reference: #16796 This page is meant to serve as a reference for all the related retry and waiting logic present in the provider. Further enhancements could discuss resource timeouts in general, however there is some future uncertainty with that functionality so it is currently omitted.
Reference: #12844 Reference: #15792 Reference: #16796 This page is meant to serve as a reference for all the related retry and waiting logic present in the provider. Further enhancements could discuss resource timeouts in general, however there is some future uncertainty with that functionality so it is currently omitted.
This information is now present in the following Contributing Guide documentation: |
This has been released in version 3.28.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 for triage. Thanks! |
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! |
Add a section to documentation providing guidance on API error handling.
Among others, things to document:
d.SetId("")
when not found during the Read operationresource.Retry(iamwaiter.PropagationTimeout, ...)
for IAM eventual consistencyThe text was updated successfully, but these errors were encountered: