Properly support 429 and backoff if received
Currently, 429 is handled as any other status code. We should make all our API calls to be intelligent, maybe pipelined to properly support 429 and backoff when we have higher error rate.
Do not update/delete: Banner broadcast message test data
Do not update/delete: Notification broadcast message test data
Currently, 429 is handled as any other status code. We should make all our API calls to be intelligent, maybe pipelined to properly support 429 and backoff when we have higher error rate.
changed milestone to %v9.2
added Deliverable GitLab API improvement labels
assigned to @tmaczukin
mentioned in merge request !570 (merged)
changed milestone to %9.3
closed via merge request !570 (merged)