You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/dyn/contactcenteraiplatform_v1alpha1.projects.locations.contactCenters.html
+36-56Lines changed: 36 additions & 56 deletions
Original file line number
Diff line number
Diff line change
@@ -157,29 +157,24 @@ <h3>Method Details</h3>
157
157
"egressSettings": [ # List of egress components that should not be accessed via the Internet. For more information see go/ccaip-private-path-v2.
158
158
{ # Defines a logical CCAIP component that e.g. “EMAIL”, "CRM". For more information see go/ccaip-private-path-v2. Each logical component is associated with a list of service attachments.
159
159
"name": "A String", # Name of the component.
160
-
"serviceAttachments": [ # Associated service attachments.
161
-
{ # Container for the VPC-SC networking configurations.
162
-
"allowedProjectIds": [ # The list of project ids that are allowed to send traffic to the service attachment. This field should be filled only for the ingress service attachments.
163
-
"A String",
164
-
],
165
-
"name": "A String", # The service attachment name that will be used for sending private traffic to the CCAIP tenant project. Example: "projects/${TENANT_PROJECT_ID}/regions/${REGION}/serviceAttachments/ingress-default".
166
-
},
160
+
"serviceAttachmentNames": [ # Associated service attachments. The service attachment names that will be used for sending private traffic to the CCAIP tenant project. Example service attachment name: "projects/${TENANT_PROJECT_ID}/regions/${REGION}/serviceAttachments/ingress-default".
161
+
"A String",
167
162
],
168
163
},
169
164
],
170
165
"ingressSettings": [ # List of ingress components that should not be accessed via the Internet. For more information see go/ccaip-private-path-v2.
171
166
{ # Defines a logical CCAIP component that e.g. “EMAIL”, "CRM". For more information see go/ccaip-private-path-v2. Each logical component is associated with a list of service attachments.
172
167
"name": "A String", # Name of the component.
173
-
"serviceAttachments": [ # Associated service attachments.
174
-
{ # Container for the VPC-SC networking configurations.
175
-
"allowedProjectIds": [ # The list of project ids that are allowed to send traffic to the service attachment. This field should be filled only for the ingress service attachments.
176
-
"A String",
177
-
],
178
-
"name": "A String", # The service attachment name that will be used for sending private traffic to the CCAIP tenant project. Example: "projects/${TENANT_PROJECT_ID}/regions/${REGION}/serviceAttachments/ingress-default".
179
-
},
168
+
"serviceAttachmentNames": [ # Associated service attachments. The service attachment names that will be used for sending private traffic to the CCAIP tenant project. Example service attachment name: "projects/${TENANT_PROJECT_ID}/regions/${REGION}/serviceAttachments/ingress-default".
169
+
"A String",
180
170
],
181
171
},
182
172
],
173
+
"pscSetting": { # Private service connect settings. # Private service connect settings.
174
+
"allowedConsumerProjectIds": [ # The list of project ids that are allowed to send traffic to the service attachment. This field should be filled only for the ingress components.
175
+
"A String",
176
+
],
177
+
},
183
178
},
184
179
"privateComponents": [ # Output only. A list of UJET components that should be privately accessed. This field is set by reading settings from the data plane. For more information about the format of the component please refer to go/ccaip-vpc-sc-org-policy. This field is must be fully populated only for Create/Update resource operations. The main use case for this field is OrgPolicy checks via CPE.
185
180
"A String",
@@ -333,29 +328,24 @@ <h3>Method Details</h3>
333
328
"egressSettings": [ # List of egress components that should not be accessed via the Internet. For more information see go/ccaip-private-path-v2.
334
329
{ # Defines a logical CCAIP component that e.g. “EMAIL”, "CRM". For more information see go/ccaip-private-path-v2. Each logical component is associated with a list of service attachments.
335
330
"name": "A String", # Name of the component.
336
-
"serviceAttachments": [ # Associated service attachments.
337
-
{ # Container for the VPC-SC networking configurations.
338
-
"allowedProjectIds": [ # The list of project ids that are allowed to send traffic to the service attachment. This field should be filled only for the ingress service attachments.
339
-
"A String",
340
-
],
341
-
"name": "A String", # The service attachment name that will be used for sending private traffic to the CCAIP tenant project. Example: "projects/${TENANT_PROJECT_ID}/regions/${REGION}/serviceAttachments/ingress-default".
342
-
},
331
+
"serviceAttachmentNames": [ # Associated service attachments. The service attachment names that will be used for sending private traffic to the CCAIP tenant project. Example service attachment name: "projects/${TENANT_PROJECT_ID}/regions/${REGION}/serviceAttachments/ingress-default".
332
+
"A String",
343
333
],
344
334
},
345
335
],
346
336
"ingressSettings": [ # List of ingress components that should not be accessed via the Internet. For more information see go/ccaip-private-path-v2.
347
337
{ # Defines a logical CCAIP component that e.g. “EMAIL”, "CRM". For more information see go/ccaip-private-path-v2. Each logical component is associated with a list of service attachments.
348
338
"name": "A String", # Name of the component.
349
-
"serviceAttachments": [ # Associated service attachments.
350
-
{ # Container for the VPC-SC networking configurations.
351
-
"allowedProjectIds": [ # The list of project ids that are allowed to send traffic to the service attachment. This field should be filled only for the ingress service attachments.
352
-
"A String",
353
-
],
354
-
"name": "A String", # The service attachment name that will be used for sending private traffic to the CCAIP tenant project. Example: "projects/${TENANT_PROJECT_ID}/regions/${REGION}/serviceAttachments/ingress-default".
355
-
},
339
+
"serviceAttachmentNames": [ # Associated service attachments. The service attachment names that will be used for sending private traffic to the CCAIP tenant project. Example service attachment name: "projects/${TENANT_PROJECT_ID}/regions/${REGION}/serviceAttachments/ingress-default".
340
+
"A String",
356
341
],
357
342
},
358
343
],
344
+
"pscSetting": { # Private service connect settings. # Private service connect settings.
345
+
"allowedConsumerProjectIds": [ # The list of project ids that are allowed to send traffic to the service attachment. This field should be filled only for the ingress components.
346
+
"A String",
347
+
],
348
+
},
359
349
},
360
350
"privateComponents": [ # Output only. A list of UJET components that should be privately accessed. This field is set by reading settings from the data plane. For more information about the format of the component please refer to go/ccaip-vpc-sc-org-policy. This field is must be fully populated only for Create/Update resource operations. The main use case for this field is OrgPolicy checks via CPE.
361
351
"A String",
@@ -449,29 +439,24 @@ <h3>Method Details</h3>
449
439
"egressSettings": [ # List of egress components that should not be accessed via the Internet. For more information see go/ccaip-private-path-v2.
450
440
{ # Defines a logical CCAIP component that e.g. “EMAIL”, "CRM". For more information see go/ccaip-private-path-v2. Each logical component is associated with a list of service attachments.
451
441
"name": "A String", # Name of the component.
452
-
"serviceAttachments": [ # Associated service attachments.
453
-
{ # Container for the VPC-SC networking configurations.
454
-
"allowedProjectIds": [ # The list of project ids that are allowed to send traffic to the service attachment. This field should be filled only for the ingress service attachments.
455
-
"A String",
456
-
],
457
-
"name": "A String", # The service attachment name that will be used for sending private traffic to the CCAIP tenant project. Example: "projects/${TENANT_PROJECT_ID}/regions/${REGION}/serviceAttachments/ingress-default".
458
-
},
442
+
"serviceAttachmentNames": [ # Associated service attachments. The service attachment names that will be used for sending private traffic to the CCAIP tenant project. Example service attachment name: "projects/${TENANT_PROJECT_ID}/regions/${REGION}/serviceAttachments/ingress-default".
443
+
"A String",
459
444
],
460
445
},
461
446
],
462
447
"ingressSettings": [ # List of ingress components that should not be accessed via the Internet. For more information see go/ccaip-private-path-v2.
463
448
{ # Defines a logical CCAIP component that e.g. “EMAIL”, "CRM". For more information see go/ccaip-private-path-v2. Each logical component is associated with a list of service attachments.
464
449
"name": "A String", # Name of the component.
465
-
"serviceAttachments": [ # Associated service attachments.
466
-
{ # Container for the VPC-SC networking configurations.
467
-
"allowedProjectIds": [ # The list of project ids that are allowed to send traffic to the service attachment. This field should be filled only for the ingress service attachments.
468
-
"A String",
469
-
],
470
-
"name": "A String", # The service attachment name that will be used for sending private traffic to the CCAIP tenant project. Example: "projects/${TENANT_PROJECT_ID}/regions/${REGION}/serviceAttachments/ingress-default".
471
-
},
450
+
"serviceAttachmentNames": [ # Associated service attachments. The service attachment names that will be used for sending private traffic to the CCAIP tenant project. Example service attachment name: "projects/${TENANT_PROJECT_ID}/regions/${REGION}/serviceAttachments/ingress-default".
451
+
"A String",
472
452
],
473
453
},
474
454
],
455
+
"pscSetting": { # Private service connect settings. # Private service connect settings.
456
+
"allowedConsumerProjectIds": [ # The list of project ids that are allowed to send traffic to the service attachment. This field should be filled only for the ingress components.
457
+
"A String",
458
+
],
459
+
},
475
460
},
476
461
"privateComponents": [ # Output only. A list of UJET components that should be privately accessed. This field is set by reading settings from the data plane. For more information about the format of the component please refer to go/ccaip-vpc-sc-org-policy. This field is must be fully populated only for Create/Update resource operations. The main use case for this field is OrgPolicy checks via CPE.
477
462
"A String",
@@ -574,29 +559,24 @@ <h3>Method Details</h3>
574
559
"egressSettings": [ # List of egress components that should not be accessed via the Internet. For more information see go/ccaip-private-path-v2.
575
560
{ # Defines a logical CCAIP component that e.g. “EMAIL”, "CRM". For more information see go/ccaip-private-path-v2. Each logical component is associated with a list of service attachments.
576
561
"name": "A String", # Name of the component.
577
-
"serviceAttachments": [ # Associated service attachments.
578
-
{ # Container for the VPC-SC networking configurations.
579
-
"allowedProjectIds": [ # The list of project ids that are allowed to send traffic to the service attachment. This field should be filled only for the ingress service attachments.
580
-
"A String",
581
-
],
582
-
"name": "A String", # The service attachment name that will be used for sending private traffic to the CCAIP tenant project. Example: "projects/${TENANT_PROJECT_ID}/regions/${REGION}/serviceAttachments/ingress-default".
583
-
},
562
+
"serviceAttachmentNames": [ # Associated service attachments. The service attachment names that will be used for sending private traffic to the CCAIP tenant project. Example service attachment name: "projects/${TENANT_PROJECT_ID}/regions/${REGION}/serviceAttachments/ingress-default".
563
+
"A String",
584
564
],
585
565
},
586
566
],
587
567
"ingressSettings": [ # List of ingress components that should not be accessed via the Internet. For more information see go/ccaip-private-path-v2.
588
568
{ # Defines a logical CCAIP component that e.g. “EMAIL”, "CRM". For more information see go/ccaip-private-path-v2. Each logical component is associated with a list of service attachments.
589
569
"name": "A String", # Name of the component.
590
-
"serviceAttachments": [ # Associated service attachments.
591
-
{ # Container for the VPC-SC networking configurations.
592
-
"allowedProjectIds": [ # The list of project ids that are allowed to send traffic to the service attachment. This field should be filled only for the ingress service attachments.
593
-
"A String",
594
-
],
595
-
"name": "A String", # The service attachment name that will be used for sending private traffic to the CCAIP tenant project. Example: "projects/${TENANT_PROJECT_ID}/regions/${REGION}/serviceAttachments/ingress-default".
596
-
},
570
+
"serviceAttachmentNames": [ # Associated service attachments. The service attachment names that will be used for sending private traffic to the CCAIP tenant project. Example service attachment name: "projects/${TENANT_PROJECT_ID}/regions/${REGION}/serviceAttachments/ingress-default".
571
+
"A String",
597
572
],
598
573
},
599
574
],
575
+
"pscSetting": { # Private service connect settings. # Private service connect settings.
576
+
"allowedConsumerProjectIds": [ # The list of project ids that are allowed to send traffic to the service attachment. This field should be filled only for the ingress components.
577
+
"A String",
578
+
],
579
+
},
600
580
},
601
581
"privateComponents": [ # Output only. A list of UJET components that should be privately accessed. This field is set by reading settings from the data plane. For more information about the format of the component please refer to go/ccaip-vpc-sc-org-policy. This field is must be fully populated only for Create/Update resource operations. The main use case for this field is OrgPolicy checks via CPE.
"description": "Associated service attachments. The service attachment names that will be used for sending private traffic to the CCAIP tenant project. Example service attachment name: \"projects/${TENANT_PROJECT_ID}/regions/${REGION}/serviceAttachments/ingress-default\".",
549
549
"items": {
550
-
"$ref": "ServiceAttachment"
550
+
"type": "string"
551
551
},
552
552
"type": "array"
553
553
}
@@ -1016,6 +1016,24 @@
1016
1016
"$ref": "Component"
1017
1017
},
1018
1018
"type": "array"
1019
+
},
1020
+
"pscSetting": {
1021
+
"$ref": "PscSetting",
1022
+
"description": "Private service connect settings."
1023
+
}
1024
+
},
1025
+
"type": "object"
1026
+
},
1027
+
"PscSetting": {
1028
+
"description": "Private service connect settings.",
1029
+
"id": "PscSetting",
1030
+
"properties": {
1031
+
"allowedConsumerProjectIds": {
1032
+
"description": "The list of project ids that are allowed to send traffic to the service attachment. This field should be filled only for the ingress components.",
1033
+
"items": {
1034
+
"type": "string"
1035
+
},
1036
+
"type": "array"
1019
1037
}
1020
1038
},
1021
1039
"type": "object"
@@ -1162,24 +1180,6 @@
1162
1180
},
1163
1181
"type": "object"
1164
1182
},
1165
-
"ServiceAttachment": {
1166
-
"description": "Container for the VPC-SC networking configurations.",
1167
-
"id": "ServiceAttachment",
1168
-
"properties": {
1169
-
"allowedProjectIds": {
1170
-
"description": "The list of project ids that are allowed to send traffic to the service attachment. This field should be filled only for the ingress service attachments.",
1171
-
"items": {
1172
-
"type": "string"
1173
-
},
1174
-
"type": "array"
1175
-
},
1176
-
"name": {
1177
-
"description": "The service attachment name that will be used for sending private traffic to the CCAIP tenant project. Example: \"projects/${TENANT_PROJECT_ID}/regions/${REGION}/serviceAttachments/ingress-default\".",
1178
-
"type": "string"
1179
-
}
1180
-
},
1181
-
"type": "object"
1182
-
},
1183
1183
"Status": {
1184
1184
"description": "The `Status` type defines a logical error model that is suitable for different programming environments, including REST APIs and RPC APIs. It is used by [gRPC](https://github.com/grpc). Each `Status` message contains three pieces of data: error code, error message, and error details. You can find out more about this error model and how to work with it in the [API Design Guide](https://cloud.google.com/apis/design/errors).",
0 commit comments