Required. The resource name of the location to create the new VMware Engine
network in. A VMware Engine network of type
LEGACY is a regional resource, and a VMware
Engine network of type STANDARD is a global resource.
Resource names are schemeless URIs that follow the conventions in
https://cloud.google.com/apis/design/resource_names. For example:
projects/my-project/locations/global
Required. The resource name of the location to create the new VMware Engine
network in. A VMware Engine network of type
LEGACY is a regional resource, and a VMware
Engine network of type STANDARD is a global resource.
Resource names are schemeless URIs that follow the conventions in
https://cloud.google.com/apis/design/resource_names. For example:
projects/my-project/locations/global
Optional. A 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. The server guarantees that a
request doesn't result in creation of duplicate commitments for at least 60
minutes.
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).
Optional. A 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. The server guarantees that a
request doesn't result in creation of duplicate commitments for at least 60
minutes.
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).
Required. The user-provided identifier of the new VMware Engine network.
This identifier must be unique among VMware Engine network resources
within the parent and becomes the final token in the name URI. The
identifier must meet the following requirements:
For networks of type LEGACY, adheres to the format:
{region-id}-default. Replace {region-id} with the region where you want
to create the VMware Engine network. For example, "us-central1-default".
Only contains 1-63 alphanumeric characters and hyphens
Required. The user-provided identifier of the new VMware Engine network.
This identifier must be unique among VMware Engine network resources
within the parent and becomes the final token in the name URI. The
identifier must meet the following requirements:
For networks of type LEGACY, adheres to the format:
{region-id}-default. Replace {region-id} with the region where you want
to create the VMware Engine network. For example, "us-central1-default".
Only contains 1-63 alphanumeric characters and hyphens
[[["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-01-27 UTC."],[],[]]
