InterconnectAttachmentGroupsOperationalStatusAttachmentStatus
import type { InterconnectAttachmentGroupsOperationalStatusAttachmentStatus } from "https://googleapis.deno.dev/v1/compute:v1.ts";
The status of one Attachment in the group. List order is arbitrary.
interface InterconnectAttachmentGroupsOperationalStatusAttachmentStatus {
adminEnabled?: boolean;
attachment?: string;
isActive?: "ACTIVE" | "INACTIVE" | "UNSPECIFIED";
status?:
} | "ATTACHMENT_STATUS_UNKNOWN"
| "CONNECTION_DISABLED"
| "CONNECTION_DOWN"
| "CONNECTION_UP"
| "DEFUNCT"
| "IPSEC_CONFIGURATION_NEEDED_STATUS"
| "IPSEC_READY_TO_RESUME_FLOW_STATUS"
| "IPV4_DOWN_IPV6_UP"
| "IPV4_UP_IPV6_DOWN"
| "PARTNER_REQUEST_RECEIVED"
| "PENDING_CUSTOMER"
| "PENDING_PARTNER"
| "PROVISIONED"
| "ROUTER_CONFIGURATION_BROKEN"
| "UNPROVISIONED";
§Properties
§
adminEnabled?: boolean
[src]Whether this Attachment is enabled. This becomes false when the customer drains their Attachment.
§
isActive?: "ACTIVE" | "INACTIVE" | "UNSPECIFIED"
[src]Whether this Attachment is participating in the redundant configuration. This will be ACTIVE if and only if the status below is CONNECTION_UP. Any INACTIVE Attachments are excluded from the analysis that generates operational.availabilitySLA.
§
status?: "ATTACHMENT_STATUS_UNKNOWN" | "CONNECTION_DISABLED" | "CONNECTION_DOWN" | "CONNECTION_UP" | "DEFUNCT" | "IPSEC_CONFIGURATION_NEEDED_STATUS" | "IPSEC_READY_TO_RESUME_FLOW_STATUS" | "IPV4_DOWN_IPV6_UP" | "IPV4_UP_IPV6_DOWN" | "PARTNER_REQUEST_RECEIVED" | "PENDING_CUSTOMER" | "PENDING_PARTNER" | "PROVISIONED" | "ROUTER_CONFIGURATION_BROKEN" | "UNPROVISIONED"
[src]Whether this Attachment is active, and if so, whether BGP is up. This is based on the statuses available in the Pantheon UI here: http://google3/java/com/google/cloud/boq/clientapi/gce/hybrid/api/interconnect_models.proto