429 TooManyRequests exception handling
Type of change
-
Bug Fix
Gitlab issue
Does this introduce a change in the core logic?
- [NO]
Does this introduce a change in the cloud provider implementation, if so which cloud?
-
Azure
Does this introduce a breaking change?
- [NO]
What is the current behavior?
Search returns 500 when Elastic returns 429 (Too Many Requests)
What is the new/expected behavior?
Search service returns a 429 when Elastic returns a 429 (Too Many Requests)
Have you added/updated Unit Tests and Integration Tests?
Yes, added the unit test