Change Details

Wrap gRPC Get handler message response into a function because the same logic exists for sending a response on a new message from AMQP and database. We don't need to repeat this part of the code and must wrap it into a reusable function. As this part is for Get handler specific, there is no reason to make this a separate class `private` function. We can move it to internal lambda. Linear task: ENG-1043

Wrap gRPC Get handler message response into a function because the same logic exists for sending a response on a new message from AMQP and database. We don't need to repeat this part of the code and must wrap it into a reusable function. As this part is for Get handler specific, there is no reason to make this a separate class `private` function. We can move it to internal lambda. Linear task: [[ https://linear.app/comm/issue/ENG-1043/wrap-grpc-message-response-into-a-function-in-tunnelbroker | ENG-1043 ]]

Wrap gRPC Get handler message response into a function because the same logic exists for sending a response on a new message from AMQP and database. We don't need to repeat this part of the code and must wrap it into a reusable function. As this part is for Get handler specific, there is no reason to make this a separate class `private` function. We can move it to internal lambda. Linear task: [[ https://linear.app/comm/issue/ENG-1043/wrap-grpc-message-response-into-a-function-in-tunnelbroker | ENG-1043 ]]