Hi there! Are you looking for the official Deno documentation? Try docs.deno.com for all your Deno learning needs.

NetworkConfig

import type { NetworkConfig } from "https://googleapis.deno.dev/v1/vmwareengine:v1.ts";

Network configuration in the consumer project with which the peering has to be done.

interface NetworkConfig {
readonly dnsServerIp?: string;
managementCidr?: string;
readonly managementIpAddressLayoutVersion?: number;
vmwareEngineNetwork?: string;
readonly vmwareEngineNetworkCanonical?: string;
}

§Properties

§
readonly dnsServerIp?: string
[src]

Output only. DNS Server IP of the Private Cloud. All DNS queries can be forwarded to this address for name resolution of Private Cloud's management entities like vCenter, NSX-T Manager and ESXi hosts.

§
managementCidr?: string
[src]

Required. Management CIDR used by VMware management appliances.

§
readonly managementIpAddressLayoutVersion?: number
[src]

Output only. The IP address layout version of the management IP address range. Possible versions include: * managementIpAddressLayoutVersion=1: Indicates the legacy IP address layout used by some existing private clouds. This is no longer supported for new private clouds as it does not support all features. * managementIpAddressLayoutVersion=2: Indicates the latest IP address layout used by all newly created private clouds. This version supports all current features.

§
vmwareEngineNetwork?: string
[src]

Optional. The relative resource name of the VMware Engine network attached to the private cloud. Specify the name in the following form: projects/{project}/locations/{location}/vmwareEngineNetworks/{vmware_engine_network_id} where {project} can either be a project number or a project ID.

§
readonly vmwareEngineNetworkCanonical?: string
[src]

Output only. The canonical name of the VMware Engine network in the form: projects/{project_number}/locations/{location}/vmwareEngineNetworks/{vmware_engine_network_id}