Lines Matching full:partner
151 … attachments of type PARTNER, the Google Partner that is operating the interconnect must set the b…
169 …PARTNER. Input only for PARTNER_PROVIDER. Not present for DEDICATED]. The opaque identifier of an …
170 …PARTNER, and PARTNER_PROVIDER interconnect attachments, while enum values PENDING_PARTNER, PARTNER…
173 …# - PENDING_PARTNER: A newly-created PARTNER attachment that has not yet been configured on the Pa…
174 …# - PARTNER_REQUEST_RECEIVED: A PARTNER attachment is in the process of provisioning after a PARTN…
175 …# - PENDING_CUSTOMER: A PARTNER or PARTNER_PROVIDER attachment that is waiting for a customer to a…
176 … the associated Interconnect was removed, or because the other side of a Partner attachment was de…
177 …Partner attachments from Partners to display to customers. These fields are propagated from PARTNE…
178 …ring", # Plain text name of the Partner providing this attachment. This value may be validated to …
179 …ted to, as displayed in the Partner?s portal. For instance "Chicago 1". This value may be validate…
180 …Partner?s portal for this Attachment. Partners may customise this to be a deep link to the specifi…
184 # - PARTNER: an attachment to a Partner Interconnect, created by the customer.
185 … # - PARTNER_PROVIDER: an attachment to a Partner Interconnect, created by the partner.
186 …or the router supplied by a Layer 3 Partner if they configured BGP on behalf of the customer. Outp…
203 … Desired availability domain for the attachment. Only available for type PARTNER, at creation time…
206 …ability domain. The selected availability domain will be provided to the Partner via the pairing k…
348 … attachments of type PARTNER, the Google Partner that is operating the interconnect must set the b…
366 …PARTNER. Input only for PARTNER_PROVIDER. Not present for DEDICATED]. The opaque identifier of an …
367 …PARTNER, and PARTNER_PROVIDER interconnect attachments, while enum values PENDING_PARTNER, PARTNER…
370 …# - PENDING_PARTNER: A newly-created PARTNER attachment that has not yet been configured on the Pa…
371 …# - PARTNER_REQUEST_RECEIVED: A PARTNER attachment is in the process of provisioning after a PARTN…
372 …# - PENDING_CUSTOMER: A PARTNER or PARTNER_PROVIDER attachment that is waiting for a customer to a…
373 … the associated Interconnect was removed, or because the other side of a Partner attachment was de…
374 …Partner attachments from Partners to display to customers. These fields are propagated from PARTNE…
375 …ring", # Plain text name of the Partner providing this attachment. This value may be validated to …
376 …ted to, as displayed in the Partner?s portal. For instance "Chicago 1". This value may be validate…
377 …Partner?s portal for this Attachment. Partners may customise this to be a deep link to the specifi…
381 # - PARTNER: an attachment to a Partner Interconnect, created by the customer.
382 # - PARTNER_PROVIDER: an attachment to a Partner Interconnect, created by the partner.
383 …or the router supplied by a Layer 3 Partner if they configured BGP on behalf of the customer. Outp…
400 … Desired availability domain for the attachment. Only available for type PARTNER, at creation time…
403 …ability domain. The selected availability domain will be provided to the Partner via the pairing k…
579 … attachments of type PARTNER, the Google Partner that is operating the interconnect must set the b…
597 …PARTNER. Input only for PARTNER_PROVIDER. Not present for DEDICATED]. The opaque identifier of an …
598 …PARTNER, and PARTNER_PROVIDER interconnect attachments, while enum values PENDING_PARTNER, PARTNER…
601 …# - PENDING_PARTNER: A newly-created PARTNER attachment that has not yet been configured on the Pa…
602 …# - PARTNER_REQUEST_RECEIVED: A PARTNER attachment is in the process of provisioning after a PARTN…
603 …# - PENDING_CUSTOMER: A PARTNER or PARTNER_PROVIDER attachment that is waiting for a customer to a…
604 … the associated Interconnect was removed, or because the other side of a Partner attachment was de…
605 …Partner attachments from Partners to display to customers. These fields are propagated from PARTNE…
606 …ring", # Plain text name of the Partner providing this attachment. This value may be validated to …
607 …ted to, as displayed in the Partner?s portal. For instance "Chicago 1". This value may be validate…
608 …Partner?s portal for this Attachment. Partners may customise this to be a deep link to the specifi…
612 # - PARTNER: an attachment to a Partner Interconnect, created by the customer.
613 # - PARTNER_PROVIDER: an attachment to a Partner Interconnect, created by the partner.
614 …or the router supplied by a Layer 3 Partner if they configured BGP on behalf of the customer. Outp…
631 … Desired availability domain for the attachment. Only available for type PARTNER, at creation time…
634 …ability domain. The selected availability domain will be provided to the Partner via the pairing k…
743 … attachments of type PARTNER, the Google Partner that is operating the interconnect must set the b…
761 …PARTNER. Input only for PARTNER_PROVIDER. Not present for DEDICATED]. The opaque identifier of an …
762 …PARTNER, and PARTNER_PROVIDER interconnect attachments, while enum values PENDING_PARTNER, PARTNER…
765 …# - PENDING_PARTNER: A newly-created PARTNER attachment that has not yet been configured on the Pa…
766 …# - PARTNER_REQUEST_RECEIVED: A PARTNER attachment is in the process of provisioning after a PARTN…
767 …# - PENDING_CUSTOMER: A PARTNER or PARTNER_PROVIDER attachment that is waiting for a customer to a…
768 … the associated Interconnect was removed, or because the other side of a Partner attachment was de…
769 …Partner attachments from Partners to display to customers. These fields are propagated from PARTNE…
770 …ring", # Plain text name of the Partner providing this attachment. This value may be validated to …
771 …ted to, as displayed in the Partner?s portal. For instance "Chicago 1". This value may be validate…
772 …Partner?s portal for this Attachment. Partners may customise this to be a deep link to the specifi…
776 # - PARTNER: an attachment to a Partner Interconnect, created by the customer.
777 # - PARTNER_PROVIDER: an attachment to a Partner Interconnect, created by the partner.
778 …or the router supplied by a Layer 3 Partner if they configured BGP on behalf of the customer. Outp…
795 … Desired availability domain for the attachment. Only available for type PARTNER, at creation time…
798 …ability domain. The selected availability domain will be provided to the Partner via the pairing k…
852 … attachments of type PARTNER, the Google Partner that is operating the interconnect must set the b…
870 …PARTNER. Input only for PARTNER_PROVIDER. Not present for DEDICATED]. The opaque identifier of an …
871 …PARTNER, and PARTNER_PROVIDER interconnect attachments, while enum values PENDING_PARTNER, PARTNER…
874 …# - PENDING_PARTNER: A newly-created PARTNER attachment that has not yet been configured on the Pa…
875 …# - PARTNER_REQUEST_RECEIVED: A PARTNER attachment is in the process of provisioning after a PARTN…
876 …# - PENDING_CUSTOMER: A PARTNER or PARTNER_PROVIDER attachment that is waiting for a customer to a…
877 … the associated Interconnect was removed, or because the other side of a Partner attachment was de…
878 …Partner attachments from Partners to display to customers. These fields are propagated from PARTNE…
879 …ring", # Plain text name of the Partner providing this attachment. This value may be validated to …
880 …ted to, as displayed in the Partner?s portal. For instance "Chicago 1". This value may be validate…
881 …Partner?s portal for this Attachment. Partners may customise this to be a deep link to the specifi…
885 # - PARTNER: an attachment to a Partner Interconnect, created by the customer.
886 # - PARTNER_PROVIDER: an attachment to a Partner Interconnect, created by the partner.
887 …or the router supplied by a Layer 3 Partner if they configured BGP on behalf of the customer. Outp…
904 … Desired availability domain for the attachment. Only available for type PARTNER, at creation time…
907 …ability domain. The selected availability domain will be provided to the Partner via the pairing k…