• Home
  • Raw
  • Download

Lines Matching full:partner

132 … attachments of type PARTNER, the Google Partner that is operating the interconnect must set the b…
146 …"dataplaneVersion": 42, # [Output only for types PARTNER and DEDICATED. Not present for …
148PARTNER, at creation time, and can take one of the following values: - AVAILABILITY_DOMAIN_ANY - A…
149 …nterconnectAttachment). Can only be specified at attachment creation for PARTNER or DEDICATED atta…
160PARTNER. Input only for PARTNER_PROVIDER. Not present for DEDICATED]. The opaque identifier of an
161 …or the router supplied by a Layer 3 Partner if they configured BGP on behalf of the customer. Outp…
162Partner attachments from Partners to display to customers. These fields are propagated from PARTNE…
163 …as displayed in the Partner's portal. For instance "Chicago 1". This value may be v…
164 …quot;, # Plain text name of the Partner providing this attachment. This value may be validated to …
165Partner's portal for this Attachment. Partners may customise this to be a deep link to the sp…
175PARTNER, and PARTNER_PROVIDER interconnect attachments, while enum values PENDING_PARTNER, PARTNER…
176PARTNER: an attachment to a Partner Interconnect, created by the customer. - PARTNER_PROVIDER: an …
312 … attachments of type PARTNER, the Google Partner that is operating the interconnect must set the b…
326 …"dataplaneVersion": 42, # [Output only for types PARTNER and DEDICATED. Not present for …
328PARTNER, at creation time, and can take one of the following values: - AVAILABILITY_DOMAIN_ANY - A…
329 …nterconnectAttachment). Can only be specified at attachment creation for PARTNER or DEDICATED atta…
340PARTNER. Input only for PARTNER_PROVIDER. Not present for DEDICATED]. The opaque identifier of an
341 …or the router supplied by a Layer 3 Partner if they configured BGP on behalf of the customer. Outp…
342Partner attachments from Partners to display to customers. These fields are propagated from PARTNE…
343 …as displayed in the Partner's portal. For instance "Chicago 1". This value may be v…
344 …quot;, # Plain text name of the Partner providing this attachment. This value may be validated to …
345Partner's portal for this Attachment. Partners may customise this to be a deep link to the sp…
355PARTNER, and PARTNER_PROVIDER interconnect attachments, while enum values PENDING_PARTNER, PARTNER…
356PARTNER: an attachment to a Partner Interconnect, created by the customer. - PARTNER_PROVIDER: an …
373 … attachments of type PARTNER, the Google Partner that is operating the interconnect must set the b…
387 …"dataplaneVersion": 42, # [Output only for types PARTNER and DEDICATED. Not present for …
389PARTNER, at creation time, and can take one of the following values: - AVAILABILITY_DOMAIN_ANY - A…
390 …nterconnectAttachment). Can only be specified at attachment creation for PARTNER or DEDICATED atta…
401PARTNER. Input only for PARTNER_PROVIDER. Not present for DEDICATED]. The opaque identifier of an
402 …or the router supplied by a Layer 3 Partner if they configured BGP on behalf of the customer. Outp…
403Partner attachments from Partners to display to customers. These fields are propagated from PARTNE…
404 …as displayed in the Partner's portal. For instance "Chicago 1". This value may be v…
405 …quot;, # Plain text name of the Partner providing this attachment. This value may be validated to …
406Partner's portal for this Attachment. Partners may customise this to be a deep link to the sp…
416PARTNER, and PARTNER_PROVIDER interconnect attachments, while enum values PENDING_PARTNER, PARTNER…
417PARTNER: 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…
531PARTNER. Input only for PARTNER_PROVIDER. Not present for DEDICATED]. The opaque identifier of an
532 …or the router supplied by a Layer 3 Partner if they configured BGP on behalf of the customer. Outp…
533Partner attachments from Partners to display to customers. These fields are propagated from PARTNE…
534 …as displayed in the Partner's portal. For instance "Chicago 1". This value may be v…
535 …quot;, # Plain text name of the Partner providing this attachment. This value may be validated to …
536Partner's portal for this Attachment. Partners may customise this to be a deep link to the sp…
546PARTNER, and PARTNER_PROVIDER interconnect attachments, while enum values PENDING_PARTNER, PARTNER…
547PARTNER: an attachment to a Partner Interconnect, created by the customer. - PARTNER_PROVIDER: an …
594 … attachments of type PARTNER, the Google Partner that is operating the interconnect must set the b…
608 …"dataplaneVersion": 42, # [Output only for types PARTNER and DEDICATED. Not present for …
610PARTNER, at creation time, and can take one of the following values: - AVAILABILITY_DOMAIN_ANY - A…
611 …nterconnectAttachment). Can only be specified at attachment creation for PARTNER or DEDICATED atta…
622PARTNER. Input only for PARTNER_PROVIDER. Not present for DEDICATED]. The opaque identifier of an
623 …or the router supplied by a Layer 3 Partner if they configured BGP on behalf of the customer. Outp…
624Partner attachments from Partners to display to customers. These fields are propagated from PARTNE…
625 …as displayed in the Partner's portal. For instance "Chicago 1". This value may be v…
626 …quot;, # Plain text name of the Partner providing this attachment. This value may be validated to …
627Partner's portal for this Attachment. Partners may customise this to be a deep link to the sp…
637PARTNER, and PARTNER_PROVIDER interconnect attachments, while enum values PENDING_PARTNER, PARTNER…
638PARTNER: an attachment to a Partner Interconnect, created by the customer. - PARTNER_PROVIDER: an …