Required. Unique id for the policy-based route to create. Provided by the
client when the resource is created. The name must comply with
https://google.aip.dev/122#resource-id-segments. Specifically, the name
must be 1-63 characters long and match the regular expression
a-z?. The first character must be a lowercase letter,
and all following characters (except for the last character) must be a
dash, lowercase letter, or digit. The last character must be a lowercase
letter or digit.
Required. Unique id for the policy-based route to create. Provided by the
client when the resource is created. The name must comply with
https://google.aip.dev/122#resource-id-segments. Specifically, the name
must be 1-63 characters long and match the regular expression
a-z?. The first character must be a lowercase letter,
and all following characters (except for the last character) must be a
dash, lowercase letter, or digit. The last character must be a lowercase
letter or digit.
Optional. An optional request ID to identify requests. Specify a unique
request ID so that if you must retry your request, the server knows to
ignore the request if it has already been completed. The server guarantees
that for at least 60 minutes since the first request.
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, ignores 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).
Optional. An optional request ID to identify requests. Specify a unique
request ID so that if you must retry your request, the server knows to
ignore the request if it has already been completed. The server guarantees
that for at least 60 minutes since the first request.
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, ignores 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).
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-05-15 UTC."],[],[]]