• Home
  • Raw
  • Download

Lines Matching full:partner

144 … attachments of type PARTNER, the Google Partner that is operating the interconnect must set the b…
158 …"dataplaneVersion": 42, # [Output only for types PARTNER and DEDICATED. Not present for …
160PARTNER, at creation time, and can take one of the following values: - AVAILABILITY_DOMAIN_ANY - A…
161 …nterconnectAttachment). Can only be specified at attachment creation for PARTNER or DEDICATED atta…
176PARTNER. Input only for PARTNER_PROVIDER. Not present for DEDICATED]. The opaque identifier of an
177 …or the router supplied by a Layer 3 Partner if they configured BGP on behalf of the customer. Outp…
178Partner attachments from Partners to display to customers. These fields are propagated from PARTNE…
179 …as displayed in the Partner's portal. For instance "Chicago 1". This value may be v…
180 …quot;, # Plain text name of the Partner providing this attachment. This value may be validated to …
181Partner's portal for this Attachment. Partners may customise this to be a deep link to the sp…
192PARTNER, and PARTNER_PROVIDER interconnect attachments, while enum values PENDING_PARTNER, PARTNER…
193PARTNER: an attachment to a Partner Interconnect, created by the customer. - PARTNER_PROVIDER: an …
333 … attachments of type PARTNER, the Google Partner that is operating the interconnect must set the b…
347 …"dataplaneVersion": 42, # [Output only for types PARTNER and DEDICATED. Not present for …
349PARTNER, at creation time, and can take one of the following values: - AVAILABILITY_DOMAIN_ANY - A…
350 …nterconnectAttachment). Can only be specified at attachment creation for PARTNER or DEDICATED atta…
365PARTNER. Input only for PARTNER_PROVIDER. Not present for DEDICATED]. The opaque identifier of an
366 …or the router supplied by a Layer 3 Partner if they configured BGP on behalf of the customer. Outp…
367Partner attachments from Partners to display to customers. These fields are propagated from PARTNE…
368 …as displayed in the Partner's portal. For instance "Chicago 1". This value may be v…
369 …quot;, # Plain text name of the Partner providing this attachment. This value may be validated to …
370Partner's portal for this Attachment. Partners may customise this to be a deep link to the sp…
381PARTNER, and PARTNER_PROVIDER interconnect attachments, while enum values PENDING_PARTNER, PARTNER…
382PARTNER: an attachment to a Partner Interconnect, created by the customer. - PARTNER_PROVIDER: an …
503 … attachments of type PARTNER, the Google Partner that is operating the interconnect must set the b…
517 …"dataplaneVersion": 42, # [Output only for types PARTNER and DEDICATED. Not present for …
519PARTNER, at creation time, and can take one of the following values: - AVAILABILITY_DOMAIN_ANY - A…
520 …nterconnectAttachment). Can only be specified at attachment creation for PARTNER or DEDICATED atta…
535PARTNER. Input only for PARTNER_PROVIDER. Not present for DEDICATED]. The opaque identifier of an
536 …or the router supplied by a Layer 3 Partner if they configured BGP on behalf of the customer. Outp…
537Partner attachments from Partners to display to customers. These fields are propagated from PARTNE…
538 …as displayed in the Partner's portal. For instance "Chicago 1". This value may be v…
539 …quot;, # Plain text name of the Partner providing this attachment. This value may be validated to …
540Partner's portal for this Attachment. Partners may customise this to be a deep link to the sp…
551PARTNER, and PARTNER_PROVIDER interconnect attachments, while enum values PENDING_PARTNER, PARTNER…
552PARTNER: an attachment to a Partner Interconnect, created by the customer. - PARTNER_PROVIDER: an …
642 … attachments of type PARTNER, the Google Partner that is operating the interconnect must set the b…
656 …"dataplaneVersion": 42, # [Output only for types PARTNER and DEDICATED. Not present for …
658PARTNER, at creation time, and can take one of the following values: - AVAILABILITY_DOMAIN_ANY - A…
659 …nterconnectAttachment). Can only be specified at attachment creation for PARTNER or DEDICATED atta…
674PARTNER. Input only for PARTNER_PROVIDER. Not present for DEDICATED]. The opaque identifier of an
675 …or the router supplied by a Layer 3 Partner if they configured BGP on behalf of the customer. Outp…
676Partner attachments from Partners to display to customers. These fields are propagated from PARTNE…
677 …as displayed in the Partner's portal. For instance "Chicago 1". This value may be v…
678 …quot;, # Plain text name of the Partner providing this attachment. This value may be validated to …
679Partner's portal for this Attachment. Partners may customise this to be a deep link to the sp…
690PARTNER, and PARTNER_PROVIDER interconnect attachments, while enum values PENDING_PARTNER, PARTNER…
691PARTNER: an attachment to a Partner Interconnect, created by the customer. - PARTNER_PROVIDER: an …
738 … attachments of type PARTNER, the Google Partner that is operating the interconnect must set the b…
752 …"dataplaneVersion": 42, # [Output only for types PARTNER and DEDICATED. Not present for …
754PARTNER, at creation time, and can take one of the following values: - AVAILABILITY_DOMAIN_ANY - A…
755 …nterconnectAttachment). Can only be specified at attachment creation for PARTNER or DEDICATED atta…
770PARTNER. Input only for PARTNER_PROVIDER. Not present for DEDICATED]. The opaque identifier of an
771 …or the router supplied by a Layer 3 Partner if they configured BGP on behalf of the customer. Outp…
772Partner attachments from Partners to display to customers. These fields are propagated from PARTNE…
773 …as displayed in the Partner's portal. For instance "Chicago 1". This value may be v…
774 …quot;, # Plain text name of the Partner providing this attachment. This value may be validated to …
775Partner's portal for this Attachment. Partners may customise this to be a deep link to the sp…
786PARTNER, and PARTNER_PROVIDER interconnect attachments, while enum values PENDING_PARTNER, PARTNER…
787PARTNER: an attachment to a Partner Interconnect, created by the customer. - PARTNER_PROVIDER: an …