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

PeeringRoute

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

Exchanged network peering route.

interface PeeringRoute {
readonly destRange?: string;
readonly direction?: "DIRECTION_UNSPECIFIED" | "INCOMING" | "OUTGOING";
readonly imported?: boolean;
readonly nextHopRegion?: string;
readonly priority?: bigint;
readonly type?:
| "TYPE_UNSPECIFIED"
| "DYNAMIC_PEERING_ROUTE"
| "STATIC_PEERING_ROUTE"
| "SUBNET_PEERING_ROUTE";
}

§Properties

§
readonly destRange?: string
[src]

Output only. Destination range of the peering route in CIDR notation.

§
readonly direction?: "DIRECTION_UNSPECIFIED" | "INCOMING" | "OUTGOING"
[src]

Output only. Direction of the routes exchanged with the peer network, from the VMware Engine network perspective: * Routes of direction INCOMING are imported from the peer network. * Routes of direction OUTGOING are exported from the intranet VPC network of the VMware Engine network.

§
readonly imported?: boolean
[src]

Output only. True if the peering route has been imported from a peered VPC network; false otherwise. The import happens if the field NetworkPeering.importCustomRoutes is true for this network, NetworkPeering.exportCustomRoutes is true for the peer VPC network, and the import does not result in a route conflict.

§
readonly nextHopRegion?: string
[src]

Output only. Region containing the next hop of the peering route. This field only applies to dynamic routes in the peer VPC network.

§
readonly priority?: bigint
[src]

Output only. The priority of the peering route.

§
readonly type?: "TYPE_UNSPECIFIED" | "DYNAMIC_PEERING_ROUTE" | "STATIC_PEERING_ROUTE" | "SUBNET_PEERING_ROUTE"
[src]

Output only. Type of the route in the peer VPC network.