Desired availability domain for the attachment. Only available for type PARTNER, at creation time, and can take one of the following values: - AVAILABILITY_DOMAIN_ANY - AVAILABILITY_DOMAIN_1 - AVAILABILITY_DOMAIN_2 For improved reliability, customers should configure a pair of attachments, one per availability domain. The selected availability domain will be provided to the Partner via the pairing key, so that the provisioned circuit will lie in the specified domain. If not specified, the value will default to AVAILABILITY_DOMAIN_ANY.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-03-24 UTC."],[[["This page details the `EdgeAvailabilityDomain` enum within the `Google.Cloud.Compute.V1` namespace, specifically for Interconnect Attachments."],["The latest version for this information is 3.6.0, but it also includes documentation for version ranges from 1.0.0 to 3.6.0."],["The `EdgeAvailabilityDomain` can be set to `AVAILABILITY_DOMAIN_ANY`, `AVAILABILITY_DOMAIN_1`, or `AVAILABILITY_DOMAIN_2` when creating `PARTNER` type attachments."],["The enum includes fields such as `AvailabilityDomain1`, `AvailabilityDomain2`, `AvailabilityDomainAny`, and `UndefinedEdgeAvailabilityDomain`."],["Customers are encouraged to create a pair of attachments, each within a different availability domain, to enhance reliability."]]],[]]
