rate-limiting support

[bmc-msft]

Azure Devops includes rate limits that could be complex to predict in an automated solution. According to the documentation, the endpoints provide headers in responses in the instances that the client has hit a rate limiting threshold.

Is responding to the Retry-After header as discussed as recommendations in the API on the roadmap?

The API uses msrest as an HTTP library, which doesn't appear to support it at this time. Note, much of the Azure SDK uses azure-core which provides Retry-After support.

[suchir001]

Following this one. We're hitting the limits pretty frequently now. At this time I can only introduce random limits between calls myself, but would be great to have the Retry-After header. Is this in the backlog now?