google-api-python-client 2.110.0__py2.py3-none-any.whl → 2.111.0__py2.py3-none-any.whl

googleapiclient/discovery_cache/documents/cloudkms.v1.json

@@ -1828,7 +1828,7 @@
       }
     }
   },
-  "revision": "20231109",
+  "revision": "20231130",
   "rootUrl": "https://cloudkms.googleapis.com/",
   "schemas": {
     "AsymmetricDecryptRequest": {

googleapiclient/discovery_cache/documents/cloudprofiler.v2.json

@@ -216,7 +216,7 @@
       }
     }
   },
-  "revision": "20231127",
+  "revision": "20231205",
   "rootUrl": "https://cloudprofiler.googleapis.com/",
   "schemas": {
     "CreateProfileRequest": {

googleapiclient/discovery_cache/documents/cloudresourcemanager.v1.json

@@ -1171,7 +1171,7 @@
       }
     }
   },
-  "revision": "20231203",
+  "revision": "20231207",
   "rootUrl": "https://cloudresourcemanager.googleapis.com/",
   "schemas": {
     "Ancestor": {

googleapiclient/discovery_cache/documents/cloudresourcemanager.v1beta1.json

@@ -568,7 +568,7 @@
       }
     }
   },
-  "revision": "20231203",
+  "revision": "20231207",
   "rootUrl": "https://cloudresourcemanager.googleapis.com/",
   "schemas": {
     "Ancestor": {

googleapiclient/discovery_cache/documents/cloudresourcemanager.v2.json

@@ -450,7 +450,7 @@
       }
     }
   },
-  "revision": "20231203",
+  "revision": "20231207",
   "rootUrl": "https://cloudresourcemanager.googleapis.com/",
   "schemas": {
     "AuditConfig": {

googleapiclient/discovery_cache/documents/cloudresourcemanager.v2beta1.json

@@ -450,7 +450,7 @@
       }
     }
   },
-  "revision": "20231203",
+  "revision": "20231207",
   "rootUrl": "https://cloudresourcemanager.googleapis.com/",
   "schemas": {
     "AuditConfig": {

googleapiclient/discovery_cache/documents/cloudresourcemanager.v3.json

@@ -1805,7 +1805,7 @@
       }
     }
   },
-  "revision": "20231203",
+  "revision": "20231207",
   "rootUrl": "https://cloudresourcemanager.googleapis.com/",
   "schemas": {
     "AuditConfig": {

googleapiclient/discovery_cache/documents/cloudscheduler.v1.json

@@ -418,7 +418,7 @@
       }
     }
   },
-  "revision": "20231103",
+  "revision": "20231201",
   "rootUrl": "https://cloudscheduler.googleapis.com/",
   "schemas": {
     "AppEngineHttpTarget": {
@@ -438,7 +438,7 @@
           "additionalProperties": {
             "type": "string"
           },
-          "description": "HTTP request headers. This map contains the header field names and values. Headers can be set when the job is created. Cloud Scheduler sets some headers to default values: * `User-Agent`: By default, this header is `\"AppEngine-Google; (+http://code.google.com/appengine)\"`. This header can be modified, but Cloud Scheduler will append `\"AppEngine-Google; (+http://code.google.com/appengine)\"` to the modified `User-Agent`. * `X-CloudScheduler`: This header will be set to true. * `X-CloudScheduler-JobName`: This header will contain the job name. * `X-CloudScheduler-ScheduleTime`: For Cloud Scheduler jobs specified in the unix-cron format, this header will contain the job schedule time in RFC3339 UTC \"Zulu\" format. If the job has a body and the following headers are not set by the user, Cloud Scheduler sets default values: * `Content-Type`: This will be set to `\"application/octet-stream\"`. You can override this default by explicitly setting `Content-Type` to a particular media type when creating the job. For example, you can set `Content-Type` to `\"application/json\"`. The headers below are output only. They cannot be set or overridden: * `Content-Length`: This is computed by Cloud Scheduler. * `X-Google-*`: For Google internal use only. * `X-AppEngine-*`: For Google internal use only. In addition, some App Engine headers, which contain job-specific information, are also be sent to the job handler.",
+          "description": "HTTP request headers. This map contains the header field names and values. Headers can be set when the job is created. Cloud Scheduler sets some headers to default values: * `User-Agent`: By default, this header is `\"AppEngine-Google; (+http://code.google.com/appengine)\"`. This header can be modified, but Cloud Scheduler will append `\"AppEngine-Google; (+http://code.google.com/appengine)\"` to the modified `User-Agent`. * `X-CloudScheduler`: This header will be set to true. * `X-CloudScheduler-JobName`: This header will contain the job name. * `X-CloudScheduler-ScheduleTime`: For Cloud Scheduler jobs specified in the unix-cron format, this header will contain the job schedule as an offset of UTC parsed according to RFC3339. If the job has a body and the following headers are not set by the user, Cloud Scheduler sets default values: * `Content-Type`: This will be set to `\"application/octet-stream\"`. You can override this default by explicitly setting `Content-Type` to a particular media type when creating the job. For example, you can set `Content-Type` to `\"application/json\"`. The headers below are output only. They cannot be set or overridden: * `Content-Length`: This is computed by Cloud Scheduler. * `X-Google-*`: For Google internal use only. * `X-AppEngine-*`: For Google internal use only. In addition, some App Engine headers, which contain job-specific information, are also be sent to the job handler.",
           "type": "object"
         },
         "httpMethod": {
@@ -514,7 +514,7 @@
           "additionalProperties": {
             "type": "string"
           },
-          "description": "HTTP request headers. This map contains the header field names and values. The user can specify HTTP request headers to send with the job's HTTP request. Repeated headers are not supported, but a header value can contain commas. The following headers represent a subset of the headers that accompany the job's HTTP request. Some HTTP request headers are ignored or replaced. A partial list of headers that are ignored or replaced is below: * Host: This will be computed by Cloud Scheduler and derived from uri. * `Content-Length`: This will be computed by Cloud Scheduler. * `User-Agent`: This will be set to `\"Google-Cloud-Scheduler\"`. * `X-Google-*`: Google internal use only. * `X-AppEngine-*`: Google internal use only. * `X-CloudScheduler`: This header will be set to true. * `X-CloudScheduler-JobName`: This header will contain the job name. * `X-CloudScheduler-ScheduleTime`: For Cloud Scheduler jobs specified in the unix-cron format, this header will contain the job schedule time in RFC3339 UTC \"Zulu\" format. If the job has a body and the following headers are not set by the user, Cloud Scheduler sets default values: * `Content-Type`: This will be set to `\"application/octet-stream\"`. You can override this default by explicitly setting `Content-Type` to a particular media type when creating the job. For example, you can set `Content-Type` to `\"application/json\"`. The total size of headers must be less than 80KB.",
+          "description": "HTTP request headers. This map contains the header field names and values. The user can specify HTTP request headers to send with the job's HTTP request. Repeated headers are not supported, but a header value can contain commas. The following headers represent a subset of the headers that accompany the job's HTTP request. Some HTTP request headers are ignored or replaced. A partial list of headers that are ignored or replaced is below: * Host: This will be computed by Cloud Scheduler and derived from uri. * `Content-Length`: This will be computed by Cloud Scheduler. * `User-Agent`: This will be set to `\"Google-Cloud-Scheduler\"`. * `X-Google-*`: Google internal use only. * `X-AppEngine-*`: Google internal use only. * `X-CloudScheduler`: This header will be set to true. * `X-CloudScheduler-JobName`: This header will contain the job name. * `X-CloudScheduler-ScheduleTime`: For Cloud Scheduler jobs specified in the unix-cron format, this header will contain the job schedule as an offset of UTC parsed according to RFC3339. If the job has a body and the following headers are not set by the user, Cloud Scheduler sets default values: * `Content-Type`: This will be set to `\"application/octet-stream\"`. You can override this default by explicitly setting `Content-Type` to a particular media type when creating the job. For example, you can set `Content-Type` to `\"application/json\"`. The total size of headers must be less than 80KB.",
           "type": "object"
         },
         "httpMethod": {

googleapiclient/discovery_cache/documents/cloudscheduler.v1beta1.json

@@ -433,7 +433,7 @@
       }
     }
   },
-  "revision": "20231103",
+  "revision": "20231201",
   "rootUrl": "https://cloudscheduler.googleapis.com/",
   "schemas": {
     "AppEngineHttpTarget": {
@@ -453,7 +453,7 @@
           "additionalProperties": {
             "type": "string"
           },
-          "description": "HTTP request headers. This map contains the header field names and values. Headers can be set when the job is created. Cloud Scheduler sets some headers to default values: * `User-Agent`: By default, this header is `\"AppEngine-Google; (+http://code.google.com/appengine)\"`. This header can be modified, but Cloud Scheduler will append `\"AppEngine-Google; (+http://code.google.com/appengine)\"` to the modified `User-Agent`. * `X-CloudScheduler`: This header will be set to true. * `X-CloudScheduler-JobName`: This header will contain the job name. * `X-CloudScheduler-ScheduleTime`: For Cloud Scheduler jobs specified in the unix-cron format, this header will contain the job schedule time in RFC3339 UTC \"Zulu\" format. If the job has a body and the following headers are not set by the user, Cloud Scheduler sets default values: * `Content-Type`: This will be set to `\"application/octet-stream\"`. You can override this default by explicitly setting `Content-Type` to a particular media type when creating the job. For example, you can set `Content-Type` to `\"application/json\"`. The headers below are output only. They cannot be set or overridden: * `Content-Length`: This is computed by Cloud Scheduler. * `X-Google-*`: For Google internal use only. * `X-AppEngine-*`: For Google internal use only. In addition, some App Engine headers, which contain job-specific information, are also be sent to the job handler.",
+          "description": "HTTP request headers. This map contains the header field names and values. Headers can be set when the job is created. Cloud Scheduler sets some headers to default values: * `User-Agent`: By default, this header is `\"AppEngine-Google; (+http://code.google.com/appengine)\"`. This header can be modified, but Cloud Scheduler will append `\"AppEngine-Google; (+http://code.google.com/appengine)\"` to the modified `User-Agent`. * `X-CloudScheduler`: This header will be set to true. * `X-CloudScheduler-JobName`: This header will contain the job name. * `X-CloudScheduler-ScheduleTime`: For Cloud Scheduler jobs specified in the unix-cron format, this header will contain the job schedule as an offset of UTC parsed according to RFC3339. If the job has a body and the following headers are not set by the user, Cloud Scheduler sets default values: * `Content-Type`: This will be set to `\"application/octet-stream\"`. You can override this default by explicitly setting `Content-Type` to a particular media type when creating the job. For example, you can set `Content-Type` to `\"application/json\"`. The headers below are output only. They cannot be set or overridden: * `Content-Length`: This is computed by Cloud Scheduler. * `X-Google-*`: For Google internal use only. * `X-AppEngine-*`: For Google internal use only. In addition, some App Engine headers, which contain job-specific information, are also be sent to the job handler.",
           "type": "object"
         },
         "httpMethod": {
@@ -529,7 +529,7 @@
           "additionalProperties": {
             "type": "string"
           },
-          "description": "HTTP request headers. This map contains the header field names and values. The user can specify HTTP request headers to send with the job's HTTP request. Repeated headers are not supported, but a header value can contain commas. The following headers represent a subset of the headers that accompany the job's HTTP request. Some HTTP request headers are ignored or replaced. A partial list of headers that are ignored or replaced is below: * Host: This will be computed by Cloud Scheduler and derived from uri. * `Content-Length`: This will be computed by Cloud Scheduler. * `User-Agent`: This will be set to `\"Google-Cloud-Scheduler\"`. * `X-Google-*`: Google internal use only. * `X-AppEngine-*`: Google internal use only. * `X-CloudScheduler`: This header will be set to true. * `X-CloudScheduler-JobName`: This header will contain the job name. * `X-CloudScheduler-ScheduleTime`: For Cloud Scheduler jobs specified in the unix-cron format, this header will contain the job schedule time in RFC3339 UTC \"Zulu\" format. If the job has a body and the following headers are not set by the user, Cloud Scheduler sets default values: * `Content-Type`: This will be set to `\"application/octet-stream\"`. You can override this default by explicitly setting `Content-Type` to a particular media type when creating the job. For example, you can set `Content-Type` to `\"application/json\"`. The total size of headers must be less than 80KB.",
+          "description": "HTTP request headers. This map contains the header field names and values. The user can specify HTTP request headers to send with the job's HTTP request. Repeated headers are not supported, but a header value can contain commas. The following headers represent a subset of the headers that accompany the job's HTTP request. Some HTTP request headers are ignored or replaced. A partial list of headers that are ignored or replaced is below: * Host: This will be computed by Cloud Scheduler and derived from uri. * `Content-Length`: This will be computed by Cloud Scheduler. * `User-Agent`: This will be set to `\"Google-Cloud-Scheduler\"`. * `X-Google-*`: Google internal use only. * `X-AppEngine-*`: Google internal use only. * `X-CloudScheduler`: This header will be set to true. * `X-CloudScheduler-JobName`: This header will contain the job name. * `X-CloudScheduler-ScheduleTime`: For Cloud Scheduler jobs specified in the unix-cron format, this header will contain the job schedule as an offset of UTC parsed according to RFC3339. If the job has a body and the following headers are not set by the user, Cloud Scheduler sets default values: * `Content-Type`: This will be set to `\"application/octet-stream\"`. You can override this default by explicitly setting `Content-Type` to a particular media type when creating the job. For example, you can set `Content-Type` to `\"application/json\"`. The total size of headers must be less than 80KB.",
           "type": "object"
         },
         "httpMethod": {

googleapiclient/discovery_cache/documents/cloudshell.v1.json

@@ -374,7 +374,7 @@
       }
     }
   },
-  "revision": "20231204",
+  "revision": "20231211",
   "rootUrl": "https://cloudshell.googleapis.com/",
   "schemas": {
     "AddPublicKeyMetadata": {

googleapiclient/discovery_cache/documents/cloudsupport.v2.json

@@ -552,7 +552,7 @@
       }
     }
   },
-  "revision": "20231204",
+  "revision": "20231207",
   "rootUrl": "https://cloudsupport.googleapis.com/",
   "schemas": {
     "Actor": {

googleapiclient/discovery_cache/documents/cloudsupport.v2beta.json

@@ -548,7 +548,7 @@
       }
     }
   },
-  "revision": "20231204",
+  "revision": "20231207",
   "rootUrl": "https://cloudsupport.googleapis.com/",
   "schemas": {
     "Actor": {

googleapiclient/discovery_cache/documents/cloudtasks.v2.json

@@ -779,7 +779,7 @@
       }
     }
   },
-  "revision": "20231103",
+  "revision": "20231201",
   "rootUrl": "https://cloudtasks.googleapis.com/",
   "schemas": {
     "AppEngineHttpRequest": {
@@ -962,7 +962,7 @@
         },
         "task": {
           "$ref": "Task",
-          "description": "Required. The task to add. Task names have the following format: `projects/PROJECT_ID/locations/LOCATION_ID/queues/QUEUE_ID/tasks/TASK_ID`. The user can optionally specify a task name. If a name is not specified then the system will generate a random unique task id, which will be set in the task returned in the response. If schedule_time is not set or is in the past then Cloud Tasks will set it to the current time. Task De-duplication: Explicitly specifying a task ID enables task de-duplication. If a task's ID is identical to that of an existing task or a task that was deleted or executed recently then the call will fail with ALREADY_EXISTS. If the task's queue was created using Cloud Tasks, then another task with the same name can't be created for ~1hour after the original task was deleted or executed. If the task's queue was created using queue.yaml or queue.xml, then another task with the same name can't be created for ~9days after the original task was deleted or executed. Because there is an extra lookup cost to identify duplicate task names, these CreateTask calls have significantly increased latency. Using hashed strings for the task id or for the prefix of the task id is recommended. Choosing task ids that are sequential or have sequential prefixes, for example using a timestamp, causes an increase in latency and error rates in all task commands. The infrastructure relies on an approximately uniform distribution of task ids to store and serve tasks efficiently."
+          "description": "Required. The task to add. Task names have the following format: `projects/PROJECT_ID/locations/LOCATION_ID/queues/QUEUE_ID/tasks/TASK_ID`. The user can optionally specify a task name. If a name is not specified then the system will generate a random unique task id, which will be set in the task returned in the response. If schedule_time is not set or is in the past then Cloud Tasks will set it to the current time. Task De-duplication: Explicitly specifying a task ID enables task de-duplication. If a task's ID is identical to that of an existing task or a task that was deleted or executed recently then the call will fail with ALREADY_EXISTS. The IDs of deleted tasks are not immediately available for reuse. It can take up to 4 hours (or 9 days if the task's queue was created using a queue.yaml or queue.xml) for the task ID to be released and made available again. Because there is an extra lookup cost to identify duplicate task names, these CreateTask calls have significantly increased latency. Using hashed strings for the task id or for the prefix of the task id is recommended. Choosing task ids that are sequential or have sequential prefixes, for example using a timestamp, causes an increase in latency and error rates in all task commands. The infrastructure relies on an approximately uniform distribution of task ids to store and serve tasks efficiently."
         }
       },
       "type": "object"

googleapiclient/discovery_cache/documents/cloudtasks.v2beta2.json

@@ -935,7 +935,7 @@
       }
     }
   },
-  "revision": "20231103",
+  "revision": "20231201",
   "rootUrl": "https://cloudtasks.googleapis.com/",
   "schemas": {
     "AcknowledgeTaskRequest": {
@@ -1167,7 +1167,7 @@
         },
         "task": {
           "$ref": "Task",
-          "description": "Required. The task to add. Task names have the following format: `projects/PROJECT_ID/locations/LOCATION_ID/queues/QUEUE_ID/tasks/TASK_ID`. The user can optionally specify a task name. If a name is not specified then the system will generate a random unique task id, which will be set in the task returned in the response. If schedule_time is not set or is in the past then Cloud Tasks will set it to the current time. Task De-duplication: Explicitly specifying a task ID enables task de-duplication. If a task's ID is identical to that of an existing task or a task that was deleted or completed recently then the call will fail with ALREADY_EXISTS. If the task's queue was created using Cloud Tasks, then another task with the same name can't be created for ~1 hour after the original task was deleted or completed. If the task's queue was created using queue.yaml or queue.xml, then another task with the same name can't be created for ~9 days after the original task was deleted or completed. Because there is an extra lookup cost to identify duplicate task names, these CreateTask calls have significantly increased latency. Using hashed strings for the task id or for the prefix of the task id is recommended. Choosing task ids that are sequential or have sequential prefixes, for example using a timestamp, causes an increase in latency and error rates in all task commands. The infrastructure relies on an approximately uniform distribution of task ids to store and serve tasks efficiently."
+          "description": "Required. The task to add. Task names have the following format: `projects/PROJECT_ID/locations/LOCATION_ID/queues/QUEUE_ID/tasks/TASK_ID`. The user can optionally specify a task name. If a name is not specified then the system will generate a random unique task id, which will be set in the task returned in the response. If schedule_time is not set or is in the past then Cloud Tasks will set it to the current time. Task De-duplication: Explicitly specifying a task ID enables task de-duplication. If a task's ID is identical to that of an existing task or a task that was deleted or completed recently then the call will fail with ALREADY_EXISTS. The IDs of deleted tasks are not immediately available for reuse. It can take up to 4 hours (or 9 days if the task's queue was created using a queue.yaml or queue.xml) for the task ID to be released and made available again. Because there is an extra lookup cost to identify duplicate task names, these CreateTask calls have significantly increased latency. Using hashed strings for the task id or for the prefix of the task id is recommended. Choosing task ids that are sequential or have sequential prefixes, for example using a timestamp, causes an increase in latency and error rates in all task commands. The infrastructure relies on an approximately uniform distribution of task ids to store and serve tasks efficiently."
         }
       },
       "type": "object"

googleapiclient/discovery_cache/documents/cloudtasks.v2beta3.json

@@ -791,7 +791,7 @@
       }
     }
   },
-  "revision": "20231103",
+  "revision": "20231201",
   "rootUrl": "https://cloudtasks.googleapis.com/",
   "schemas": {
     "AppEngineHttpQueue": {
@@ -985,7 +985,7 @@
         },
         "task": {
           "$ref": "Task",
-          "description": "Required. The task to add. Task names have the following format: `projects/PROJECT_ID/locations/LOCATION_ID/queues/QUEUE_ID/tasks/TASK_ID`. The user can optionally specify a task name. If a name is not specified then the system will generate a random unique task id, which will be set in the task returned in the response. If schedule_time is not set or is in the past then Cloud Tasks will set it to the current time. Task De-duplication: Explicitly specifying a task ID enables task de-duplication. If a task's ID is identical to that of an existing task or a task that was deleted or executed recently then the call will fail with ALREADY_EXISTS. If the task's queue was created using Cloud Tasks, then another task with the same name can't be created for ~1 hour after the original task was deleted or executed. If the task's queue was created using queue.yaml or queue.xml, then another task with the same name can't be created for ~9 days after the original task was deleted or executed. Because there is an extra lookup cost to identify duplicate task names, these CreateTask calls have significantly increased latency. Using hashed strings for the task id or for the prefix of the task id is recommended. Choosing task ids that are sequential or have sequential prefixes, for example using a timestamp, causes an increase in latency and error rates in all task commands. The infrastructure relies on an approximately uniform distribution of task ids to store and serve tasks efficiently."
+          "description": "Required. The task to add. Task names have the following format: `projects/PROJECT_ID/locations/LOCATION_ID/queues/QUEUE_ID/tasks/TASK_ID`. The user can optionally specify a task name. If a name is not specified then the system will generate a random unique task id, which will be set in the task returned in the response. If schedule_time is not set or is in the past then Cloud Tasks will set it to the current time. Task De-duplication: Explicitly specifying a task ID enables task de-duplication. If a task's ID is identical to that of an existing task or a task that was deleted or executed recently then the call will fail with ALREADY_EXISTS. The IDs of deleted tasks are not immediately available for reuse. It can take up to 4 hours (or 9 days if the task's queue was created using a queue.yaml or queue.xml) for the task ID to be released and made available again. Because there is an extra lookup cost to identify duplicate task names, these CreateTask calls have significantly increased latency. Using hashed strings for the task id or for the prefix of the task id is recommended. Choosing task ids that are sequential or have sequential prefixes, for example using a timestamp, causes an increase in latency and error rates in all task commands. The infrastructure relies on an approximately uniform distribution of task ids to store and serve tasks efficiently."
         }
       },
       "type": "object"

googleapiclient/discovery_cache/documents/cloudtrace.v1.json

@@ -257,7 +257,7 @@
       }
     }
   },
-  "revision": "20231109",
+  "revision": "20231130",
   "rootUrl": "https://cloudtrace.googleapis.com/",
   "schemas": {
     "Empty": {

googleapiclient/discovery_cache/documents/cloudtrace.v2beta1.json

@@ -273,7 +273,7 @@
       }
     }
   },
-  "revision": "20231109",
+  "revision": "20231130",
   "rootUrl": "https://cloudtrace.googleapis.com/",
   "schemas": {
     "Empty": {

googleapiclient/discovery_cache/documents/composer.v1.json

@@ -599,7 +599,7 @@
       }
     }
   },
-  "revision": "20231129",
+  "revision": "20231205",
   "rootUrl": "https://composer.googleapis.com/",
   "schemas": {
     "AllowedIpRange": {

googleapiclient/discovery_cache/documents/composer.v1beta1.json

@@ -655,7 +655,7 @@
       }
     }
   },
-  "revision": "20231129",
+  "revision": "20231205",
   "rootUrl": "https://composer.googleapis.com/",
   "schemas": {
     "AllowedIpRange": {

googleapiclient/discovery_cache/documents/connectors.v1.json

@@ -2349,7 +2349,7 @@
       }
     }
   },
-  "revision": "20231126",
+  "revision": "20231205",
   "rootUrl": "https://connectors.googleapis.com/",
   "schemas": {
     "AuditConfig": {
@@ -2625,6 +2625,22 @@
           "description": "Key of the config variable.",
           "type": "string"
         },
+        "locationType": {
+          "description": "Optional. Location Tyep denotes where this value should be sent in BYOC connections.",
+          "enum": [
+            "LOCATION_TYPE_UNSPECIFIED",
+            "HEADER",
+            "PAYLOAD",
+            "QUERY_PARAM"
+          ],
+          "enumDescriptions": [
+            "Location type unspecified.",
+            "Request header.",
+            "Request Payload.",
+            "Request query param."
+          ],
+          "type": "string"
+        },
         "required": {
           "description": "Flag represents that this `ConfigVariable` must be provided for a connection.",
           "type": "boolean"
@@ -3211,6 +3227,26 @@
           "description": "Output only. Information about the runtime features supported by the Connector.",
           "readOnly": true
         },
+        "unsupportedConnectionTypes": {
+          "description": "Output only. Unsupported connection types.",
+          "items": {
+            "enum": [
+              "CONNECTION_TYPE_UNSPECIFIED",
+              "CONNECTION_WITH_EVENTING",
+              "ONLY_CONNECTION",
+              "ONLY_EVENTING"
+            ],
+            "enumDescriptions": [
+              "Connection type is unspecified.",
+              "Connection with eventing.",
+              "Only connection.",
+              "Only eventing."
+            ],
+            "type": "string"
+          },
+          "readOnly": true,
+          "type": "array"
+        },
         "updateTime": {
           "description": "Output only. Updated time.",
           "format": "google-datetime",
@@ -3338,7 +3374,14 @@
       "properties": {
         "authConfig": {
           "$ref": "AuthConfig",
-          "description": "Required. Configuration for establishing the authentication to the connector destination."
+          "description": "Optional. Authentication config for accessing connector facade/ proxy. This is used only when enable_backend_destination_config is true."
+        },
+        "backendVariableTemplates": {
+          "description": "Optional. Backend variables config templates. This translates to additional variable templates in connection.",
+          "items": {
+            "$ref": "ConfigVariableTemplate"
+          },
+          "type": "array"
         },
         "createTime": {
           "description": "Output only. Created time.",
@@ -3346,12 +3389,15 @@
           "readOnly": true,
           "type": "string"
         },
-        "destinationConfig": {
-          "$ref": "DestinationConfig",
-          "description": "Required. Configuration of the customConnector's destination."
+        "destinationConfigs": {
+          "description": "Optional. Destination config(s) for accessing connector facade/ proxy. This is used only when enable_backend_destination_config is true.",
+          "items": {
+            "$ref": "DestinationConfig"
+          },
+          "type": "array"
         },
         "enableBackendDestinationConfig": {
-          "description": "Optional. Whether to enable backend destination config. This is the backend server that the connector connects to.",
+          "description": "Optional. When enabled, the connector will be a facade/ proxy, and connects to the destination provided during connection creation.",
           "type": "boolean"
         },
         "labels": {
@@ -3367,7 +3413,7 @@
           "type": "string"
         },
         "serviceAccount": {
-          "description": "Required. Service account needed for runtime plane to access Custom Connector secrets.",
+          "description": "Required. Service account used by runtime plane to access auth config secrets.",
           "type": "string"
         },
         "specLocation": {

googleapiclient/discovery_cache/documents/connectors.v2.json

@@ -111,6 +111,81 @@
           "resources": {
             "connections": {
               "methods": {
+                "checkReadiness": {
+                  "description": "Reports readiness status of the connector. Similar logic to GetStatus but modified for kubernetes health check to understand.",
+                  "flatPath": "v2/projects/{projectsId}/locations/{locationsId}/connections/{connectionsId}:checkReadiness",
+                  "httpMethod": "GET",
+                  "id": "connectors.projects.locations.connections.checkReadiness",
+                  "parameterOrder": [
+                    "name"
+                  ],
+                  "parameters": {
+                    "name": {
+                      "location": "path",
+                      "pattern": "^projects/[^/]+/locations/[^/]+/connections/[^/]+$",
+                      "required": true,
+                      "type": "string"
+                    }
+                  },
+                  "path": "v2/{+name}:checkReadiness",
+                  "response": {
+                    "$ref": "CheckReadinessResponse"
+                  },
+                  "scopes": [
+                    "https://www.googleapis.com/auth/cloud-platform"
+                  ]
+                },
+                "checkStatus": {
+                  "description": "Reports the status of the connection. Note that when the connection is in a state that is not ACTIVE, the implementation of this RPC method must return a Status with the corresponding State instead of returning a gRPC status code that is not \"OK\", which indicates that ConnectionStatus itself, not the connection, failed.",
+                  "flatPath": "v2/projects/{projectsId}/locations/{locationsId}/connections/{connectionsId}:checkStatus",
+                  "httpMethod": "GET",
+                  "id": "connectors.projects.locations.connections.checkStatus",
+                  "parameterOrder": [
+                    "name"
+                  ],
+                  "parameters": {
+                    "name": {
+                      "location": "path",
+                      "pattern": "^projects/[^/]+/locations/[^/]+/connections/[^/]+$",
+                      "required": true,
+                      "type": "string"
+                    }
+                  },
+                  "path": "v2/{+name}:checkStatus",
+                  "response": {
+                    "$ref": "CheckStatusResponse"
+                  },
+                  "scopes": [
+                    "https://www.googleapis.com/auth/cloud-platform"
+                  ]
+                },
+                "exchangeAuthCode": {
+                  "description": "ExchangeAuthCode exchanges the OAuth authorization code (and other necessary data) for an access token (and associated credentials).",
+                  "flatPath": "v2/projects/{projectsId}/locations/{locationsId}/connections/{connectionsId}:exchangeAuthCode",
+                  "httpMethod": "POST",
+                  "id": "connectors.projects.locations.connections.exchangeAuthCode",
+                  "parameterOrder": [
+                    "name"
+                  ],
+                  "parameters": {
+                    "name": {
+                      "location": "path",
+                      "pattern": "^projects/[^/]+/locations/[^/]+/connections/[^/]+$",
+                      "required": true,
+                      "type": "string"
+                    }
+                  },
+                  "path": "v2/{+name}:exchangeAuthCode",
+                  "request": {
+                    "$ref": "ExchangeAuthCodeRequest"
+                  },
+                  "response": {
+                    "$ref": "ExchangeAuthCodeResponse"
+                  },
+                  "scopes": [
+                    "https://www.googleapis.com/auth/cloud-platform"
+                  ]
+                },
                 "executeSqlQuery": {
                   "description": "Executes a SQL statement specified in the body of the request. An example of this SQL statement in the case of Salesforce connector would be 'select * from Account a, Order o where a.Id = o.AccountId'.",
                   "flatPath": "v2/projects/{projectsId}/locations/{locationsId}/connections/{connectionsId}:executeSqlQuery",
@@ -138,6 +213,33 @@
                   "scopes": [
                     "https://www.googleapis.com/auth/cloud-platform"
                   ]
+                },
+                "refreshAccessToken": {
+                  "description": "RefreshAccessToken exchanges the OAuth refresh token (and other necessary data) for a new access token (and new associated credentials).",
+                  "flatPath": "v2/projects/{projectsId}/locations/{locationsId}/connections/{connectionsId}:refreshAccessToken",
+                  "httpMethod": "POST",
+                  "id": "connectors.projects.locations.connections.refreshAccessToken",
+                  "parameterOrder": [
+                    "name"
+                  ],
+                  "parameters": {
+                    "name": {
+                      "location": "path",
+                      "pattern": "^projects/[^/]+/locations/[^/]+/connections/[^/]+$",
+                      "required": true,
+                      "type": "string"
+                    }
+                  },
+                  "path": "v2/{+name}:refreshAccessToken",
+                  "request": {
+                    "$ref": "RefreshAccessTokenRequest"
+                  },
+                  "response": {
+                    "$ref": "RefreshAccessTokenResponse"
+                  },
+                  "scopes": [
+                    "https://www.googleapis.com/auth/cloud-platform"
+                  ]
                 }
               },
               "resources": {
@@ -558,9 +660,29 @@
       }
     }
   },
-  "revision": "20231126",
+  "revision": "20231205",
   "rootUrl": "https://connectors.googleapis.com/",
   "schemas": {
+    "AccessCredentials": {
+      "description": "AccessCredentials includes the OAuth access token, and the other fields returned along with it.",
+      "id": "AccessCredentials",
+      "properties": {
+        "accessToken": {
+          "description": "OAuth access token.",
+          "type": "string"
+        },
+        "expiresIn": {
+          "description": "Duration till the access token expires.",
+          "format": "google-duration",
+          "type": "string"
+        },
+        "refreshToken": {
+          "description": "OAuth refresh token.",
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
     "Action": {
       "description": "Action message contains metadata information about a single action present in the external system.",
       "id": "Action",
@@ -602,6 +724,43 @@
       },
       "type": "object"
     },
+    "CheckReadinessResponse": {
+      "description": "Response containing status of the connector for readiness prober.",
+      "id": "CheckReadinessResponse",
+      "properties": {
+        "status": {
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
+    "CheckStatusResponse": {
+      "description": "The status of the connector.",
+      "id": "CheckStatusResponse",
+      "properties": {
+        "description": {
+          "description": "When the connector is not in ACTIVE state, the description must be populated to specify the reason why it's not in ACTIVE state.",
+          "type": "string"
+        },
+        "state": {
+          "description": "State of the connector.",
+          "enum": [
+            "STATE_UNSPECIFIED",
+            "ACTIVE",
+            "ERROR",
+            "AUTH_ERROR"
+          ],
+          "enumDescriptions": [
+            "State unspecified.",
+            "The connector is active and ready to process runtime requests. This can also mean that from the connector's perspective, the connector is not in an error state and should be able to process runtime requests successfully.",
+            "The connector is in an error state and cannot process runtime requests. An example reason would be that the connection container has some network issues that prevent outbound requests from being sent.",
+            "This is a more specific error state that the developers can opt to use when the connector is facing auth-related errors caused by auth configuration not present, invalid auth credentials, etc."
+          ],
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
     "Empty": {
       "description": "A generic empty message that you can re-use to avoid defining duplicated empty messages in your APIs. A typical example is to use it as the request or the response type of an API method. For instance: service Foo { rpc Bar(google.protobuf.Empty) returns (google.protobuf.Empty); }",
       "id": "Empty",
@@ -649,6 +808,22 @@
       },
       "type": "object"
     },
+    "ExchangeAuthCodeRequest": {
+      "description": "ExchangeAuthCodeRequest currently includes no fields.",
+      "id": "ExchangeAuthCodeRequest",
+      "properties": {},
+      "type": "object"
+    },
+    "ExchangeAuthCodeResponse": {
+      "description": "ExchangeAuthCodeResponse includes the returned access token and its associated credentials.",
+      "id": "ExchangeAuthCodeResponse",
+      "properties": {
+        "accessCredentials": {
+          "$ref": "AccessCredentials"
+        }
+      },
+      "type": "object"
+    },
     "ExecuteActionRequest": {
       "description": "Request message for ActionService.ExecuteAction",
       "id": "ExecuteActionRequest",
@@ -1547,6 +1722,22 @@
       },
       "type": "object"
     },
+    "RefreshAccessTokenRequest": {
+      "description": "RefreshAccessTokenRequest currently includes no fields.",
+      "id": "RefreshAccessTokenRequest",
+      "properties": {},
+      "type": "object"
+    },
+    "RefreshAccessTokenResponse": {
+      "description": "RefreshAccessTokenResponse includes the returned access token and its associated credentials.",
+      "id": "RefreshAccessTokenResponse",
+      "properties": {
+        "accessCredentials": {
+          "$ref": "AccessCredentials"
+        }
+      },
+      "type": "object"
+    },
     "ResultMetadata": {
       "description": "Result Metadata message contains metadata about the result returned after executing an Action.",
       "id": "ResultMetadata",

googleapiclient/discovery_cache/documents/contactcenterinsights.v1.json

@@ -1412,7 +1412,7 @@
       }
     }
   },
-  "revision": "20231206",
+  "revision": "20231211",
   "rootUrl": "https://contactcenterinsights.googleapis.com/",
   "schemas": {
     "GoogleCloudContactcenterinsightsV1Analysis": {