• Home
  • Raw
  • Download

Lines Matching full:partner

138 … attachments of type PARTNER, the Google Partner that is operating the interconnect must set the b…
152 …"dataplaneVersion": 42, # [Output only for types PARTNER and DEDICATED. Not present for …
154PARTNER, at creation time, and can take one of the following values: - AVAILABILITY_DOMAIN_ANY - A…
155 …nterconnectAttachment). Can only be specified at attachment creation for PARTNER or DEDICATED atta…
170PARTNER. Input only for PARTNER_PROVIDER. Not present for DEDICATED]. The opaque identifier of an
171 …or the router supplied by a Layer 3 Partner if they configured BGP on behalf of the customer. Outp…
172Partner attachments from Partners to display to customers. These fields are propagated from PARTNE…
173 …as displayed in the Partner's portal. For instance "Chicago 1". This value may be v…
174 …quot;, # Plain text name of the Partner providing this attachment. This value may be validated to …
175Partner's portal for this Attachment. Partners may customise this to be a deep link to the sp…
185PARTNER, and PARTNER_PROVIDER interconnect attachments, while enum values PENDING_PARTNER, PARTNER…
186PARTNER: an attachment to a Partner Interconnect, created by the customer. - PARTNER_PROVIDER: an …
322 … attachments of type PARTNER, the Google Partner that is operating the interconnect must set the b…
336 …"dataplaneVersion": 42, # [Output only for types PARTNER and DEDICATED. Not present for …
338PARTNER, at creation time, and can take one of the following values: - AVAILABILITY_DOMAIN_ANY - A…
339 …nterconnectAttachment). Can only be specified at attachment creation for PARTNER or DEDICATED atta…
354PARTNER. Input only for PARTNER_PROVIDER. Not present for DEDICATED]. The opaque identifier of an
355 …or the router supplied by a Layer 3 Partner if they configured BGP on behalf of the customer. Outp…
356Partner attachments from Partners to display to customers. These fields are propagated from PARTNE…
357 …as displayed in the Partner's portal. For instance "Chicago 1". This value may be v…
358 …quot;, # Plain text name of the Partner providing this attachment. This value may be validated to …
359Partner's portal for this Attachment. Partners may customise this to be a deep link to the sp…
369PARTNER, and PARTNER_PROVIDER interconnect attachments, while enum values PENDING_PARTNER, PARTNER…
370PARTNER: an attachment to a Partner Interconnect, created by the customer. - PARTNER_PROVIDER: an …
387 … attachments of type PARTNER, the Google Partner that is operating the interconnect must set the b…
401 …"dataplaneVersion": 42, # [Output only for types PARTNER and DEDICATED. Not present for …
403PARTNER, at creation time, and can take one of the following values: - AVAILABILITY_DOMAIN_ANY - A…
404 …nterconnectAttachment). Can only be specified at attachment creation for PARTNER or DEDICATED atta…
419PARTNER. Input only for PARTNER_PROVIDER. Not present for DEDICATED]. The opaque identifier of an
420 …or the router supplied by a Layer 3 Partner if they configured BGP on behalf of the customer. Outp…
421Partner attachments from Partners to display to customers. These fields are propagated from PARTNE…
422 …as displayed in the Partner's portal. For instance "Chicago 1". This value may be v…
423 …quot;, # Plain text name of the Partner providing this attachment. This value may be validated to …
424Partner's portal for this Attachment. Partners may customise this to be a deep link to the sp…
434PARTNER, and PARTNER_PROVIDER interconnect attachments, while enum values PENDING_PARTNER, PARTNER…
435PARTNER: an attachment to a Partner Interconnect, created by the customer. - PARTNER_PROVIDER: an …
521 … attachments of type PARTNER, the Google Partner that is operating the interconnect must set the b…
535 …"dataplaneVersion": 42, # [Output only for types PARTNER and DEDICATED. Not present for …
537PARTNER, at creation time, and can take one of the following values: - AVAILABILITY_DOMAIN_ANY - A…
538 …nterconnectAttachment). Can only be specified at attachment creation for PARTNER or DEDICATED atta…
553PARTNER. Input only for PARTNER_PROVIDER. Not present for DEDICATED]. The opaque identifier of an
554 …or the router supplied by a Layer 3 Partner if they configured BGP on behalf of the customer. Outp…
555Partner attachments from Partners to display to customers. These fields are propagated from PARTNE…
556 …as displayed in the Partner's portal. For instance "Chicago 1". This value may be v…
557 …quot;, # Plain text name of the Partner providing this attachment. This value may be validated to …
558Partner's portal for this Attachment. Partners may customise this to be a deep link to the sp…
568PARTNER, and PARTNER_PROVIDER interconnect attachments, while enum values PENDING_PARTNER, PARTNER…
569PARTNER: an attachment to a Partner Interconnect, created by the customer. - PARTNER_PROVIDER: an …
616 … attachments of type PARTNER, the Google Partner that is operating the interconnect must set the b…
630 …"dataplaneVersion": 42, # [Output only for types PARTNER and DEDICATED. Not present for …
632PARTNER, at creation time, and can take one of the following values: - AVAILABILITY_DOMAIN_ANY - A…
633 …nterconnectAttachment). Can only be specified at attachment creation for PARTNER or DEDICATED atta…
648PARTNER. Input only for PARTNER_PROVIDER. Not present for DEDICATED]. The opaque identifier of an
649 …or the router supplied by a Layer 3 Partner if they configured BGP on behalf of the customer. Outp…
650Partner attachments from Partners to display to customers. These fields are propagated from PARTNE…
651 …as displayed in the Partner's portal. For instance "Chicago 1". This value may be v…
652 …quot;, # Plain text name of the Partner providing this attachment. This value may be validated to …
653Partner's portal for this Attachment. Partners may customise this to be a deep link to the sp…
663PARTNER, and PARTNER_PROVIDER interconnect attachments, while enum values PENDING_PARTNER, PARTNER…
664PARTNER: an attachment to a Partner Interconnect, created by the customer. - PARTNER_PROVIDER: an …