From 016214975099347cdc4870ce8e6d9b14bd2e7bd3 Mon Sep 17 00:00:00 2001 From: Yoshi Automation Date: Tue, 4 Oct 2022 07:14:49 +0000 Subject: [PATCH] feat(cloudtasks): update the api #### cloudtasks:v2beta2 The following keys were deleted: - resources.projects.resources.locations.resources.queues.resources.tasks.methods.buffer.parameters.parent (Total Keys: 4) - schemas.Header.properties.key.format (Total Keys: 1) - schemas.Header.properties.value.format (Total Keys: 1) The following keys were added: - resources.api.resources.queue.methods.update (Total Keys: 10) - resources.projects.resources.locations.resources.queues.resources.tasks.methods.buffer.parameters.queue (Total Keys: 4) The following keys were changed: - resources.projects.resources.locations.resources.queues.resources.tasks.methods.buffer (Total Keys: 2) --- docs/dyn/cloudtasks_v2beta2.api.html | 91 +++++++++++++ docs/dyn/cloudtasks_v2beta2.api.queue.html | 120 ++++++++++++++++++ docs/dyn/cloudtasks_v2beta2.html | 5 + ...sks_v2beta2.projects.locations.queues.html | 36 +++--- ...beta2.projects.locations.queues.tasks.html | 15 ++- .../documents/cloudtasks.v2.json | 2 +- .../documents/cloudtasks.v2beta2.json | 46 ++++++- .../documents/cloudtasks.v2beta3.json | 2 +- 8 files changed, 283 insertions(+), 34 deletions(-) create mode 100644 docs/dyn/cloudtasks_v2beta2.api.html create mode 100644 docs/dyn/cloudtasks_v2beta2.api.queue.html diff --git a/docs/dyn/cloudtasks_v2beta2.api.html b/docs/dyn/cloudtasks_v2beta2.api.html new file mode 100644 index 00000000000..716f01a34eb --- /dev/null +++ b/docs/dyn/cloudtasks_v2beta2.api.html @@ -0,0 +1,91 @@ + + + +

Cloud Tasks API . api

+

Instance Methods

+

+ queue() +

+

Returns the queue Resource.

+ +

+ close()

+

Close httplib2 connections.

+

Method Details

+
+ close() + 
Close httplib2 connections.
+
+ + \ No newline at end of file diff --git a/docs/dyn/cloudtasks_v2beta2.api.queue.html b/docs/dyn/cloudtasks_v2beta2.api.queue.html new file mode 100644 index 00000000000..f47d1fca0e6 --- /dev/null +++ b/docs/dyn/cloudtasks_v2beta2.api.queue.html @@ -0,0 +1,120 @@ + + + +

Cloud Tasks API . api . queue

+

Instance Methods

+

+ close()

+

Close httplib2 connections.

+

+ update(appId=None, body=None, x__xgafv=None)

+

Update queue list by uploading a queue.yaml file. The queue.yaml file is supplied in the request body as a YAML encoded string. This method was added to support gcloud clients versions before 322.0.0. New clients should use CreateQueue instead of this method.

+

Method Details

+
+ close() + 
Close httplib2 connections.
+
+ +
+ update(appId=None, body=None, x__xgafv=None) + 
Update queue list by uploading a queue.yaml file. The queue.yaml file is supplied in the request body as a YAML encoded string. This method was added to support gcloud clients versions before 322.0.0. New clients should use CreateQueue instead of this method.
+
+Args:
+  body: object, The request body.
+    The object takes the form of:
+
+{ # Message that represents an arbitrary HTTP body. It should only be used for payload formats that can't be represented as JSON, such as raw binary or an HTML page. This message can be used both in streaming and non-streaming API methods in the request as well as the response. It can be used as a top-level request field, which is convenient if one wants to extract parameters from either the URL or HTTP template into the request fields and also want access to the raw HTTP body. Example: message GetResourceRequest { // A unique request id. string request_id = 1; // The raw HTTP body is bound to this field. google.api.HttpBody http_body = 2; } service ResourceService { rpc GetResource(GetResourceRequest) returns (google.api.HttpBody); rpc UpdateResource(google.api.HttpBody) returns (google.protobuf.Empty); } Example with streaming methods: service CaldavService { rpc GetCalendar(stream google.api.HttpBody) returns (stream google.api.HttpBody); rpc UpdateCalendar(stream google.api.HttpBody) returns (stream google.api.HttpBody); } Use of this type only changes how the request and response bodies are handled, all other features will continue to work unchanged.
+  "contentType": "A String", # The HTTP Content-Type header value specifying the content type of the body.
+  "data": "A String", # The HTTP request/response body as raw binary.
+  "extensions": [ # Application specific response metadata. Must be set in the first response for streaming APIs.
+    {
+      "a_key": "", # Properties of the object. Contains field @type with type URL.
+    },
+  ],
+}
+
+  appId: string, Required. The App ID is supplied as an HTTP parameter. Unlike internal usage of App ID, it does not include a region prefix. Rather, the App ID represents the Project ID against which to make the request.
+  x__xgafv: string, V1 error format.
+    Allowed values
+      1 - v1 error format
+      2 - v2 error format
+
+Returns:
+  An object of the form:
+
+    { # 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); }
+}
+
+ + \ No newline at end of file diff --git a/docs/dyn/cloudtasks_v2beta2.html b/docs/dyn/cloudtasks_v2beta2.html index b52f00be9ac..52d0ca72517 100644 --- a/docs/dyn/cloudtasks_v2beta2.html +++ b/docs/dyn/cloudtasks_v2beta2.html @@ -74,6 +74,11 @@

Cloud Tasks API

Instance Methods

+

+ api() +

+

Returns the api Resource.

+

projects()

diff --git a/docs/dyn/cloudtasks_v2beta2.projects.locations.queues.html b/docs/dyn/cloudtasks_v2beta2.projects.locations.queues.html index d4d7ac8c27a..9a61f49b7db 100644 --- a/docs/dyn/cloudtasks_v2beta2.projects.locations.queues.html +++ b/docs/dyn/cloudtasks_v2beta2.projects.locations.queues.html @@ -146,8 +146,8 @@

Method Details

"headerOverrides": [ # HTTP target headers. This map contains the header field names and values. Headers will be set when running the task is created and/or task is created. These headers represent a subset of the headers that will accompany the task's HTTP request. Some HTTP request headers will be ignored or replaced. A partial list of headers that will be ignored or replaced is: * Any header that is prefixed with "X-Google-Cloud-Tasks-" will be treated as service header. Service headers define properties of the task and are predefined in CloudTask. * Host: This will be computed by Cloud Tasks and derived from HttpRequest.url. * Content-Length: This will be computed by Cloud Tasks. * User-Agent: This will be set to `"Google-Cloud-Tasks"`. * `X-Google-*`: Google use only. * `X-AppEngine-*`: Google use only. `Content-Type` won't be set by Cloud Tasks. You can explicitly set `Content-Type` to a media type when the task is created. For example, `Content-Type` can be set to `"application/octet-stream"` or `"application/json"`. Headers which can have multiple values (according to RFC2616) can be specified using comma-separated values. The size of the headers must be less than 80KB. Queue-level headers to override headers of all the tasks in the queue. { # Wraps the Header object. "header": { # Defines a header message. A header can have a key and a value. # header embodying a key and a value. - "key": "A String", - "value": "A String", + "key": "A String", # The key of the header. + "value": "A String", # The value of the header. }, }, ], @@ -218,8 +218,8 @@

Method Details

"headerOverrides": [ # HTTP target headers. This map contains the header field names and values. Headers will be set when running the task is created and/or task is created. These headers represent a subset of the headers that will accompany the task's HTTP request. Some HTTP request headers will be ignored or replaced. A partial list of headers that will be ignored or replaced is: * Any header that is prefixed with "X-Google-Cloud-Tasks-" will be treated as service header. Service headers define properties of the task and are predefined in CloudTask. * Host: This will be computed by Cloud Tasks and derived from HttpRequest.url. * Content-Length: This will be computed by Cloud Tasks. * User-Agent: This will be set to `"Google-Cloud-Tasks"`. * `X-Google-*`: Google use only. * `X-AppEngine-*`: Google use only. `Content-Type` won't be set by Cloud Tasks. You can explicitly set `Content-Type` to a media type when the task is created. For example, `Content-Type` can be set to `"application/octet-stream"` or `"application/json"`. Headers which can have multiple values (according to RFC2616) can be specified using comma-separated values. The size of the headers must be less than 80KB. Queue-level headers to override headers of all the tasks in the queue. { # Wraps the Header object. "header": { # Defines a header message. A header can have a key and a value. # header embodying a key and a value. - "key": "A String", - "value": "A String", + "key": "A String", # The key of the header. + "value": "A String", # The value of the header. }, }, ], @@ -316,8 +316,8 @@

Method Details

"headerOverrides": [ # HTTP target headers. This map contains the header field names and values. Headers will be set when running the task is created and/or task is created. These headers represent a subset of the headers that will accompany the task's HTTP request. Some HTTP request headers will be ignored or replaced. A partial list of headers that will be ignored or replaced is: * Any header that is prefixed with "X-Google-Cloud-Tasks-" will be treated as service header. Service headers define properties of the task and are predefined in CloudTask. * Host: This will be computed by Cloud Tasks and derived from HttpRequest.url. * Content-Length: This will be computed by Cloud Tasks. * User-Agent: This will be set to `"Google-Cloud-Tasks"`. * `X-Google-*`: Google use only. * `X-AppEngine-*`: Google use only. `Content-Type` won't be set by Cloud Tasks. You can explicitly set `Content-Type` to a media type when the task is created. For example, `Content-Type` can be set to `"application/octet-stream"` or `"application/json"`. Headers which can have multiple values (according to RFC2616) can be specified using comma-separated values. The size of the headers must be less than 80KB. Queue-level headers to override headers of all the tasks in the queue. { # Wraps the Header object. "header": { # Defines a header message. A header can have a key and a value. # header embodying a key and a value. - "key": "A String", - "value": "A String", + "key": "A String", # The key of the header. + "value": "A String", # The value of the header. }, }, ], @@ -445,8 +445,8 @@

Method Details

"headerOverrides": [ # HTTP target headers. This map contains the header field names and values. Headers will be set when running the task is created and/or task is created. These headers represent a subset of the headers that will accompany the task's HTTP request. Some HTTP request headers will be ignored or replaced. A partial list of headers that will be ignored or replaced is: * Any header that is prefixed with "X-Google-Cloud-Tasks-" will be treated as service header. Service headers define properties of the task and are predefined in CloudTask. * Host: This will be computed by Cloud Tasks and derived from HttpRequest.url. * Content-Length: This will be computed by Cloud Tasks. * User-Agent: This will be set to `"Google-Cloud-Tasks"`. * `X-Google-*`: Google use only. * `X-AppEngine-*`: Google use only. `Content-Type` won't be set by Cloud Tasks. You can explicitly set `Content-Type` to a media type when the task is created. For example, `Content-Type` can be set to `"application/octet-stream"` or `"application/json"`. Headers which can have multiple values (according to RFC2616) can be specified using comma-separated values. The size of the headers must be less than 80KB. Queue-level headers to override headers of all the tasks in the queue. { # Wraps the Header object. "header": { # Defines a header message. A header can have a key and a value. # header embodying a key and a value. - "key": "A String", - "value": "A String", + "key": "A String", # The key of the header. + "value": "A String", # The value of the header. }, }, ], @@ -535,8 +535,8 @@

Method Details

"headerOverrides": [ # HTTP target headers. This map contains the header field names and values. Headers will be set when running the task is created and/or task is created. These headers represent a subset of the headers that will accompany the task's HTTP request. Some HTTP request headers will be ignored or replaced. A partial list of headers that will be ignored or replaced is: * Any header that is prefixed with "X-Google-Cloud-Tasks-" will be treated as service header. Service headers define properties of the task and are predefined in CloudTask. * Host: This will be computed by Cloud Tasks and derived from HttpRequest.url. * Content-Length: This will be computed by Cloud Tasks. * User-Agent: This will be set to `"Google-Cloud-Tasks"`. * `X-Google-*`: Google use only. * `X-AppEngine-*`: Google use only. `Content-Type` won't be set by Cloud Tasks. You can explicitly set `Content-Type` to a media type when the task is created. For example, `Content-Type` can be set to `"application/octet-stream"` or `"application/json"`. Headers which can have multiple values (according to RFC2616) can be specified using comma-separated values. The size of the headers must be less than 80KB. Queue-level headers to override headers of all the tasks in the queue. { # Wraps the Header object. "header": { # Defines a header message. A header can have a key and a value. # header embodying a key and a value. - "key": "A String", - "value": "A String", + "key": "A String", # The key of the header. + "value": "A String", # The value of the header. }, }, ], @@ -608,8 +608,8 @@

Method Details

"headerOverrides": [ # HTTP target headers. This map contains the header field names and values. Headers will be set when running the task is created and/or task is created. These headers represent a subset of the headers that will accompany the task's HTTP request. Some HTTP request headers will be ignored or replaced. A partial list of headers that will be ignored or replaced is: * Any header that is prefixed with "X-Google-Cloud-Tasks-" will be treated as service header. Service headers define properties of the task and are predefined in CloudTask. * Host: This will be computed by Cloud Tasks and derived from HttpRequest.url. * Content-Length: This will be computed by Cloud Tasks. * User-Agent: This will be set to `"Google-Cloud-Tasks"`. * `X-Google-*`: Google use only. * `X-AppEngine-*`: Google use only. `Content-Type` won't be set by Cloud Tasks. You can explicitly set `Content-Type` to a media type when the task is created. For example, `Content-Type` can be set to `"application/octet-stream"` or `"application/json"`. Headers which can have multiple values (according to RFC2616) can be specified using comma-separated values. The size of the headers must be less than 80KB. Queue-level headers to override headers of all the tasks in the queue. { # Wraps the Header object. "header": { # Defines a header message. A header can have a key and a value. # header embodying a key and a value. - "key": "A String", - "value": "A String", + "key": "A String", # The key of the header. + "value": "A String", # The value of the header. }, }, ], @@ -693,8 +693,8 @@

Method Details

"headerOverrides": [ # HTTP target headers. This map contains the header field names and values. Headers will be set when running the task is created and/or task is created. These headers represent a subset of the headers that will accompany the task's HTTP request. Some HTTP request headers will be ignored or replaced. A partial list of headers that will be ignored or replaced is: * Any header that is prefixed with "X-Google-Cloud-Tasks-" will be treated as service header. Service headers define properties of the task and are predefined in CloudTask. * Host: This will be computed by Cloud Tasks and derived from HttpRequest.url. * Content-Length: This will be computed by Cloud Tasks. * User-Agent: This will be set to `"Google-Cloud-Tasks"`. * `X-Google-*`: Google use only. * `X-AppEngine-*`: Google use only. `Content-Type` won't be set by Cloud Tasks. You can explicitly set `Content-Type` to a media type when the task is created. For example, `Content-Type` can be set to `"application/octet-stream"` or `"application/json"`. Headers which can have multiple values (according to RFC2616) can be specified using comma-separated values. The size of the headers must be less than 80KB. Queue-level headers to override headers of all the tasks in the queue. { # Wraps the Header object. "header": { # Defines a header message. A header can have a key and a value. # header embodying a key and a value. - "key": "A String", - "value": "A String", + "key": "A String", # The key of the header. + "value": "A String", # The value of the header. }, }, ], @@ -778,8 +778,8 @@

Method Details

"headerOverrides": [ # HTTP target headers. This map contains the header field names and values. Headers will be set when running the task is created and/or task is created. These headers represent a subset of the headers that will accompany the task's HTTP request. Some HTTP request headers will be ignored or replaced. A partial list of headers that will be ignored or replaced is: * Any header that is prefixed with "X-Google-Cloud-Tasks-" will be treated as service header. Service headers define properties of the task and are predefined in CloudTask. * Host: This will be computed by Cloud Tasks and derived from HttpRequest.url. * Content-Length: This will be computed by Cloud Tasks. * User-Agent: This will be set to `"Google-Cloud-Tasks"`. * `X-Google-*`: Google use only. * `X-AppEngine-*`: Google use only. `Content-Type` won't be set by Cloud Tasks. You can explicitly set `Content-Type` to a media type when the task is created. For example, `Content-Type` can be set to `"application/octet-stream"` or `"application/json"`. Headers which can have multiple values (according to RFC2616) can be specified using comma-separated values. The size of the headers must be less than 80KB. Queue-level headers to override headers of all the tasks in the queue. { # Wraps the Header object. "header": { # Defines a header message. A header can have a key and a value. # header embodying a key and a value. - "key": "A String", - "value": "A String", + "key": "A String", # The key of the header. + "value": "A String", # The value of the header. }, }, ], @@ -863,8 +863,8 @@

Method Details

"headerOverrides": [ # HTTP target headers. This map contains the header field names and values. Headers will be set when running the task is created and/or task is created. These headers represent a subset of the headers that will accompany the task's HTTP request. Some HTTP request headers will be ignored or replaced. A partial list of headers that will be ignored or replaced is: * Any header that is prefixed with "X-Google-Cloud-Tasks-" will be treated as service header. Service headers define properties of the task and are predefined in CloudTask. * Host: This will be computed by Cloud Tasks and derived from HttpRequest.url. * Content-Length: This will be computed by Cloud Tasks. * User-Agent: This will be set to `"Google-Cloud-Tasks"`. * `X-Google-*`: Google use only. * `X-AppEngine-*`: Google use only. `Content-Type` won't be set by Cloud Tasks. You can explicitly set `Content-Type` to a media type when the task is created. For example, `Content-Type` can be set to `"application/octet-stream"` or `"application/json"`. Headers which can have multiple values (according to RFC2616) can be specified using comma-separated values. The size of the headers must be less than 80KB. Queue-level headers to override headers of all the tasks in the queue. { # Wraps the Header object. "header": { # Defines a header message. A header can have a key and a value. # header embodying a key and a value. - "key": "A String", - "value": "A String", + "key": "A String", # The key of the header. + "value": "A String", # The value of the header. }, }, ], diff --git a/docs/dyn/cloudtasks_v2beta2.projects.locations.queues.tasks.html b/docs/dyn/cloudtasks_v2beta2.projects.locations.queues.tasks.html index 156723c01b1..d4476efa816 100644 --- a/docs/dyn/cloudtasks_v2beta2.projects.locations.queues.tasks.html +++ b/docs/dyn/cloudtasks_v2beta2.projects.locations.queues.tasks.html @@ -78,8 +78,8 @@

Instance Methods

acknowledge(name, body=None, x__xgafv=None)

Acknowledges a pull task. The worker, that is, the entity that leased this task must call this method to indicate that the work associated with the task has finished. The worker must acknowledge a task within the lease_duration or the lease will expire and the task will become available to be leased again. After the task is acknowledged, it will not be returned by a later LeaseTasks, GetTask, or ListTasks.

- buffer(parent, body=None, x__xgafv=None)

-

Creates and buffers a new task without the need to explicitly define a Task message. The queue must have HTTP target. Note: This feature is in its experimental stage. You must request access to the API through the [Cloud Tasks BufferTasks Experiment Signup form](https://forms.gle/X8Zr5hiXH5tTGFqh8).

+ buffer(queue, taskId, body=None, x__xgafv=None)

+

Creates and buffers a new task without the need to explicitly define a Task message. The queue must have HTTP target. To create the task with a custom ID, use the following format and set TASK_ID to your desired ID: projects/PROJECT_ID/locations/LOCATION_ID/queues/QUEUE_ID/tasks/TASK_ID:buffer To create the task with an automatically generated ID, use the following format: projects/PROJECT_ID/locations/LOCATION_ID/queues/QUEUE_ID/tasks:buffer. Note: This feature is in its experimental stage. You must request access to the API through the [Cloud Tasks BufferTask Experiment Signup form](https://forms.gle/X8Zr5hiXH5tTGFqh8).

cancelLease(name, body=None, x__xgafv=None)

Cancel a pull task's lease. The worker can use this method to cancel a task's lease by setting its schedule_time to now. This will make the task available to be leased to the next caller of LeaseTasks.

@@ -137,16 +137,17 @@

Method Details

- buffer(parent, body=None, x__xgafv=None) - 
Creates and buffers a new task without the need to explicitly define a Task message. The queue must have HTTP target. Note: This feature is in its experimental stage. You must request access to the API through the [Cloud Tasks BufferTasks Experiment Signup form](https://forms.gle/X8Zr5hiXH5tTGFqh8).
+    buffer(queue, taskId, body=None, x__xgafv=None)
+  
Creates and buffers a new task without the need to explicitly define a Task message. The queue must have HTTP target. To create the task with a custom ID, use the following format and set TASK_ID to your desired ID: projects/PROJECT_ID/locations/LOCATION_ID/queues/QUEUE_ID/tasks/TASK_ID:buffer To create the task with an automatically generated ID, use the following format: projects/PROJECT_ID/locations/LOCATION_ID/queues/QUEUE_ID/tasks:buffer. Note: This feature is in its experimental stage. You must request access to the API through the [Cloud Tasks BufferTask Experiment Signup form](https://forms.gle/X8Zr5hiXH5tTGFqh8).
 
 Args:
-  parent: string, Required. The parent queue name. For example: projects/PROJECT_ID/locations/LOCATION_ID/queues/QUEUE_ID` The queue must already exist. (required)
+  queue: string, Required. The parent queue name. For example: projects/PROJECT_ID/locations/LOCATION_ID/queues/QUEUE_ID` The queue must already exist. (required)
+  taskId: string, Optional. Task ID for the task being created. If not provided, a random task ID is assigned to the task. (required)
   body: object, The request body.
     The object takes the form of:
 
-{ # Request message for BufferTask.
-  "body": { # Message that represents an arbitrary HTTP body. It should only be used for payload formats that can't be represented as JSON, such as raw binary or an HTML page. This message can be used both in streaming and non-streaming API methods in the request as well as the response. It can be used as a top-level request field, which is convenient if one wants to extract parameters from either the URL or HTTP template into the request fields and also want access to the raw HTTP body. Example: message GetResourceRequest { // A unique request id. string request_id = 1; // The raw HTTP body is bound to this field. google.api.HttpBody http_body = 2; } service ResourceService { rpc GetResource(GetResourceRequest) returns (google.api.HttpBody); rpc UpdateResource(google.api.HttpBody) returns (google.protobuf.Empty); } Example with streaming methods: service CaldavService { rpc GetCalendar(stream google.api.HttpBody) returns (stream google.api.HttpBody); rpc UpdateCalendar(stream google.api.HttpBody) returns (stream google.api.HttpBody); } Use of this type only changes how the request and response bodies are handled, all other features will continue to work unchanged. # Optional. Body of the HTTP request. The body can take any generic value. The value will be written to the HttpRequest of the [Task].
+{ # LINT.IfChange Request message for BufferTask.
+  "body": { # Message that represents an arbitrary HTTP body. It should only be used for payload formats that can't be represented as JSON, such as raw binary or an HTML page. This message can be used both in streaming and non-streaming API methods in the request as well as the response. It can be used as a top-level request field, which is convenient if one wants to extract parameters from either the URL or HTTP template into the request fields and also want access to the raw HTTP body. Example: message GetResourceRequest { // A unique request id. string request_id = 1; // The raw HTTP body is bound to this field. google.api.HttpBody http_body = 2; } service ResourceService { rpc GetResource(GetResourceRequest) returns (google.api.HttpBody); rpc UpdateResource(google.api.HttpBody) returns (google.protobuf.Empty); } Example with streaming methods: service CaldavService { rpc GetCalendar(stream google.api.HttpBody) returns (stream google.api.HttpBody); rpc UpdateCalendar(stream google.api.HttpBody) returns (stream google.api.HttpBody); } Use of this type only changes how the request and response bodies are handled, all other features will continue to work unchanged. # Optional. Body of the HTTP request. The body can take any generic value. The value is written to the HttpRequest of the [Task].
     "contentType": "A String", # The HTTP Content-Type header value specifying the content type of the body.
     "data": "A String", # The HTTP request/response body as raw binary.
     "extensions": [ # Application specific response metadata. Must be set in the first response for streaming APIs.
diff --git a/googleapiclient/discovery_cache/documents/cloudtasks.v2.json b/googleapiclient/discovery_cache/documents/cloudtasks.v2.json
index 4b791c289f8..dc3d14b1639 100644
--- a/googleapiclient/discovery_cache/documents/cloudtasks.v2.json
+++ b/googleapiclient/discovery_cache/documents/cloudtasks.v2.json
@@ -685,7 +685,7 @@
       }
     }
   },
-  "revision": "20220913",
+  "revision": "20220923",
   "rootUrl": "https://cloudtasks.googleapis.com/",
   "schemas": {
     "AppEngineHttpRequest": {
diff --git a/googleapiclient/discovery_cache/documents/cloudtasks.v2beta2.json b/googleapiclient/discovery_cache/documents/cloudtasks.v2beta2.json
index 0e15b885f75..c45b6ff1e05 100644
--- a/googleapiclient/discovery_cache/documents/cloudtasks.v2beta2.json
+++ b/googleapiclient/discovery_cache/documents/cloudtasks.v2beta2.json
@@ -105,6 +105,38 @@
   },
   "protocol": "rest",
   "resources": {
+    "api": {
+      "resources": {
+        "queue": {
+          "methods": {
+            "update": {
+              "description": "Update queue list by uploading a queue.yaml file. The queue.yaml file is supplied in the request body as a YAML encoded string. This method was added to support gcloud clients versions before 322.0.0. New clients should use CreateQueue instead of this method.",
+              "flatPath": "api/queue/update",
+              "httpMethod": "POST",
+              "id": "cloudtasks.api.queue.update",
+              "parameterOrder": [],
+              "parameters": {
+                "appId": {
+                  "description": "Required. The App ID is supplied as an HTTP parameter. Unlike internal usage of App ID, it does not include a region prefix. Rather, the App ID represents the Project ID against which to make the request.",
+                  "location": "query",
+                  "type": "string"
+                }
+              },
+              "path": "api/queue/update",
+              "request": {
+                "$ref": "HttpBody"
+              },
+              "response": {
+                "$ref": "Empty"
+              },
+              "scopes": [
+                "https://www.googleapis.com/auth/cloud-platform"
+              ]
+            }
+          }
+        }
+      }
+    },
     "projects": {
       "resources": {
         "locations": {
@@ -550,11 +582,11 @@
                       "httpMethod": "POST",
                       "id": "cloudtasks.projects.locations.queues.tasks.buffer",
                       "parameterOrder": [
-                        "parent",
+                        "queue",
                         "taskId"
                       ],
                       "parameters": {
-                        "parent": {
+                        "queue": {
                           "description": "Required. The parent queue name. For example: projects/PROJECT_ID/locations/LOCATION_ID/queues/QUEUE_ID` The queue must already exist.",
                           "location": "path",
                           "pattern": "^projects/[^/]+/locations/[^/]+/queues/[^/]+$",
@@ -568,7 +600,7 @@
                           "type": "string"
                         }
                       },
-                      "path": "v2beta2/{+parent}/tasks/{taskId}:buffer",
+                      "path": "v2beta2/{+queue}/tasks/{taskId}:buffer",
                       "request": {
                         "$ref": "BufferTaskRequest"
                       },
@@ -844,7 +876,7 @@
       }
     }
   },
-  "revision": "20220913",
+  "revision": "20220923",
   "rootUrl": "https://cloudtasks.googleapis.com/",
   "schemas": {
     "AcknowledgeTaskRequest": {
@@ -993,7 +1025,7 @@
       "type": "object"
     },
     "BufferTaskRequest": {
-      "description": "Request message for BufferTask.",
+      "description": "LINT.IfChange Request message for BufferTask.",
       "id": "BufferTaskRequest",
       "properties": {
         "body": {
@@ -1122,11 +1154,11 @@
       "id": "Header",
       "properties": {
         "key": {
-          "format": "byte",
+          "description": "The key of the header.",
           "type": "string"
         },
         "value": {
-          "format": "byte",
+          "description": "The value of the header.",
           "type": "string"
         }
       },
diff --git a/googleapiclient/discovery_cache/documents/cloudtasks.v2beta3.json b/googleapiclient/discovery_cache/documents/cloudtasks.v2beta3.json
index 17cfae56fdc..caf9f132d03 100644
--- a/googleapiclient/discovery_cache/documents/cloudtasks.v2beta3.json
+++ b/googleapiclient/discovery_cache/documents/cloudtasks.v2beta3.json
@@ -697,7 +697,7 @@
       }
     }
   },
-  "revision": "20220913",
+  "revision": "20220923",
   "rootUrl": "https://cloudtasks.googleapis.com/",
   "schemas": {
     "AppEngineHttpQueue": {