You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When attempting to perform a terraform plan on an admittedly large number of resources, I hit the API rate limit while the plan refreshes the state, and my terraform plan fails. If I am lucky, it will work on the next run. My concern is if I keep building infrastructure out, I will run into a point where I won't be able to re-run by builds, as my code base has become too large.
I could split up my states, so that each state tracks a smaller group of inventory, but other providers have solved this exact problem by adding a configurable API retry to their provider configuration.
I am wondering if we can do something similar here.
@tjkervin We plan to release an enhancement to allow configurable retry timeouts. The way you would set this is through a new field in the provider oci block like this:
provider oci {
retry_timeout_seconds = "3600"
}
This would affect how long retries will continue in the face of 429 and 500 errors.
Terraform Version
Terraform v0.11.7
OCI Provider Version
3.7.0
Description:
When attempting to perform a terraform plan on an admittedly large number of resources, I hit the API rate limit while the plan refreshes the state, and my terraform plan fails. If I am lucky, it will work on the next run. My concern is if I keep building infrastructure out, I will run into a point where I won't be able to re-run by builds, as my code base has become too large.
I could split up my states, so that each state tracks a smaller group of inventory, but other providers have solved this exact problem by adding a configurable API retry to their provider configuration.
I am wondering if we can do something similar here.
Terraform Plan
Error: Error refreshing state: 1 error(s) occurred:
module.instance_name_1.data.oci_core_vnic.resource_Vnic_n2: 1 error(s) occurred::
module.instance_name_1.data.oci_core_vnic.resource_Vnic_n2: data.oci_core_vnic.resource_Vnic_n2: Service error:TooManyRequests. User-rate limit exceeded.. http status code: 429. Opc request id: f1f727525fda6940c8c105ce7058e8c4/CAB13F834C66C4763C955BFA05E664F5/23D5EE262DE0B8B3A68144D777606E99
The text was updated successfully, but these errors were encountered: