Skip to content

fix: use UUID instead of base64 string as request id

Sylvester Chin requested to merge sc1-fix-request-uuid into main

What

This MR fixes the request ID to be a UUID string instead of base64 as it is a requirement for the googleapi.

RequestID needs to be a UUID string: lifted from code comment // An optional request ID to identify requests. Specify a unique request ID so that if you must retry your request, the server will know to ignore the request if it has already been completed. For example, consider a situation where you make an initial request and the request times out. If you make the request again with the same request ID, the server can check if original operation with the same request ID was received, and if so, will ignore the second request. This prevents clients from accidentally creating duplicate commitments. The request ID must be a valid UUID with the exception that zero UUID is not supported ( 00000000-0000-0000-0000-000000000000).

Why

team#357 (closed)

Edited by Sylvester Chin

Merge request reports

Loading