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

InterconnectGroupConfiguredTopologyCapabilityIntendedCapabilityBlockers

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

[Output Only] Reasons why configuration.topologyCapability.sla differs from intent.topologyCapability. This list is empty if and only if those are the same.

interface InterconnectGroupConfiguredTopologyCapabilityIntendedCapabilityBlockers {
blockerType?:
| "INCOMPATIBLE_METROS"
| "NOT_AVAILABLE"
| "NO_INTERCONNECTS"
| "NO_INTERCONNECTS_IN_METRO_AND_ZONE"
| "OTHER"
| "UNSPECIFIED";
documentationLink?: string;
explanation?: string;
facilities?: string[];
interconnects?: string[];
metros?: string[];
zones?: string[];
}

§Properties

§
blockerType?: "INCOMPATIBLE_METROS" | "NOT_AVAILABLE" | "NO_INTERCONNECTS" | "NO_INTERCONNECTS_IN_METRO_AND_ZONE" | "OTHER" | "UNSPECIFIED"
[src]
§
explanation?: string
[src]

[Output Only] A human-readable explanation of this requirement and why it's not met. This is set for every type of requirement.

§
facilities?: string[]
[src]

[Output Only] Facilities used to explain this blocker in more detail. Like physicalStructure.metros.facilities.facility, this is a numeric string like "5467".

§
interconnects?: string[]
[src]

[Output Only] Interconnects used to explain this blocker in more detail.

§
metros?: string[]
[src]

[Output Only] Metros used to explain this blocker in more detail. These are three-letter lowercase strings like "iad". A blocker like INCOMPATIBLE_METROS will specify the problematic metros in this field.

§
zones?: string[]
[src]

[Output Only] Zones used to explain this blocker in more detail. Zone names are "zone1" and/or "zone2".