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

ConnectivityTest

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

A Connectivity Test for a network reachability analysis.

interface ConnectivityTest {
bypassFirewallChecks?: boolean;
readonly createTime?: Date;
description?: string;
destination?: Endpoint;
readonly displayName?: string;
labels?: {
[key: string]: string;
}
;
name?: string;
readonly probingDetails?: ProbingDetails;
protocol?: string;
readonly reachabilityDetails?: ReachabilityDetails;
relatedProjects?: string[];
source?: Endpoint;
readonly updateTime?: Date;
}

§Properties

§
bypassFirewallChecks?: boolean
[src]

Whether the test should skip firewall checking. If not provided, we assume false.

§
readonly createTime?: Date
[src]

Output only. The time the test was created.

§
description?: string
[src]

The user-supplied description of the Connectivity Test. Maximum of 512 characters.

§
destination?: Endpoint
[src]

Required. Destination specification of the Connectivity Test. You can use a combination of destination IP address, Compute Engine VM instance, or VPC network to uniquely identify the destination location. Even if the destination IP address is not unique, the source IP location is unique. Usually, the analysis can infer the destination endpoint from route information. If the destination you specify is a VM instance and the instance has multiple network interfaces, then you must also specify either a destination IP address or VPC network to identify the destination interface. A reachability analysis proceeds even if the destination location is ambiguous. However, the result can include endpoints that you don't intend to test.

§
readonly displayName?: string
[src]

Output only. The display name of a Connectivity Test.

§
labels?: {
[key: string]: string;
}
[src]

Resource labels to represent user-provided metadata.

§
name?: string
[src]

Identifier. Unique name of the resource using the form: projects/{project_id}/locations/global/connectivityTests/{test_id}

§
readonly probingDetails?: ProbingDetails
[src]

Output only. The probing details of this test from the latest run, present for applicable tests only. The details are updated when creating a new test, updating an existing test, or triggering a one-time rerun of an existing test.

§
protocol?: string
[src]

IP Protocol of the test. When not provided, "TCP" is assumed.

§
readonly reachabilityDetails?: ReachabilityDetails
[src]

Output only. The reachability details of this test from the latest run. The details are updated when creating a new test, updating an existing test, or triggering a one-time rerun of an existing test.

§
relatedProjects?: string[]
[src]

Other projects that may be relevant for reachability analysis. This is applicable to scenarios where a test can cross project boundaries.

§
source?: Endpoint
[src]

Required. Source specification of the Connectivity Test. You can use a combination of source IP address, virtual machine (VM) instance, or Compute Engine network to uniquely identify the source location. Examples: If the source IP address is an internal IP address within a Google Cloud Virtual Private Cloud (VPC) network, then you must also specify the VPC network. Otherwise, specify the VM instance, which already contains its internal IP address and VPC network information. If the source of the test is within an on-premises network, then you must provide the destination VPC network. If the source endpoint is a Compute Engine VM instance with multiple network interfaces, the instance itself is not sufficient to identify the endpoint. So, you must also specify the source IP address or VPC network. A reachability analysis proceeds even if the source location is ambiguous. However, the test result may include endpoints that you don't intend to test.

§
readonly updateTime?: Date
[src]

Output only. The time the test's configuration was updated.