Reference documentation and code samples for the Compute Engine v1 API enum InterconnectAttachment.Types.State.
[Output Only] The current state of this attachment's functionality. Enum values ACTIVE and UNPROVISIONED are shared by DEDICATED/PRIVATE, PARTNER, and PARTNER_PROVIDER interconnect attachments, while enum values PENDING_PARTNER, PARTNER_REQUEST_RECEIVED, and PENDING_CUSTOMER are used for only PARTNER and PARTNER_PROVIDER interconnect attachments. This state can take one of the following values: - ACTIVE: The attachment has been turned up and is ready to use. - UNPROVISIONED: The attachment is not ready to use yet, because turnup is not complete. - PENDING_PARTNER: A newly-created PARTNER attachment that has not yet been configured on the Partner side. - PARTNER_REQUEST_RECEIVED: A PARTNER attachment is in the process of provisioning after a PARTNER_PROVIDER attachment was created that references it. - PENDING_CUSTOMER: A PARTNER or PARTNER_PROVIDER attachment that is waiting for a customer to activate it. - DEFUNCT: The attachment was deleted externally and is no longer functional. This could be because the associated Interconnect was removed, or because the other side of a Partner attachment was deleted.
Indicates that attachment has been turned up and is ready to use.
Defunct
The attachment was deleted externally and is no longer functional. This could be because the associated Interconnect was wiped out, or because the other side of a Partner attachment was deleted.
PartnerRequestReceived
A PARTNER attachment is in the process of provisioning after a PARTNER_PROVIDER attachment was created that references it.
PendingCustomer
PARTNER or PARTNER_PROVIDER attachment that is waiting for the customer to activate.
PendingPartner
A newly created PARTNER attachment that has not yet been configured on the Partner side.
UndefinedState
A value indicating that the enum field is not set.
Unprovisioned
Indicates that attachment is not ready to use yet, because turnup is not complete.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-08 UTC."],[[["\u003cp\u003eThe latest version available for \u003ccode\u003eInterconnectAttachment.Types.State\u003c/code\u003e is 3.6.0, with a range of versions available from 1.0.0 to 3.6.0.\u003c/p\u003e\n"],["\u003cp\u003e\u003ccode\u003eInterconnectAttachment.Types.State\u003c/code\u003e within the Compute Engine v1 API contains different states, like \u003ccode\u003eActive\u003c/code\u003e, \u003ccode\u003eUnprovisioned\u003c/code\u003e, \u003ccode\u003ePendingPartner\u003c/code\u003e, \u003ccode\u003ePartnerRequestReceived\u003c/code\u003e, \u003ccode\u003ePendingCustomer\u003c/code\u003e, and \u003ccode\u003eDefunct\u003c/code\u003e.\u003c/p\u003e\n"],["\u003cp\u003eThese states describe the current functionality of an interconnect attachment, which can range from being fully operational (\u003ccode\u003eActive\u003c/code\u003e) to not yet ready for use (\u003ccode\u003eUnprovisioned\u003c/code\u003e) or deleted externally (\u003ccode\u003eDefunct\u003c/code\u003e).\u003c/p\u003e\n"],["\u003cp\u003eThe \u003ccode\u003eGoogle.Cloud.Compute.V1\u003c/code\u003e namespace provides access to the \u003ccode\u003eInterconnectAttachment.Types.State\u003c/code\u003e enum.\u003c/p\u003e\n"],["\u003cp\u003eThere are also states that are specific to PARTNER or PARTNER_PROVIDER interconnect attachments, such as \u003ccode\u003ePendingPartner\u003c/code\u003e, \u003ccode\u003ePartnerRequestReceived\u003c/code\u003e, and \u003ccode\u003ePendingCustomer\u003c/code\u003e.\u003c/p\u003e\n"]]],[],null,[]]
