-
Notifications
You must be signed in to change notification settings - Fork 9.4k
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 possibility to retry/delay/timeout on data sources #11342
Comments
any updates? |
Hi Team, Any updates on the ticket? I'm looking forward to hearing from you guys. Thanks |
Any updates ? |
Any updates on this issue?? |
Any updates? or at least offer workaround (don't offer re-running with apply) |
This functionality has been released in v4.25.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 issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. |
Community Note
Description
First of all, I was not sure if I needed to post this feature request here or in terraform core itself but as we are using AWS provider intensely in the first place and considering that this is also requiring changes in its corresponding code, I thought this was the best place to post this FR
Second, do not flame me right away as I know this is not really matching the "philosophical" way terraform and providers are supposed to work, but considering all others questions I have seen here and there concerning similar things I thought there is room/legitimity for this enhancement
Third, as I did look at the source code and more specifically aws/data_source_aws_instances.go, I think this could be done quite easily/effortlessly
OK so here is my concern: let's assume we are using Autoscaling group and need to specify a dedicated target group rule for each instance (like a monitoring agent, ...). This could be done via Lambda code plugged to autoscaling events of course or also within the HCL code using a workaround/hack with null_resources, local-exec, sleep and data sources but as far as what I read so far:
New or Affected Resource(s)
All data sources concerning dynamic resources
Potential Terraform Configuration
References
The text was updated successfully, but these errors were encountered: