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
As a result of #454 running terraform on a project with an error in the config or one that contains a resource that had been manually deleted became extremely slow. The rules for retry are not centralized and vary widely from resource type to resource type.
There is a lot of value in retrying for a long time on 429 but for example, we should not wait 5 min to learn we made a typo or are missing field and get a 400. Sometimes it might be valuable to avoid a race condition for a 404, but that should not take 5min, maybe 30s.
The text was updated successfully, but these errors were encountered:
drastawi
changed the title
Introduce more response code checking and centralize logic for error timeouts duration
Too many unnecessarily long timeouts on known errors
Jul 14, 2022
As a result of #454 running terraform on a project with an error in the config or one that contains a resource that had been manually deleted became extremely slow. The rules for retry are not centralized and vary widely from resource type to resource type.
There is a lot of value in retrying for a long time on 429 but for example, we should not wait 5 min to learn we made a typo or are missing field and get a 400. Sometimes it might be valuable to avoid a race condition for a 404, but that should not take 5min, maybe 30s.
The text was updated successfully, but these errors were encountered: