Misleading error log on 429 errors from registry #3932
Labels
bug
Something isn't working
contributions-requested
Requesting contributions from the community
preserved
Preserved issues never go stale
Hey,
Recently we have been throttled by hashicorp registry (As we confirmed by talking with their support)
But it was impossible to understand from our error logs (even when enabling debug)
we are running terragrunt plan commands on high scale and this is the error log that we got:
the error here has not information about rate-limiting or the status code of 429, and makes it much harder to recognize and troubleshoot
we saw this error message due to this code:
https://github.com/gruntwork-io/terragrunt/blob/main/tf/cache/services/provider_cache.go#L218-L236
it doesnt say anything about being 429 and without hashicorp support we wouldn't understand this.
Steps To Reproduce
Get 429 from hashicorp (as their support states - something around 3000 requests in 5 minutes is enough to get 429 error)
also, have terragrunt use their caching mechanism:
0.69.9 and 0.71.1 - its the same error message.
Expected behavior
We want a clear message that says - 429 Rate-limiting just like it would say if we would use terraform.
Versions
The text was updated successfully, but these errors were encountered: