Class CreateVmwareEngineNetworkRequest (1.7.0)

Version latest

• 1.7.0 (latest)
• 1.6.1
• 1.5.0
• 1.4.4
• 1.3.0
• 1.2.0
• 1.1.1
• 1.0.1
• 0.2.2
• 0.1.1

CreateVmwareEngineNetworkRequest(
    mapping=None, *, ignore_unknown_fields=False, **kwargs
)

Request message for VmwareEngine.CreateVmwareEngineNetwork

Attributes
Name	Description
parent	str 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
vmware_engine_network_id	str 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 - Begins with an alphabetical character - Ends with a non-hyphen character - Not formatted as a UUID - Complies with `RFC 1034
vmware_engine_network	google.cloud.vmwareengine_v1.types.VmwareEngineNetwork Required. The initial description of the new VMware Engine network.
request_id	str 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).