Currently fleet-server responds with a 429 and a JSON response by if the OpAMP endpoint is throttled.
We should change the response body to be a protobuf body with ServerErrorResponse.type: UNAVAILABLE and RetryInfo set to other clients can properly interpret the response
Currently fleet-server responds with a 429 and a JSON response by if the OpAMP endpoint is throttled.
We should change the response body to be a protobuf body with
ServerErrorResponse.type: UNAVAILABLEand RetryInfo set to other clients can properly interpret the response