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

DynamicListener

import type { DynamicListener } from "https://googleapis.deno.dev/v1/trafficdirector:v3.ts";

Describes a dynamically loaded listener via the LDS API. [#next-free-field: 7]

interface DynamicListener {
activeState?: DynamicListenerState;
clientStatus?:
| "UNKNOWN"
| "REQUESTED"
| "DOES_NOT_EXIST"
| "ACKED"
| "NACKED";
drainingState?: DynamicListenerState;
errorState?: UpdateFailureState;
name?: string;
warmingState?: DynamicListenerState;
}

§Properties

§

The listener state for any active listener by this name. These are listeners that are available to service data plane traffic.

§
clientStatus?: "UNKNOWN" | "REQUESTED" | "DOES_NOT_EXIST" | "ACKED" | "NACKED"
[src]

The client status of this resource. [#not-implemented-hide:]

§

The listener state for any draining listener by this name. These are listeners that are currently undergoing draining in preparation to stop servicing data plane traffic. Note that if attempting to recreate an Envoy configuration from a configuration dump, the draining listeners should generally be discarded.

§

Set if the last update failed, cleared after the next successful update. The error_state field contains the rejected version of this particular resource along with the reason and timestamp. For successfully updated or acknowledged resource, this field should be empty.

§
name?: string
[src]

The name or unique id of this listener, pulled from the DynamicListenerState config.

§

The listener state for any warming listener by this name. These are listeners that are currently undergoing warming in preparation to service data plane traffic. Note that if attempting to recreate an Envoy configuration from a configuration dump, the warming listeners should generally be discarded.