Optional. An optional request ID to identify requests. Specify a unique request ID so that if you must retry your request, the server ignores 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 the 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 ignores 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 the 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).
Returns
Type
Description
string
setRequestId
Optional. An optional request ID to identify requests. Specify a unique
request ID so that if you must retry your request, the server ignores 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 the 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-09-04 UTC."],[],[],null,["# Google Cloud AlloyDB for PostgreSQL V1 Client - Class BatchCreateInstancesRequest (1.4.1)\n\nVersion latestkeyboard_arrow_down\n\n- [1.4.1 (latest)](/php/docs/reference/cloud-alloydb/latest/V1.BatchCreateInstancesRequest)\n- [1.4.0](/php/docs/reference/cloud-alloydb/1.4.0/V1.BatchCreateInstancesRequest)\n- [1.3.0](/php/docs/reference/cloud-alloydb/1.3.0/V1.BatchCreateInstancesRequest)\n- [1.2.0](/php/docs/reference/cloud-alloydb/1.2.0/V1.BatchCreateInstancesRequest)\n- [1.1.3](/php/docs/reference/cloud-alloydb/1.1.3/V1.BatchCreateInstancesRequest)\n- [1.0.0](/php/docs/reference/cloud-alloydb/1.0.0/V1.BatchCreateInstancesRequest)\n- [0.10.3](/php/docs/reference/cloud-alloydb/0.10.3/V1.BatchCreateInstancesRequest)\n- [0.9.0](/php/docs/reference/cloud-alloydb/0.9.0/V1.BatchCreateInstancesRequest)\n- [0.8.0](/php/docs/reference/cloud-alloydb/0.8.0/V1.BatchCreateInstancesRequest)\n- [0.7.1](/php/docs/reference/cloud-alloydb/0.7.1/V1.BatchCreateInstancesRequest)\n- [0.6.0](/php/docs/reference/cloud-alloydb/0.6.0/V1.BatchCreateInstancesRequest)\n- [0.5.0](/php/docs/reference/cloud-alloydb/0.5.0/V1.BatchCreateInstancesRequest)\n- [0.4.0](/php/docs/reference/cloud-alloydb/0.4.0/V1.BatchCreateInstancesRequest)\n- [0.3.0](/php/docs/reference/cloud-alloydb/0.3.0/V1.BatchCreateInstancesRequest)\n- [0.2.1](/php/docs/reference/cloud-alloydb/0.2.1/V1.BatchCreateInstancesRequest)\n- [0.1.3](/php/docs/reference/cloud-alloydb/0.1.3/V1.BatchCreateInstancesRequest) \nReference documentation and code samples for the Google Cloud AlloyDB for PostgreSQL V1 Client class BatchCreateInstancesRequest.\n\nMessage for creating a batch of instances under the specified cluster.\n\nGenerated from protobuf message `google.cloud.alloydb.v1.BatchCreateInstancesRequest`\n\nNamespace\n---------\n\nGoogle \\\\ Cloud \\\\ AlloyDb \\\\ V1\n\nMethods\n-------\n\n### __construct\n\nConstructor.\n\n### getParent\n\nRequired. The name of the parent resource.\n\n### setParent\n\nRequired. The name of the parent resource.\n\n### getRequests\n\nRequired. Resources being created.\n\n### hasRequests\n\n### clearRequests\n\n### setRequests\n\nRequired. Resources being created.\n\n### getRequestId\n\nOptional. An optional request ID to identify requests. Specify a unique\nrequest ID so that if you must retry your request, the server ignores the\nrequest if it has already been completed. The server guarantees that for at\nleast 60 minutes since the first request.\n\nFor example, consider a situation where you make an initial request and\nthe request times out. If you make the request again with the same request\nID, the server can check if the original operation with the same request ID\nwas received, and if so, ignores the second request. This prevents\nclients from accidentally creating duplicate commitments.\nThe request ID must be a valid UUID with the exception that zero UUID is\nnot supported (00000000-0000-0000-0000-000000000000).\n\n### setRequestId\n\nOptional. An optional request ID to identify requests. Specify a unique\nrequest ID so that if you must retry your request, the server ignores the\nrequest if it has already been completed. The server guarantees that for at\nleast 60 minutes since the first request.\n\nFor example, consider a situation where you make an initial request and\nthe request times out. If you make the request again with the same request\nID, the server can check if the original operation with the same request ID\nwas received, and if so, ignores the second request. This prevents\nclients from accidentally creating duplicate commitments.\nThe request ID must be a valid UUID with the exception that zero UUID is\nnot supported (00000000-0000-0000-0000-000000000000)."]]
