Google Cloud Native is in preview. Google Cloud Classic is fully supported.
Google Cloud Native v0.32.0 published on Wednesday, Nov 29, 2023 by Pulumi
google-native.cloudtasks/v2beta2.getQueue
Explore with Pulumi AI
Google Cloud Native is in preview. Google Cloud Classic is fully supported.
Google Cloud Native v0.32.0 published on Wednesday, Nov 29, 2023 by Pulumi
Gets a queue.
Using getQueue
Two invocation forms are available. The direct form accepts plain arguments and either blocks until the result value is available, or returns a Promise-wrapped result. The output form accepts Input-wrapped arguments and returns an Output-wrapped result.
function getQueue(args: GetQueueArgs, opts?: InvokeOptions): Promise<GetQueueResult>
function getQueueOutput(args: GetQueueOutputArgs, opts?: InvokeOptions): Output<GetQueueResult>
def get_queue(location: Optional[str] = None,
project: Optional[str] = None,
queue_id: Optional[str] = None,
read_mask: Optional[str] = None,
opts: Optional[InvokeOptions] = None) -> GetQueueResult
def get_queue_output(location: Optional[pulumi.Input[str]] = None,
project: Optional[pulumi.Input[str]] = None,
queue_id: Optional[pulumi.Input[str]] = None,
read_mask: Optional[pulumi.Input[str]] = None,
opts: Optional[InvokeOptions] = None) -> Output[GetQueueResult]
func LookupQueue(ctx *Context, args *LookupQueueArgs, opts ...InvokeOption) (*LookupQueueResult, error)
func LookupQueueOutput(ctx *Context, args *LookupQueueOutputArgs, opts ...InvokeOption) LookupQueueResultOutput
> Note: This function is named LookupQueue
in the Go SDK.
public static class GetQueue
{
public static Task<GetQueueResult> InvokeAsync(GetQueueArgs args, InvokeOptions? opts = null)
public static Output<GetQueueResult> Invoke(GetQueueInvokeArgs args, InvokeOptions? opts = null)
}
public static CompletableFuture<GetQueueResult> getQueue(GetQueueArgs args, InvokeOptions options)
// Output-based functions aren't available in Java yet
fn::invoke:
function: google-native:cloudtasks/v2beta2:getQueue
arguments:
# arguments dictionary
The following arguments are supported:
getQueue Result
The following output properties are available:
- App
Engine Pulumi.Http Target Google Native. Cloud Tasks. V2Beta2. Outputs. App Engine Http Target Response - App Engine HTTP target. An App Engine queue is a queue that has an AppEngineHttpTarget.
- Http
Target Pulumi.Google Native. Cloud Tasks. V2Beta2. Outputs. Http Target Response - An http_target is used to override the target values for HTTP tasks.
- Name string
- Caller-specified and required in CreateQueue, after which it becomes output only. The queue name. The queue name must have the following format:
projects/PROJECT_ID/locations/LOCATION_ID/queues/QUEUE_ID
*PROJECT_ID
can contain letters ([A-Za-z]), numbers ([0-9]), hyphens (-), colons (:), or periods (.). For more information, see Identifying projects *LOCATION_ID
is the canonical ID for the queue's location. The list of available locations can be obtained by calling ListLocations. For more information, see https://cloud.google.com/about/locations/. *QUEUE_ID
can contain letters ([A-Za-z]), numbers ([0-9]), or hyphens (-). The maximum length is 100 characters. - Pull
Target Pulumi.Google Native. Cloud Tasks. V2Beta2. Outputs. Pull Target Response - Pull target. A pull queue is a queue that has a PullTarget.
- Purge
Time string - The last time this queue was purged. All tasks that were created before this time were purged. A queue can be purged using PurgeQueue, the App Engine Task Queue SDK, or the Cloud Console. Purge time will be truncated to the nearest microsecond. Purge time will be unset if the queue has never been purged.
- Rate
Limits Pulumi.Google Native. Cloud Tasks. V2Beta2. Outputs. Rate Limits Response - Rate limits for task dispatches. rate_limits and retry_config are related because they both control task attempts however they control how tasks are attempted in different ways: * rate_limits controls the total rate of dispatches from a queue (i.e. all traffic dispatched from the queue, regardless of whether the dispatch is from a first attempt or a retry). * retry_config controls what happens to particular a task after its first attempt fails. That is, retry_config controls task retries (the second attempt, third attempt, etc).
- Retry
Config Pulumi.Google Native. Cloud Tasks. V2Beta2. Outputs. Retry Config Response - Settings that determine the retry behavior. * For tasks created using Cloud Tasks: the queue-level retry settings apply to all tasks in the queue that were created using Cloud Tasks. Retry settings cannot be set on individual tasks. * For tasks created using the App Engine SDK: the queue-level retry settings apply to all tasks in the queue which do not have retry settings explicitly set on the task and were created by the App Engine SDK. See App Engine documentation.
- State string
- The state of the queue.
state
can only be changed by called PauseQueue, ResumeQueue, or uploading queue.yaml/xml. UpdateQueue cannot be used to changestate
. - Stats
Pulumi.
Google Native. Cloud Tasks. V2Beta2. Outputs. Queue Stats Response - The realtime, informational statistics for a queue. In order to receive the statistics the caller should include this field in the FieldMask.
- Task
Ttl string - The maximum amount of time that a task will be retained in this queue. Queues created by Cloud Tasks have a default
task_ttl
of 31 days. After a task has lived fortask_ttl
, the task will be deleted regardless of whether it was dispatched or not. Thetask_ttl
for queues created via queue.yaml/xml is equal to the maximum duration because there is a storage quota for these queues. To view the maximum valid duration, see the documentation for Duration. - Tombstone
Ttl string - The task tombstone time to live (TTL). After a task is deleted or completed, the task's tombstone is retained for the length of time specified by
tombstone_ttl
. The tombstone is used by task de-duplication; another task with the same name can't be created until the tombstone has expired. For more information about task de-duplication, see the documentation for CreateTaskRequest. Queues created by Cloud Tasks have a defaulttombstone_ttl
of 1 hour.
- App
Engine AppHttp Target Engine Http Target Response - App Engine HTTP target. An App Engine queue is a queue that has an AppEngineHttpTarget.
- Http
Target HttpTarget Response - An http_target is used to override the target values for HTTP tasks.
- Name string
- Caller-specified and required in CreateQueue, after which it becomes output only. The queue name. The queue name must have the following format:
projects/PROJECT_ID/locations/LOCATION_ID/queues/QUEUE_ID
*PROJECT_ID
can contain letters ([A-Za-z]), numbers ([0-9]), hyphens (-), colons (:), or periods (.). For more information, see Identifying projects *LOCATION_ID
is the canonical ID for the queue's location. The list of available locations can be obtained by calling ListLocations. For more information, see https://cloud.google.com/about/locations/. *QUEUE_ID
can contain letters ([A-Za-z]), numbers ([0-9]), or hyphens (-). The maximum length is 100 characters. - Pull
Target PullTarget Response - Pull target. A pull queue is a queue that has a PullTarget.
- Purge
Time string - The last time this queue was purged. All tasks that were created before this time were purged. A queue can be purged using PurgeQueue, the App Engine Task Queue SDK, or the Cloud Console. Purge time will be truncated to the nearest microsecond. Purge time will be unset if the queue has never been purged.
- Rate
Limits RateLimits Response - Rate limits for task dispatches. rate_limits and retry_config are related because they both control task attempts however they control how tasks are attempted in different ways: * rate_limits controls the total rate of dispatches from a queue (i.e. all traffic dispatched from the queue, regardless of whether the dispatch is from a first attempt or a retry). * retry_config controls what happens to particular a task after its first attempt fails. That is, retry_config controls task retries (the second attempt, third attempt, etc).
- Retry
Config RetryConfig Response - Settings that determine the retry behavior. * For tasks created using Cloud Tasks: the queue-level retry settings apply to all tasks in the queue that were created using Cloud Tasks. Retry settings cannot be set on individual tasks. * For tasks created using the App Engine SDK: the queue-level retry settings apply to all tasks in the queue which do not have retry settings explicitly set on the task and were created by the App Engine SDK. See App Engine documentation.
- State string
- The state of the queue.
state
can only be changed by called PauseQueue, ResumeQueue, or uploading queue.yaml/xml. UpdateQueue cannot be used to changestate
. - Stats
Queue
Stats Response - The realtime, informational statistics for a queue. In order to receive the statistics the caller should include this field in the FieldMask.
- Task
Ttl string - The maximum amount of time that a task will be retained in this queue. Queues created by Cloud Tasks have a default
task_ttl
of 31 days. After a task has lived fortask_ttl
, the task will be deleted regardless of whether it was dispatched or not. Thetask_ttl
for queues created via queue.yaml/xml is equal to the maximum duration because there is a storage quota for these queues. To view the maximum valid duration, see the documentation for Duration. - Tombstone
Ttl string - The task tombstone time to live (TTL). After a task is deleted or completed, the task's tombstone is retained for the length of time specified by
tombstone_ttl
. The tombstone is used by task de-duplication; another task with the same name can't be created until the tombstone has expired. For more information about task de-duplication, see the documentation for CreateTaskRequest. Queues created by Cloud Tasks have a defaulttombstone_ttl
of 1 hour.
- app
Engine AppHttp Target Engine Http Target Response - App Engine HTTP target. An App Engine queue is a queue that has an AppEngineHttpTarget.
- http
Target HttpTarget Response - An http_target is used to override the target values for HTTP tasks.
- name String
- Caller-specified and required in CreateQueue, after which it becomes output only. The queue name. The queue name must have the following format:
projects/PROJECT_ID/locations/LOCATION_ID/queues/QUEUE_ID
*PROJECT_ID
can contain letters ([A-Za-z]), numbers ([0-9]), hyphens (-), colons (:), or periods (.). For more information, see Identifying projects *LOCATION_ID
is the canonical ID for the queue's location. The list of available locations can be obtained by calling ListLocations. For more information, see https://cloud.google.com/about/locations/. *QUEUE_ID
can contain letters ([A-Za-z]), numbers ([0-9]), or hyphens (-). The maximum length is 100 characters. - pull
Target PullTarget Response - Pull target. A pull queue is a queue that has a PullTarget.
- purge
Time String - The last time this queue was purged. All tasks that were created before this time were purged. A queue can be purged using PurgeQueue, the App Engine Task Queue SDK, or the Cloud Console. Purge time will be truncated to the nearest microsecond. Purge time will be unset if the queue has never been purged.
- rate
Limits RateLimits Response - Rate limits for task dispatches. rate_limits and retry_config are related because they both control task attempts however they control how tasks are attempted in different ways: * rate_limits controls the total rate of dispatches from a queue (i.e. all traffic dispatched from the queue, regardless of whether the dispatch is from a first attempt or a retry). * retry_config controls what happens to particular a task after its first attempt fails. That is, retry_config controls task retries (the second attempt, third attempt, etc).
- retry
Config RetryConfig Response - Settings that determine the retry behavior. * For tasks created using Cloud Tasks: the queue-level retry settings apply to all tasks in the queue that were created using Cloud Tasks. Retry settings cannot be set on individual tasks. * For tasks created using the App Engine SDK: the queue-level retry settings apply to all tasks in the queue which do not have retry settings explicitly set on the task and were created by the App Engine SDK. See App Engine documentation.
- state String
- The state of the queue.
state
can only be changed by called PauseQueue, ResumeQueue, or uploading queue.yaml/xml. UpdateQueue cannot be used to changestate
. - stats
Queue
Stats Response - The realtime, informational statistics for a queue. In order to receive the statistics the caller should include this field in the FieldMask.
- task
Ttl String - The maximum amount of time that a task will be retained in this queue. Queues created by Cloud Tasks have a default
task_ttl
of 31 days. After a task has lived fortask_ttl
, the task will be deleted regardless of whether it was dispatched or not. Thetask_ttl
for queues created via queue.yaml/xml is equal to the maximum duration because there is a storage quota for these queues. To view the maximum valid duration, see the documentation for Duration. - tombstone
Ttl String - The task tombstone time to live (TTL). After a task is deleted or completed, the task's tombstone is retained for the length of time specified by
tombstone_ttl
. The tombstone is used by task de-duplication; another task with the same name can't be created until the tombstone has expired. For more information about task de-duplication, see the documentation for CreateTaskRequest. Queues created by Cloud Tasks have a defaulttombstone_ttl
of 1 hour.
- app
Engine AppHttp Target Engine Http Target Response - App Engine HTTP target. An App Engine queue is a queue that has an AppEngineHttpTarget.
- http
Target HttpTarget Response - An http_target is used to override the target values for HTTP tasks.
- name string
- Caller-specified and required in CreateQueue, after which it becomes output only. The queue name. The queue name must have the following format:
projects/PROJECT_ID/locations/LOCATION_ID/queues/QUEUE_ID
*PROJECT_ID
can contain letters ([A-Za-z]), numbers ([0-9]), hyphens (-), colons (:), or periods (.). For more information, see Identifying projects *LOCATION_ID
is the canonical ID for the queue's location. The list of available locations can be obtained by calling ListLocations. For more information, see https://cloud.google.com/about/locations/. *QUEUE_ID
can contain letters ([A-Za-z]), numbers ([0-9]), or hyphens (-). The maximum length is 100 characters. - pull
Target PullTarget Response - Pull target. A pull queue is a queue that has a PullTarget.
- purge
Time string - The last time this queue was purged. All tasks that were created before this time were purged. A queue can be purged using PurgeQueue, the App Engine Task Queue SDK, or the Cloud Console. Purge time will be truncated to the nearest microsecond. Purge time will be unset if the queue has never been purged.
- rate
Limits RateLimits Response - Rate limits for task dispatches. rate_limits and retry_config are related because they both control task attempts however they control how tasks are attempted in different ways: * rate_limits controls the total rate of dispatches from a queue (i.e. all traffic dispatched from the queue, regardless of whether the dispatch is from a first attempt or a retry). * retry_config controls what happens to particular a task after its first attempt fails. That is, retry_config controls task retries (the second attempt, third attempt, etc).
- retry
Config RetryConfig Response - Settings that determine the retry behavior. * For tasks created using Cloud Tasks: the queue-level retry settings apply to all tasks in the queue that were created using Cloud Tasks. Retry settings cannot be set on individual tasks. * For tasks created using the App Engine SDK: the queue-level retry settings apply to all tasks in the queue which do not have retry settings explicitly set on the task and were created by the App Engine SDK. See App Engine documentation.
- state string
- The state of the queue.
state
can only be changed by called PauseQueue, ResumeQueue, or uploading queue.yaml/xml. UpdateQueue cannot be used to changestate
. - stats
Queue
Stats Response - The realtime, informational statistics for a queue. In order to receive the statistics the caller should include this field in the FieldMask.
- task
Ttl string - The maximum amount of time that a task will be retained in this queue. Queues created by Cloud Tasks have a default
task_ttl
of 31 days. After a task has lived fortask_ttl
, the task will be deleted regardless of whether it was dispatched or not. Thetask_ttl
for queues created via queue.yaml/xml is equal to the maximum duration because there is a storage quota for these queues. To view the maximum valid duration, see the documentation for Duration. - tombstone
Ttl string - The task tombstone time to live (TTL). After a task is deleted or completed, the task's tombstone is retained for the length of time specified by
tombstone_ttl
. The tombstone is used by task de-duplication; another task with the same name can't be created until the tombstone has expired. For more information about task de-duplication, see the documentation for CreateTaskRequest. Queues created by Cloud Tasks have a defaulttombstone_ttl
of 1 hour.
- app_
engine_ Apphttp_ target Engine Http Target Response - App Engine HTTP target. An App Engine queue is a queue that has an AppEngineHttpTarget.
- http_
target HttpTarget Response - An http_target is used to override the target values for HTTP tasks.
- name str
- Caller-specified and required in CreateQueue, after which it becomes output only. The queue name. The queue name must have the following format:
projects/PROJECT_ID/locations/LOCATION_ID/queues/QUEUE_ID
*PROJECT_ID
can contain letters ([A-Za-z]), numbers ([0-9]), hyphens (-), colons (:), or periods (.). For more information, see Identifying projects *LOCATION_ID
is the canonical ID for the queue's location. The list of available locations can be obtained by calling ListLocations. For more information, see https://cloud.google.com/about/locations/. *QUEUE_ID
can contain letters ([A-Za-z]), numbers ([0-9]), or hyphens (-). The maximum length is 100 characters. - pull_
target PullTarget Response - Pull target. A pull queue is a queue that has a PullTarget.
- purge_
time str - The last time this queue was purged. All tasks that were created before this time were purged. A queue can be purged using PurgeQueue, the App Engine Task Queue SDK, or the Cloud Console. Purge time will be truncated to the nearest microsecond. Purge time will be unset if the queue has never been purged.
- rate_
limits RateLimits Response - Rate limits for task dispatches. rate_limits and retry_config are related because they both control task attempts however they control how tasks are attempted in different ways: * rate_limits controls the total rate of dispatches from a queue (i.e. all traffic dispatched from the queue, regardless of whether the dispatch is from a first attempt or a retry). * retry_config controls what happens to particular a task after its first attempt fails. That is, retry_config controls task retries (the second attempt, third attempt, etc).
- retry_
config RetryConfig Response - Settings that determine the retry behavior. * For tasks created using Cloud Tasks: the queue-level retry settings apply to all tasks in the queue that were created using Cloud Tasks. Retry settings cannot be set on individual tasks. * For tasks created using the App Engine SDK: the queue-level retry settings apply to all tasks in the queue which do not have retry settings explicitly set on the task and were created by the App Engine SDK. See App Engine documentation.
- state str
- The state of the queue.
state
can only be changed by called PauseQueue, ResumeQueue, or uploading queue.yaml/xml. UpdateQueue cannot be used to changestate
. - stats
Queue
Stats Response - The realtime, informational statistics for a queue. In order to receive the statistics the caller should include this field in the FieldMask.
- task_
ttl str - The maximum amount of time that a task will be retained in this queue. Queues created by Cloud Tasks have a default
task_ttl
of 31 days. After a task has lived fortask_ttl
, the task will be deleted regardless of whether it was dispatched or not. Thetask_ttl
for queues created via queue.yaml/xml is equal to the maximum duration because there is a storage quota for these queues. To view the maximum valid duration, see the documentation for Duration. - tombstone_
ttl str - The task tombstone time to live (TTL). After a task is deleted or completed, the task's tombstone is retained for the length of time specified by
tombstone_ttl
. The tombstone is used by task de-duplication; another task with the same name can't be created until the tombstone has expired. For more information about task de-duplication, see the documentation for CreateTaskRequest. Queues created by Cloud Tasks have a defaulttombstone_ttl
of 1 hour.
- app
Engine Property MapHttp Target - App Engine HTTP target. An App Engine queue is a queue that has an AppEngineHttpTarget.
- http
Target Property Map - An http_target is used to override the target values for HTTP tasks.
- name String
- Caller-specified and required in CreateQueue, after which it becomes output only. The queue name. The queue name must have the following format:
projects/PROJECT_ID/locations/LOCATION_ID/queues/QUEUE_ID
*PROJECT_ID
can contain letters ([A-Za-z]), numbers ([0-9]), hyphens (-), colons (:), or periods (.). For more information, see Identifying projects *LOCATION_ID
is the canonical ID for the queue's location. The list of available locations can be obtained by calling ListLocations. For more information, see https://cloud.google.com/about/locations/. *QUEUE_ID
can contain letters ([A-Za-z]), numbers ([0-9]), or hyphens (-). The maximum length is 100 characters. - pull
Target Property Map - Pull target. A pull queue is a queue that has a PullTarget.
- purge
Time String - The last time this queue was purged. All tasks that were created before this time were purged. A queue can be purged using PurgeQueue, the App Engine Task Queue SDK, or the Cloud Console. Purge time will be truncated to the nearest microsecond. Purge time will be unset if the queue has never been purged.
- rate
Limits Property Map - Rate limits for task dispatches. rate_limits and retry_config are related because they both control task attempts however they control how tasks are attempted in different ways: * rate_limits controls the total rate of dispatches from a queue (i.e. all traffic dispatched from the queue, regardless of whether the dispatch is from a first attempt or a retry). * retry_config controls what happens to particular a task after its first attempt fails. That is, retry_config controls task retries (the second attempt, third attempt, etc).
- retry
Config Property Map - Settings that determine the retry behavior. * For tasks created using Cloud Tasks: the queue-level retry settings apply to all tasks in the queue that were created using Cloud Tasks. Retry settings cannot be set on individual tasks. * For tasks created using the App Engine SDK: the queue-level retry settings apply to all tasks in the queue which do not have retry settings explicitly set on the task and were created by the App Engine SDK. See App Engine documentation.
- state String
- The state of the queue.
state
can only be changed by called PauseQueue, ResumeQueue, or uploading queue.yaml/xml. UpdateQueue cannot be used to changestate
. - stats Property Map
- The realtime, informational statistics for a queue. In order to receive the statistics the caller should include this field in the FieldMask.
- task
Ttl String - The maximum amount of time that a task will be retained in this queue. Queues created by Cloud Tasks have a default
task_ttl
of 31 days. After a task has lived fortask_ttl
, the task will be deleted regardless of whether it was dispatched or not. Thetask_ttl
for queues created via queue.yaml/xml is equal to the maximum duration because there is a storage quota for these queues. To view the maximum valid duration, see the documentation for Duration. - tombstone
Ttl String - The task tombstone time to live (TTL). After a task is deleted or completed, the task's tombstone is retained for the length of time specified by
tombstone_ttl
. The tombstone is used by task de-duplication; another task with the same name can't be created until the tombstone has expired. For more information about task de-duplication, see the documentation for CreateTaskRequest. Queues created by Cloud Tasks have a defaulttombstone_ttl
of 1 hour.
Supporting Types
AppEngineHttpTargetResponse
- App
Engine Pulumi.Routing Override Google Native. Cloud Tasks. V2Beta2. Inputs. App Engine Routing Response - Overrides for the task-level app_engine_routing. If set,
app_engine_routing_override
is used for all tasks in the queue, no matter what the setting is for the task-level app_engine_routing.
- App
Engine AppRouting Override Engine Routing Response - Overrides for the task-level app_engine_routing. If set,
app_engine_routing_override
is used for all tasks in the queue, no matter what the setting is for the task-level app_engine_routing.
- app
Engine AppRouting Override Engine Routing Response - Overrides for the task-level app_engine_routing. If set,
app_engine_routing_override
is used for all tasks in the queue, no matter what the setting is for the task-level app_engine_routing.
- app
Engine AppRouting Override Engine Routing Response - Overrides for the task-level app_engine_routing. If set,
app_engine_routing_override
is used for all tasks in the queue, no matter what the setting is for the task-level app_engine_routing.
- app_
engine_ Approuting_ override Engine Routing Response - Overrides for the task-level app_engine_routing. If set,
app_engine_routing_override
is used for all tasks in the queue, no matter what the setting is for the task-level app_engine_routing.
- app
Engine Property MapRouting Override - Overrides for the task-level app_engine_routing. If set,
app_engine_routing_override
is used for all tasks in the queue, no matter what the setting is for the task-level app_engine_routing.
AppEngineRoutingResponse
- Host string
- The host that the task is sent to. For more information, see How Requests are Routed. The host is constructed as: *
host = [application_domain_name]
| [service] + '.' + [application_domain_name]
| [version] + '.' + [application_domain_name]
| [version_dot_service]+ '.' + [application_domain_name]
| [instance] + '.' + [application_domain_name]
| [instance_dot_service] + '.' + [application_domain_name]
| [instance_dot_version] + '.' + [application_domain_name]
| [instance_dot_version_dot_service] + '.' + [application_domain_name]
*application_domain_name
= The domain name of the app, for example .appspot.com, which is associated with the queue's project ID. Some tasks which were created using the App Engine SDK use a custom domain name. *service =
service *version =
version *version_dot_service =
version+ '.' +
service *instance =
instance *instance_dot_service =
instance+ '.' +
service *instance_dot_version =
instance+ '.' +
version *instance_dot_version_dot_service =
instance+ '.' +
version+ '.' +
service If service is empty, then the task will be sent to the service which is the default service when the task is attempted. If version is empty, then the task will be sent to the version which is the default version when the task is attempted. If instance is empty, then the task will be sent to an instance which is available when the task is attempted. If service, version, or instance is invalid, then the task will be sent to the default version of the default service when the task is attempted. - Instance string
- App instance. By default, the task is sent to an instance which is available when the task is attempted. Requests can only be sent to a specific instance if manual scaling is used in App Engine Standard. App Engine Flex does not support instances. For more information, see App Engine Standard request routing and App Engine Flex request routing.
- Service string
- App service. By default, the task is sent to the service which is the default service when the task is attempted. For some queues or tasks which were created using the App Engine Task Queue API, host is not parsable into service, version, and instance. For example, some tasks which were created using the App Engine SDK use a custom domain name; custom domains are not parsed by Cloud Tasks. If host is not parsable, then service, version, and instance are the empty string.
- Version string
- App version. By default, the task is sent to the version which is the default version when the task is attempted. For some queues or tasks which were created using the App Engine Task Queue API, host is not parsable into service, version, and instance. For example, some tasks which were created using the App Engine SDK use a custom domain name; custom domains are not parsed by Cloud Tasks. If host is not parsable, then service, version, and instance are the empty string.
- Host string
- The host that the task is sent to. For more information, see How Requests are Routed. The host is constructed as: *
host = [application_domain_name]
| [service] + '.' + [application_domain_name]
| [version] + '.' + [application_domain_name]
| [version_dot_service]+ '.' + [application_domain_name]
| [instance] + '.' + [application_domain_name]
| [instance_dot_service] + '.' + [application_domain_name]
| [instance_dot_version] + '.' + [application_domain_name]
| [instance_dot_version_dot_service] + '.' + [application_domain_name]
*application_domain_name
= The domain name of the app, for example .appspot.com, which is associated with the queue's project ID. Some tasks which were created using the App Engine SDK use a custom domain name. *service =
service *version =
version *version_dot_service =
version+ '.' +
service *instance =
instance *instance_dot_service =
instance+ '.' +
service *instance_dot_version =
instance+ '.' +
version *instance_dot_version_dot_service =
instance+ '.' +
version+ '.' +
service If service is empty, then the task will be sent to the service which is the default service when the task is attempted. If version is empty, then the task will be sent to the version which is the default version when the task is attempted. If instance is empty, then the task will be sent to an instance which is available when the task is attempted. If service, version, or instance is invalid, then the task will be sent to the default version of the default service when the task is attempted. - Instance string
- App instance. By default, the task is sent to an instance which is available when the task is attempted. Requests can only be sent to a specific instance if manual scaling is used in App Engine Standard. App Engine Flex does not support instances. For more information, see App Engine Standard request routing and App Engine Flex request routing.
- Service string
- App service. By default, the task is sent to the service which is the default service when the task is attempted. For some queues or tasks which were created using the App Engine Task Queue API, host is not parsable into service, version, and instance. For example, some tasks which were created using the App Engine SDK use a custom domain name; custom domains are not parsed by Cloud Tasks. If host is not parsable, then service, version, and instance are the empty string.
- Version string
- App version. By default, the task is sent to the version which is the default version when the task is attempted. For some queues or tasks which were created using the App Engine Task Queue API, host is not parsable into service, version, and instance. For example, some tasks which were created using the App Engine SDK use a custom domain name; custom domains are not parsed by Cloud Tasks. If host is not parsable, then service, version, and instance are the empty string.
- host String
- The host that the task is sent to. For more information, see How Requests are Routed. The host is constructed as: *
host = [application_domain_name]
| [service] + '.' + [application_domain_name]
| [version] + '.' + [application_domain_name]
| [version_dot_service]+ '.' + [application_domain_name]
| [instance] + '.' + [application_domain_name]
| [instance_dot_service] + '.' + [application_domain_name]
| [instance_dot_version] + '.' + [application_domain_name]
| [instance_dot_version_dot_service] + '.' + [application_domain_name]
*application_domain_name
= The domain name of the app, for example .appspot.com, which is associated with the queue's project ID. Some tasks which were created using the App Engine SDK use a custom domain name. *service =
service *version =
version *version_dot_service =
version+ '.' +
service *instance =
instance *instance_dot_service =
instance+ '.' +
service *instance_dot_version =
instance+ '.' +
version *instance_dot_version_dot_service =
instance+ '.' +
version+ '.' +
service If service is empty, then the task will be sent to the service which is the default service when the task is attempted. If version is empty, then the task will be sent to the version which is the default version when the task is attempted. If instance is empty, then the task will be sent to an instance which is available when the task is attempted. If service, version, or instance is invalid, then the task will be sent to the default version of the default service when the task is attempted. - instance String
- App instance. By default, the task is sent to an instance which is available when the task is attempted. Requests can only be sent to a specific instance if manual scaling is used in App Engine Standard. App Engine Flex does not support instances. For more information, see App Engine Standard request routing and App Engine Flex request routing.
- service String
- App service. By default, the task is sent to the service which is the default service when the task is attempted. For some queues or tasks which were created using the App Engine Task Queue API, host is not parsable into service, version, and instance. For example, some tasks which were created using the App Engine SDK use a custom domain name; custom domains are not parsed by Cloud Tasks. If host is not parsable, then service, version, and instance are the empty string.
- version String
- App version. By default, the task is sent to the version which is the default version when the task is attempted. For some queues or tasks which were created using the App Engine Task Queue API, host is not parsable into service, version, and instance. For example, some tasks which were created using the App Engine SDK use a custom domain name; custom domains are not parsed by Cloud Tasks. If host is not parsable, then service, version, and instance are the empty string.
- host string
- The host that the task is sent to. For more information, see How Requests are Routed. The host is constructed as: *
host = [application_domain_name]
| [service] + '.' + [application_domain_name]
| [version] + '.' + [application_domain_name]
| [version_dot_service]+ '.' + [application_domain_name]
| [instance] + '.' + [application_domain_name]
| [instance_dot_service] + '.' + [application_domain_name]
| [instance_dot_version] + '.' + [application_domain_name]
| [instance_dot_version_dot_service] + '.' + [application_domain_name]
*application_domain_name
= The domain name of the app, for example .appspot.com, which is associated with the queue's project ID. Some tasks which were created using the App Engine SDK use a custom domain name. *service =
service *version =
version *version_dot_service =
version+ '.' +
service *instance =
instance *instance_dot_service =
instance+ '.' +
service *instance_dot_version =
instance+ '.' +
version *instance_dot_version_dot_service =
instance+ '.' +
version+ '.' +
service If service is empty, then the task will be sent to the service which is the default service when the task is attempted. If version is empty, then the task will be sent to the version which is the default version when the task is attempted. If instance is empty, then the task will be sent to an instance which is available when the task is attempted. If service, version, or instance is invalid, then the task will be sent to the default version of the default service when the task is attempted. - instance string
- App instance. By default, the task is sent to an instance which is available when the task is attempted. Requests can only be sent to a specific instance if manual scaling is used in App Engine Standard. App Engine Flex does not support instances. For more information, see App Engine Standard request routing and App Engine Flex request routing.
- service string
- App service. By default, the task is sent to the service which is the default service when the task is attempted. For some queues or tasks which were created using the App Engine Task Queue API, host is not parsable into service, version, and instance. For example, some tasks which were created using the App Engine SDK use a custom domain name; custom domains are not parsed by Cloud Tasks. If host is not parsable, then service, version, and instance are the empty string.
- version string
- App version. By default, the task is sent to the version which is the default version when the task is attempted. For some queues or tasks which were created using the App Engine Task Queue API, host is not parsable into service, version, and instance. For example, some tasks which were created using the App Engine SDK use a custom domain name; custom domains are not parsed by Cloud Tasks. If host is not parsable, then service, version, and instance are the empty string.
- host str
- The host that the task is sent to. For more information, see How Requests are Routed. The host is constructed as: *
host = [application_domain_name]
| [service] + '.' + [application_domain_name]
| [version] + '.' + [application_domain_name]
| [version_dot_service]+ '.' + [application_domain_name]
| [instance] + '.' + [application_domain_name]
| [instance_dot_service] + '.' + [application_domain_name]
| [instance_dot_version] + '.' + [application_domain_name]
| [instance_dot_version_dot_service] + '.' + [application_domain_name]
*application_domain_name
= The domain name of the app, for example .appspot.com, which is associated with the queue's project ID. Some tasks which were created using the App Engine SDK use a custom domain name. *service =
service *version =
version *version_dot_service =
version+ '.' +
service *instance =
instance *instance_dot_service =
instance+ '.' +
service *instance_dot_version =
instance+ '.' +
version *instance_dot_version_dot_service =
instance+ '.' +
version+ '.' +
service If service is empty, then the task will be sent to the service which is the default service when the task is attempted. If version is empty, then the task will be sent to the version which is the default version when the task is attempted. If instance is empty, then the task will be sent to an instance which is available when the task is attempted. If service, version, or instance is invalid, then the task will be sent to the default version of the default service when the task is attempted. - instance str
- App instance. By default, the task is sent to an instance which is available when the task is attempted. Requests can only be sent to a specific instance if manual scaling is used in App Engine Standard. App Engine Flex does not support instances. For more information, see App Engine Standard request routing and App Engine Flex request routing.
- service str
- App service. By default, the task is sent to the service which is the default service when the task is attempted. For some queues or tasks which were created using the App Engine Task Queue API, host is not parsable into service, version, and instance. For example, some tasks which were created using the App Engine SDK use a custom domain name; custom domains are not parsed by Cloud Tasks. If host is not parsable, then service, version, and instance are the empty string.
- version str
- App version. By default, the task is sent to the version which is the default version when the task is attempted. For some queues or tasks which were created using the App Engine Task Queue API, host is not parsable into service, version, and instance. For example, some tasks which were created using the App Engine SDK use a custom domain name; custom domains are not parsed by Cloud Tasks. If host is not parsable, then service, version, and instance are the empty string.
- host String
- The host that the task is sent to. For more information, see How Requests are Routed. The host is constructed as: *
host = [application_domain_name]
| [service] + '.' + [application_domain_name]
| [version] + '.' + [application_domain_name]
| [version_dot_service]+ '.' + [application_domain_name]
| [instance] + '.' + [application_domain_name]
| [instance_dot_service] + '.' + [application_domain_name]
| [instance_dot_version] + '.' + [application_domain_name]
| [instance_dot_version_dot_service] + '.' + [application_domain_name]
*application_domain_name
= The domain name of the app, for example .appspot.com, which is associated with the queue's project ID. Some tasks which were created using the App Engine SDK use a custom domain name. *service =
service *version =
version *version_dot_service =
version+ '.' +
service *instance =
instance *instance_dot_service =
instance+ '.' +
service *instance_dot_version =
instance+ '.' +
version *instance_dot_version_dot_service =
instance+ '.' +
version+ '.' +
service If service is empty, then the task will be sent to the service which is the default service when the task is attempted. If version is empty, then the task will be sent to the version which is the default version when the task is attempted. If instance is empty, then the task will be sent to an instance which is available when the task is attempted. If service, version, or instance is invalid, then the task will be sent to the default version of the default service when the task is attempted. - instance String
- App instance. By default, the task is sent to an instance which is available when the task is attempted. Requests can only be sent to a specific instance if manual scaling is used in App Engine Standard. App Engine Flex does not support instances. For more information, see App Engine Standard request routing and App Engine Flex request routing.
- service String
- App service. By default, the task is sent to the service which is the default service when the task is attempted. For some queues or tasks which were created using the App Engine Task Queue API, host is not parsable into service, version, and instance. For example, some tasks which were created using the App Engine SDK use a custom domain name; custom domains are not parsed by Cloud Tasks. If host is not parsable, then service, version, and instance are the empty string.
- version String
- App version. By default, the task is sent to the version which is the default version when the task is attempted. For some queues or tasks which were created using the App Engine Task Queue API, host is not parsable into service, version, and instance. For example, some tasks which were created using the App Engine SDK use a custom domain name; custom domains are not parsed by Cloud Tasks. If host is not parsable, then service, version, and instance are the empty string.
HeaderOverrideResponse
- Header
Pulumi.
Google Native. Cloud Tasks. V2Beta2. Inputs. Header Response - header embodying a key and a value.
- Header
Header
Response - header embodying a key and a value.
- header
Header
Response - header embodying a key and a value.
- header
Header
Response - header embodying a key and a value.
- header
Header
Response - header embodying a key and a value.
- header Property Map
- header embodying a key and a value.
HeaderResponse
HttpTargetResponse
- Header
Overrides List<Pulumi.Google Native. Cloud Tasks. V2Beta2. Inputs. Header Override Response> - 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-CloudTasks-" 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-CloudTasks"
. *X-Google-*
: Google use only. *X-AppEngine-*
: Google use only.Content-Type
won't be set by Cloud Tasks. You can explicitly setContent-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. - Http
Method string - The HTTP method to use for the request. When specified, it overrides HttpRequest for the task. Note that if the value is set to HttpMethod the HttpRequest of the task will be ignored at execution time.
- Oauth
Token Pulumi.Google Native. Cloud Tasks. V2Beta2. Inputs. OAuth Token Response - If specified, an OAuth token will be generated and attached as an
Authorization
header in the HTTP request. This type of authorization should generally only be used when calling Google APIs hosted on *.googleapis.com. - Oidc
Token Pulumi.Google Native. Cloud Tasks. V2Beta2. Inputs. Oidc Token Response - If specified, an OIDC token will be generated and attached as an
Authorization
header in the HTTP request. This type of authorization can be used for many scenarios, including calling Cloud Run, or endpoints where you intend to validate the token yourself. - Uri
Override Pulumi.Google Native. Cloud Tasks. V2Beta2. Inputs. Uri Override Response - Uri override. When specified, overrides the execution Uri for all the tasks in the queue.
- Header
Overrides []HeaderOverride Response - 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-CloudTasks-" 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-CloudTasks"
. *X-Google-*
: Google use only. *X-AppEngine-*
: Google use only.Content-Type
won't be set by Cloud Tasks. You can explicitly setContent-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. - Http
Method string - The HTTP method to use for the request. When specified, it overrides HttpRequest for the task. Note that if the value is set to HttpMethod the HttpRequest of the task will be ignored at execution time.
- Oauth
Token OAuthToken Response - If specified, an OAuth token will be generated and attached as an
Authorization
header in the HTTP request. This type of authorization should generally only be used when calling Google APIs hosted on *.googleapis.com. - Oidc
Token OidcToken Response - If specified, an OIDC token will be generated and attached as an
Authorization
header in the HTTP request. This type of authorization can be used for many scenarios, including calling Cloud Run, or endpoints where you intend to validate the token yourself. - Uri
Override UriOverride Response - Uri override. When specified, overrides the execution Uri for all the tasks in the queue.
- header
Overrides List<HeaderOverride Response> - 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-CloudTasks-" 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-CloudTasks"
. *X-Google-*
: Google use only. *X-AppEngine-*
: Google use only.Content-Type
won't be set by Cloud Tasks. You can explicitly setContent-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. - http
Method String - The HTTP method to use for the request. When specified, it overrides HttpRequest for the task. Note that if the value is set to HttpMethod the HttpRequest of the task will be ignored at execution time.
- oauth
Token OAuthToken Response - If specified, an OAuth token will be generated and attached as an
Authorization
header in the HTTP request. This type of authorization should generally only be used when calling Google APIs hosted on *.googleapis.com. - oidc
Token OidcToken Response - If specified, an OIDC token will be generated and attached as an
Authorization
header in the HTTP request. This type of authorization can be used for many scenarios, including calling Cloud Run, or endpoints where you intend to validate the token yourself. - uri
Override UriOverride Response - Uri override. When specified, overrides the execution Uri for all the tasks in the queue.
- header
Overrides HeaderOverride Response[] - 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-CloudTasks-" 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-CloudTasks"
. *X-Google-*
: Google use only. *X-AppEngine-*
: Google use only.Content-Type
won't be set by Cloud Tasks. You can explicitly setContent-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. - http
Method string - The HTTP method to use for the request. When specified, it overrides HttpRequest for the task. Note that if the value is set to HttpMethod the HttpRequest of the task will be ignored at execution time.
- oauth
Token OAuthToken Response - If specified, an OAuth token will be generated and attached as an
Authorization
header in the HTTP request. This type of authorization should generally only be used when calling Google APIs hosted on *.googleapis.com. - oidc
Token OidcToken Response - If specified, an OIDC token will be generated and attached as an
Authorization
header in the HTTP request. This type of authorization can be used for many scenarios, including calling Cloud Run, or endpoints where you intend to validate the token yourself. - uri
Override UriOverride Response - Uri override. When specified, overrides the execution Uri for all the tasks in the queue.
- header_
overrides Sequence[HeaderOverride Response] - 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-CloudTasks-" 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-CloudTasks"
. *X-Google-*
: Google use only. *X-AppEngine-*
: Google use only.Content-Type
won't be set by Cloud Tasks. You can explicitly setContent-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. - http_
method str - The HTTP method to use for the request. When specified, it overrides HttpRequest for the task. Note that if the value is set to HttpMethod the HttpRequest of the task will be ignored at execution time.
- oauth_
token OAuthToken Response - If specified, an OAuth token will be generated and attached as an
Authorization
header in the HTTP request. This type of authorization should generally only be used when calling Google APIs hosted on *.googleapis.com. - oidc_
token OidcToken Response - If specified, an OIDC token will be generated and attached as an
Authorization
header in the HTTP request. This type of authorization can be used for many scenarios, including calling Cloud Run, or endpoints where you intend to validate the token yourself. - uri_
override UriOverride Response - Uri override. When specified, overrides the execution Uri for all the tasks in the queue.
- header
Overrides List<Property Map> - 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-CloudTasks-" 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-CloudTasks"
. *X-Google-*
: Google use only. *X-AppEngine-*
: Google use only.Content-Type
won't be set by Cloud Tasks. You can explicitly setContent-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. - http
Method String - The HTTP method to use for the request. When specified, it overrides HttpRequest for the task. Note that if the value is set to HttpMethod the HttpRequest of the task will be ignored at execution time.
- oauth
Token Property Map - If specified, an OAuth token will be generated and attached as an
Authorization
header in the HTTP request. This type of authorization should generally only be used when calling Google APIs hosted on *.googleapis.com. - oidc
Token Property Map - If specified, an OIDC token will be generated and attached as an
Authorization
header in the HTTP request. This type of authorization can be used for many scenarios, including calling Cloud Run, or endpoints where you intend to validate the token yourself. - uri
Override Property Map - Uri override. When specified, overrides the execution Uri for all the tasks in the queue.
OAuthTokenResponse
- Scope string
- OAuth scope to be used for generating OAuth access token. If not specified, "https://www.googleapis.com/auth/cloud-platform" will be used.
- Service
Account stringEmail - Service account email to be used for generating OAuth token. The service account must be within the same project as the queue. The caller must have iam.serviceAccounts.actAs permission for the service account.
- Scope string
- OAuth scope to be used for generating OAuth access token. If not specified, "https://www.googleapis.com/auth/cloud-platform" will be used.
- Service
Account stringEmail - Service account email to be used for generating OAuth token. The service account must be within the same project as the queue. The caller must have iam.serviceAccounts.actAs permission for the service account.
- scope String
- OAuth scope to be used for generating OAuth access token. If not specified, "https://www.googleapis.com/auth/cloud-platform" will be used.
- service
Account StringEmail - Service account email to be used for generating OAuth token. The service account must be within the same project as the queue. The caller must have iam.serviceAccounts.actAs permission for the service account.
- scope string
- OAuth scope to be used for generating OAuth access token. If not specified, "https://www.googleapis.com/auth/cloud-platform" will be used.
- service
Account stringEmail - Service account email to be used for generating OAuth token. The service account must be within the same project as the queue. The caller must have iam.serviceAccounts.actAs permission for the service account.
- scope str
- OAuth scope to be used for generating OAuth access token. If not specified, "https://www.googleapis.com/auth/cloud-platform" will be used.
- service_
account_ stremail - Service account email to be used for generating OAuth token. The service account must be within the same project as the queue. The caller must have iam.serviceAccounts.actAs permission for the service account.
- scope String
- OAuth scope to be used for generating OAuth access token. If not specified, "https://www.googleapis.com/auth/cloud-platform" will be used.
- service
Account StringEmail - Service account email to be used for generating OAuth token. The service account must be within the same project as the queue. The caller must have iam.serviceAccounts.actAs permission for the service account.
OidcTokenResponse
- Audience string
- Audience to be used when generating OIDC token. If not specified, the URI specified in target will be used.
- Service
Account stringEmail - Service account email to be used for generating OIDC token. The service account must be within the same project as the queue. The caller must have iam.serviceAccounts.actAs permission for the service account.
- Audience string
- Audience to be used when generating OIDC token. If not specified, the URI specified in target will be used.
- Service
Account stringEmail - Service account email to be used for generating OIDC token. The service account must be within the same project as the queue. The caller must have iam.serviceAccounts.actAs permission for the service account.
- audience String
- Audience to be used when generating OIDC token. If not specified, the URI specified in target will be used.
- service
Account StringEmail - Service account email to be used for generating OIDC token. The service account must be within the same project as the queue. The caller must have iam.serviceAccounts.actAs permission for the service account.
- audience string
- Audience to be used when generating OIDC token. If not specified, the URI specified in target will be used.
- service
Account stringEmail - Service account email to be used for generating OIDC token. The service account must be within the same project as the queue. The caller must have iam.serviceAccounts.actAs permission for the service account.
- audience str
- Audience to be used when generating OIDC token. If not specified, the URI specified in target will be used.
- service_
account_ stremail - Service account email to be used for generating OIDC token. The service account must be within the same project as the queue. The caller must have iam.serviceAccounts.actAs permission for the service account.
- audience String
- Audience to be used when generating OIDC token. If not specified, the URI specified in target will be used.
- service
Account StringEmail - Service account email to be used for generating OIDC token. The service account must be within the same project as the queue. The caller must have iam.serviceAccounts.actAs permission for the service account.
PathOverrideResponse
- Path string
- The URI path (e.g., /users/1234). Default is an empty string.
- Path string
- The URI path (e.g., /users/1234). Default is an empty string.
- path String
- The URI path (e.g., /users/1234). Default is an empty string.
- path string
- The URI path (e.g., /users/1234). Default is an empty string.
- path str
- The URI path (e.g., /users/1234). Default is an empty string.
- path String
- The URI path (e.g., /users/1234). Default is an empty string.
QueryOverrideResponse
- Query
Params string - The query parameters (e.g., qparam1=123&qparam2=456). Default is an empty string.
- Query
Params string - The query parameters (e.g., qparam1=123&qparam2=456). Default is an empty string.
- query
Params String - The query parameters (e.g., qparam1=123&qparam2=456). Default is an empty string.
- query
Params string - The query parameters (e.g., qparam1=123&qparam2=456). Default is an empty string.
- query_
params str - The query parameters (e.g., qparam1=123&qparam2=456). Default is an empty string.
- query
Params String - The query parameters (e.g., qparam1=123&qparam2=456). Default is an empty string.
QueueStatsResponse
- Concurrent
Dispatches stringCount - The number of requests that the queue has dispatched but has not received a reply for yet.
- Effective
Execution doubleRate - The current maximum number of tasks per second executed by the queue. The maximum value of this variable is controlled by the RateLimits of the Queue. However, this value could be less to avoid overloading the endpoints tasks in the queue are targeting.
- Executed
Last stringMinute Count - The number of tasks that the queue has dispatched and received a reply for during the last minute. This variable counts both successful and non-successful executions.
- Oldest
Estimated stringArrival Time - An estimation of the nearest time in the future where a task in the queue is scheduled to be executed.
- Tasks
Count string - An estimation of the number of tasks in the queue, that is, the tasks in the queue that haven't been executed, the tasks in the queue which the queue has dispatched but has not yet received a reply for, and the failed tasks that the queue is retrying.
- Concurrent
Dispatches stringCount - The number of requests that the queue has dispatched but has not received a reply for yet.
- Effective
Execution float64Rate - The current maximum number of tasks per second executed by the queue. The maximum value of this variable is controlled by the RateLimits of the Queue. However, this value could be less to avoid overloading the endpoints tasks in the queue are targeting.
- Executed
Last stringMinute Count - The number of tasks that the queue has dispatched and received a reply for during the last minute. This variable counts both successful and non-successful executions.
- Oldest
Estimated stringArrival Time - An estimation of the nearest time in the future where a task in the queue is scheduled to be executed.
- Tasks
Count string - An estimation of the number of tasks in the queue, that is, the tasks in the queue that haven't been executed, the tasks in the queue which the queue has dispatched but has not yet received a reply for, and the failed tasks that the queue is retrying.
- concurrent
Dispatches StringCount - The number of requests that the queue has dispatched but has not received a reply for yet.
- effective
Execution DoubleRate - The current maximum number of tasks per second executed by the queue. The maximum value of this variable is controlled by the RateLimits of the Queue. However, this value could be less to avoid overloading the endpoints tasks in the queue are targeting.
- executed
Last StringMinute Count - The number of tasks that the queue has dispatched and received a reply for during the last minute. This variable counts both successful and non-successful executions.
- oldest
Estimated StringArrival Time - An estimation of the nearest time in the future where a task in the queue is scheduled to be executed.
- tasks
Count String - An estimation of the number of tasks in the queue, that is, the tasks in the queue that haven't been executed, the tasks in the queue which the queue has dispatched but has not yet received a reply for, and the failed tasks that the queue is retrying.
- concurrent
Dispatches stringCount - The number of requests that the queue has dispatched but has not received a reply for yet.
- effective
Execution numberRate - The current maximum number of tasks per second executed by the queue. The maximum value of this variable is controlled by the RateLimits of the Queue. However, this value could be less to avoid overloading the endpoints tasks in the queue are targeting.
- executed
Last stringMinute Count - The number of tasks that the queue has dispatched and received a reply for during the last minute. This variable counts both successful and non-successful executions.
- oldest
Estimated stringArrival Time - An estimation of the nearest time in the future where a task in the queue is scheduled to be executed.
- tasks
Count string - An estimation of the number of tasks in the queue, that is, the tasks in the queue that haven't been executed, the tasks in the queue which the queue has dispatched but has not yet received a reply for, and the failed tasks that the queue is retrying.
- concurrent_
dispatches_ strcount - The number of requests that the queue has dispatched but has not received a reply for yet.
- effective_
execution_ floatrate - The current maximum number of tasks per second executed by the queue. The maximum value of this variable is controlled by the RateLimits of the Queue. However, this value could be less to avoid overloading the endpoints tasks in the queue are targeting.
- executed_
last_ strminute_ count - The number of tasks that the queue has dispatched and received a reply for during the last minute. This variable counts both successful and non-successful executions.
- oldest_
estimated_ strarrival_ time - An estimation of the nearest time in the future where a task in the queue is scheduled to be executed.
- tasks_
count str - An estimation of the number of tasks in the queue, that is, the tasks in the queue that haven't been executed, the tasks in the queue which the queue has dispatched but has not yet received a reply for, and the failed tasks that the queue is retrying.
- concurrent
Dispatches StringCount - The number of requests that the queue has dispatched but has not received a reply for yet.
- effective
Execution NumberRate - The current maximum number of tasks per second executed by the queue. The maximum value of this variable is controlled by the RateLimits of the Queue. However, this value could be less to avoid overloading the endpoints tasks in the queue are targeting.
- executed
Last StringMinute Count - The number of tasks that the queue has dispatched and received a reply for during the last minute. This variable counts both successful and non-successful executions.
- oldest
Estimated StringArrival Time - An estimation of the nearest time in the future where a task in the queue is scheduled to be executed.
- tasks
Count String - An estimation of the number of tasks in the queue, that is, the tasks in the queue that haven't been executed, the tasks in the queue which the queue has dispatched but has not yet received a reply for, and the failed tasks that the queue is retrying.
RateLimitsResponse
- Max
Burst intSize - The max burst size. Max burst size limits how fast tasks in queue are processed when many tasks are in the queue and the rate is high. This field allows the queue to have a high rate so processing starts shortly after a task is enqueued, but still limits resource usage when many tasks are enqueued in a short period of time. The token bucket algorithm is used to control the rate of task dispatches. Each queue has a token bucket that holds tokens, up to the maximum specified by
max_burst_size
. Each time a task is dispatched, a token is removed from the bucket. Tasks will be dispatched until the queue's bucket runs out of tokens. The bucket will be continuously refilled with new tokens based on max_dispatches_per_second. The default value ofmax_burst_size
is picked by Cloud Tasks based on the value of max_dispatches_per_second. The maximum value ofmax_burst_size
is 500. For App Engine queues that were created or updated usingqueue.yaml/xml
,max_burst_size
is equal to bucket_size. If UpdateQueue is called on a queue without explicitly setting a value formax_burst_size
,max_burst_size
value will get updated if UpdateQueue is updating max_dispatches_per_second. - Max
Concurrent intTasks - The maximum number of concurrent tasks that Cloud Tasks allows to be dispatched for this queue. After this threshold has been reached, Cloud Tasks stops dispatching tasks until the number of concurrent requests decreases. If unspecified when the queue is created, Cloud Tasks will pick the default. The maximum allowed value is 5,000. This field is output only for pull queues and always -1, which indicates no limit. No other queue types can have
max_concurrent_tasks
set to -1. This field has the same meaning as max_concurrent_requests in queue.yaml/xml. - Max
Tasks doubleDispatched Per Second - The maximum rate at which tasks are dispatched from this queue. If unspecified when the queue is created, Cloud Tasks will pick the default. * For App Engine queues, the maximum allowed value is 500. * This field is output only for pull queues. In addition to the
max_tasks_dispatched_per_second
limit, a maximum of 10 QPS of LeaseTasks requests are allowed per pull queue. This field has the same meaning as rate in queue.yaml/xml.
- Max
Burst intSize - The max burst size. Max burst size limits how fast tasks in queue are processed when many tasks are in the queue and the rate is high. This field allows the queue to have a high rate so processing starts shortly after a task is enqueued, but still limits resource usage when many tasks are enqueued in a short period of time. The token bucket algorithm is used to control the rate of task dispatches. Each queue has a token bucket that holds tokens, up to the maximum specified by
max_burst_size
. Each time a task is dispatched, a token is removed from the bucket. Tasks will be dispatched until the queue's bucket runs out of tokens. The bucket will be continuously refilled with new tokens based on max_dispatches_per_second. The default value ofmax_burst_size
is picked by Cloud Tasks based on the value of max_dispatches_per_second. The maximum value ofmax_burst_size
is 500. For App Engine queues that were created or updated usingqueue.yaml/xml
,max_burst_size
is equal to bucket_size. If UpdateQueue is called on a queue without explicitly setting a value formax_burst_size
,max_burst_size
value will get updated if UpdateQueue is updating max_dispatches_per_second. - Max
Concurrent intTasks - The maximum number of concurrent tasks that Cloud Tasks allows to be dispatched for this queue. After this threshold has been reached, Cloud Tasks stops dispatching tasks until the number of concurrent requests decreases. If unspecified when the queue is created, Cloud Tasks will pick the default. The maximum allowed value is 5,000. This field is output only for pull queues and always -1, which indicates no limit. No other queue types can have
max_concurrent_tasks
set to -1. This field has the same meaning as max_concurrent_requests in queue.yaml/xml. - Max
Tasks float64Dispatched Per Second - The maximum rate at which tasks are dispatched from this queue. If unspecified when the queue is created, Cloud Tasks will pick the default. * For App Engine queues, the maximum allowed value is 500. * This field is output only for pull queues. In addition to the
max_tasks_dispatched_per_second
limit, a maximum of 10 QPS of LeaseTasks requests are allowed per pull queue. This field has the same meaning as rate in queue.yaml/xml.
- max
Burst IntegerSize - The max burst size. Max burst size limits how fast tasks in queue are processed when many tasks are in the queue and the rate is high. This field allows the queue to have a high rate so processing starts shortly after a task is enqueued, but still limits resource usage when many tasks are enqueued in a short period of time. The token bucket algorithm is used to control the rate of task dispatches. Each queue has a token bucket that holds tokens, up to the maximum specified by
max_burst_size
. Each time a task is dispatched, a token is removed from the bucket. Tasks will be dispatched until the queue's bucket runs out of tokens. The bucket will be continuously refilled with new tokens based on max_dispatches_per_second. The default value ofmax_burst_size
is picked by Cloud Tasks based on the value of max_dispatches_per_second. The maximum value ofmax_burst_size
is 500. For App Engine queues that were created or updated usingqueue.yaml/xml
,max_burst_size
is equal to bucket_size. If UpdateQueue is called on a queue without explicitly setting a value formax_burst_size
,max_burst_size
value will get updated if UpdateQueue is updating max_dispatches_per_second. - max
Concurrent IntegerTasks - The maximum number of concurrent tasks that Cloud Tasks allows to be dispatched for this queue. After this threshold has been reached, Cloud Tasks stops dispatching tasks until the number of concurrent requests decreases. If unspecified when the queue is created, Cloud Tasks will pick the default. The maximum allowed value is 5,000. This field is output only for pull queues and always -1, which indicates no limit. No other queue types can have
max_concurrent_tasks
set to -1. This field has the same meaning as max_concurrent_requests in queue.yaml/xml. - max
Tasks DoubleDispatched Per Second - The maximum rate at which tasks are dispatched from this queue. If unspecified when the queue is created, Cloud Tasks will pick the default. * For App Engine queues, the maximum allowed value is 500. * This field is output only for pull queues. In addition to the
max_tasks_dispatched_per_second
limit, a maximum of 10 QPS of LeaseTasks requests are allowed per pull queue. This field has the same meaning as rate in queue.yaml/xml.
- max
Burst numberSize - The max burst size. Max burst size limits how fast tasks in queue are processed when many tasks are in the queue and the rate is high. This field allows the queue to have a high rate so processing starts shortly after a task is enqueued, but still limits resource usage when many tasks are enqueued in a short period of time. The token bucket algorithm is used to control the rate of task dispatches. Each queue has a token bucket that holds tokens, up to the maximum specified by
max_burst_size
. Each time a task is dispatched, a token is removed from the bucket. Tasks will be dispatched until the queue's bucket runs out of tokens. The bucket will be continuously refilled with new tokens based on max_dispatches_per_second. The default value ofmax_burst_size
is picked by Cloud Tasks based on the value of max_dispatches_per_second. The maximum value ofmax_burst_size
is 500. For App Engine queues that were created or updated usingqueue.yaml/xml
,max_burst_size
is equal to bucket_size. If UpdateQueue is called on a queue without explicitly setting a value formax_burst_size
,max_burst_size
value will get updated if UpdateQueue is updating max_dispatches_per_second. - max
Concurrent numberTasks - The maximum number of concurrent tasks that Cloud Tasks allows to be dispatched for this queue. After this threshold has been reached, Cloud Tasks stops dispatching tasks until the number of concurrent requests decreases. If unspecified when the queue is created, Cloud Tasks will pick the default. The maximum allowed value is 5,000. This field is output only for pull queues and always -1, which indicates no limit. No other queue types can have
max_concurrent_tasks
set to -1. This field has the same meaning as max_concurrent_requests in queue.yaml/xml. - max
Tasks numberDispatched Per Second - The maximum rate at which tasks are dispatched from this queue. If unspecified when the queue is created, Cloud Tasks will pick the default. * For App Engine queues, the maximum allowed value is 500. * This field is output only for pull queues. In addition to the
max_tasks_dispatched_per_second
limit, a maximum of 10 QPS of LeaseTasks requests are allowed per pull queue. This field has the same meaning as rate in queue.yaml/xml.
- max_
burst_ intsize - The max burst size. Max burst size limits how fast tasks in queue are processed when many tasks are in the queue and the rate is high. This field allows the queue to have a high rate so processing starts shortly after a task is enqueued, but still limits resource usage when many tasks are enqueued in a short period of time. The token bucket algorithm is used to control the rate of task dispatches. Each queue has a token bucket that holds tokens, up to the maximum specified by
max_burst_size
. Each time a task is dispatched, a token is removed from the bucket. Tasks will be dispatched until the queue's bucket runs out of tokens. The bucket will be continuously refilled with new tokens based on max_dispatches_per_second. The default value ofmax_burst_size
is picked by Cloud Tasks based on the value of max_dispatches_per_second. The maximum value ofmax_burst_size
is 500. For App Engine queues that were created or updated usingqueue.yaml/xml
,max_burst_size
is equal to bucket_size. If UpdateQueue is called on a queue without explicitly setting a value formax_burst_size
,max_burst_size
value will get updated if UpdateQueue is updating max_dispatches_per_second. - max_
concurrent_ inttasks - The maximum number of concurrent tasks that Cloud Tasks allows to be dispatched for this queue. After this threshold has been reached, Cloud Tasks stops dispatching tasks until the number of concurrent requests decreases. If unspecified when the queue is created, Cloud Tasks will pick the default. The maximum allowed value is 5,000. This field is output only for pull queues and always -1, which indicates no limit. No other queue types can have
max_concurrent_tasks
set to -1. This field has the same meaning as max_concurrent_requests in queue.yaml/xml. - max_
tasks_ floatdispatched_ per_ second - The maximum rate at which tasks are dispatched from this queue. If unspecified when the queue is created, Cloud Tasks will pick the default. * For App Engine queues, the maximum allowed value is 500. * This field is output only for pull queues. In addition to the
max_tasks_dispatched_per_second
limit, a maximum of 10 QPS of LeaseTasks requests are allowed per pull queue. This field has the same meaning as rate in queue.yaml/xml.
- max
Burst NumberSize - The max burst size. Max burst size limits how fast tasks in queue are processed when many tasks are in the queue and the rate is high. This field allows the queue to have a high rate so processing starts shortly after a task is enqueued, but still limits resource usage when many tasks are enqueued in a short period of time. The token bucket algorithm is used to control the rate of task dispatches. Each queue has a token bucket that holds tokens, up to the maximum specified by
max_burst_size
. Each time a task is dispatched, a token is removed from the bucket. Tasks will be dispatched until the queue's bucket runs out of tokens. The bucket will be continuously refilled with new tokens based on max_dispatches_per_second. The default value ofmax_burst_size
is picked by Cloud Tasks based on the value of max_dispatches_per_second. The maximum value ofmax_burst_size
is 500. For App Engine queues that were created or updated usingqueue.yaml/xml
,max_burst_size
is equal to bucket_size. If UpdateQueue is called on a queue without explicitly setting a value formax_burst_size
,max_burst_size
value will get updated if UpdateQueue is updating max_dispatches_per_second. - max
Concurrent NumberTasks - The maximum number of concurrent tasks that Cloud Tasks allows to be dispatched for this queue. After this threshold has been reached, Cloud Tasks stops dispatching tasks until the number of concurrent requests decreases. If unspecified when the queue is created, Cloud Tasks will pick the default. The maximum allowed value is 5,000. This field is output only for pull queues and always -1, which indicates no limit. No other queue types can have
max_concurrent_tasks
set to -1. This field has the same meaning as max_concurrent_requests in queue.yaml/xml. - max
Tasks NumberDispatched Per Second - The maximum rate at which tasks are dispatched from this queue. If unspecified when the queue is created, Cloud Tasks will pick the default. * For App Engine queues, the maximum allowed value is 500. * This field is output only for pull queues. In addition to the
max_tasks_dispatched_per_second
limit, a maximum of 10 QPS of LeaseTasks requests are allowed per pull queue. This field has the same meaning as rate in queue.yaml/xml.
RetryConfigResponse
- Max
Attempts int - The maximum number of attempts for a task. Cloud Tasks will attempt the task
max_attempts
times (that is, if the first attempt fails, then there will bemax_attempts - 1
retries). Must be > 0. - Max
Backoff string - A task will be scheduled for retry between min_backoff and max_backoff duration after it fails, if the queue's RetryConfig specifies that the task should be retried. If unspecified when the queue is created, Cloud Tasks will pick the default. This field is output only for pull queues.
max_backoff
will be truncated to the nearest second. This field has the same meaning as max_backoff_seconds in queue.yaml/xml. - Max
Doublings int - The time between retries will double
max_doublings
times. A task's retry interval starts at min_backoff, then doublesmax_doublings
times, then increases linearly, and finally retries at intervals of max_backoff up to max_attempts times. For example, if min_backoff is 10s, max_backoff is 300s, andmax_doublings
is 3, then the a task will first be retried in 10s. The retry interval will double three times, and then increase linearly by 2^3 * 10s. Finally, the task will retry at intervals of max_backoff until the task has been attempted max_attempts times. Thus, the requests will retry at 10s, 20s, 40s, 80s, 160s, 240s, 300s, 300s, .... If unspecified when the queue is created, Cloud Tasks will pick the default. This field is output only for pull queues. This field has the same meaning as max_doublings in queue.yaml/xml. - Max
Retry stringDuration - If positive,
max_retry_duration
specifies the time limit for retrying a failed task, measured from when the task was first attempted. Oncemax_retry_duration
time has passed and the task has been attempted max_attempts times, no further attempts will be made and the task will be deleted. If zero, then the task age is unlimited. If unspecified when the queue is created, Cloud Tasks will pick the default. This field is output only for pull queues.max_retry_duration
will be truncated to the nearest second. This field has the same meaning as task_age_limit in queue.yaml/xml. - Min
Backoff string - A task will be scheduled for retry between min_backoff and max_backoff duration after it fails, if the queue's RetryConfig specifies that the task should be retried. If unspecified when the queue is created, Cloud Tasks will pick the default. This field is output only for pull queues.
min_backoff
will be truncated to the nearest second. This field has the same meaning as min_backoff_seconds in queue.yaml/xml. - Unlimited
Attempts bool - If true, then the number of attempts is unlimited.
- Max
Attempts int - The maximum number of attempts for a task. Cloud Tasks will attempt the task
max_attempts
times (that is, if the first attempt fails, then there will bemax_attempts - 1
retries). Must be > 0. - Max
Backoff string - A task will be scheduled for retry between min_backoff and max_backoff duration after it fails, if the queue's RetryConfig specifies that the task should be retried. If unspecified when the queue is created, Cloud Tasks will pick the default. This field is output only for pull queues.
max_backoff
will be truncated to the nearest second. This field has the same meaning as max_backoff_seconds in queue.yaml/xml. - Max
Doublings int - The time between retries will double
max_doublings
times. A task's retry interval starts at min_backoff, then doublesmax_doublings
times, then increases linearly, and finally retries at intervals of max_backoff up to max_attempts times. For example, if min_backoff is 10s, max_backoff is 300s, andmax_doublings
is 3, then the a task will first be retried in 10s. The retry interval will double three times, and then increase linearly by 2^3 * 10s. Finally, the task will retry at intervals of max_backoff until the task has been attempted max_attempts times. Thus, the requests will retry at 10s, 20s, 40s, 80s, 160s, 240s, 300s, 300s, .... If unspecified when the queue is created, Cloud Tasks will pick the default. This field is output only for pull queues. This field has the same meaning as max_doublings in queue.yaml/xml. - Max
Retry stringDuration - If positive,
max_retry_duration
specifies the time limit for retrying a failed task, measured from when the task was first attempted. Oncemax_retry_duration
time has passed and the task has been attempted max_attempts times, no further attempts will be made and the task will be deleted. If zero, then the task age is unlimited. If unspecified when the queue is created, Cloud Tasks will pick the default. This field is output only for pull queues.max_retry_duration
will be truncated to the nearest second. This field has the same meaning as task_age_limit in queue.yaml/xml. - Min
Backoff string - A task will be scheduled for retry between min_backoff and max_backoff duration after it fails, if the queue's RetryConfig specifies that the task should be retried. If unspecified when the queue is created, Cloud Tasks will pick the default. This field is output only for pull queues.
min_backoff
will be truncated to the nearest second. This field has the same meaning as min_backoff_seconds in queue.yaml/xml. - Unlimited
Attempts bool - If true, then the number of attempts is unlimited.
- max
Attempts Integer - The maximum number of attempts for a task. Cloud Tasks will attempt the task
max_attempts
times (that is, if the first attempt fails, then there will bemax_attempts - 1
retries). Must be > 0. - max
Backoff String - A task will be scheduled for retry between min_backoff and max_backoff duration after it fails, if the queue's RetryConfig specifies that the task should be retried. If unspecified when the queue is created, Cloud Tasks will pick the default. This field is output only for pull queues.
max_backoff
will be truncated to the nearest second. This field has the same meaning as max_backoff_seconds in queue.yaml/xml. - max
Doublings Integer - The time between retries will double
max_doublings
times. A task's retry interval starts at min_backoff, then doublesmax_doublings
times, then increases linearly, and finally retries at intervals of max_backoff up to max_attempts times. For example, if min_backoff is 10s, max_backoff is 300s, andmax_doublings
is 3, then the a task will first be retried in 10s. The retry interval will double three times, and then increase linearly by 2^3 * 10s. Finally, the task will retry at intervals of max_backoff until the task has been attempted max_attempts times. Thus, the requests will retry at 10s, 20s, 40s, 80s, 160s, 240s, 300s, 300s, .... If unspecified when the queue is created, Cloud Tasks will pick the default. This field is output only for pull queues. This field has the same meaning as max_doublings in queue.yaml/xml. - max
Retry StringDuration - If positive,
max_retry_duration
specifies the time limit for retrying a failed task, measured from when the task was first attempted. Oncemax_retry_duration
time has passed and the task has been attempted max_attempts times, no further attempts will be made and the task will be deleted. If zero, then the task age is unlimited. If unspecified when the queue is created, Cloud Tasks will pick the default. This field is output only for pull queues.max_retry_duration
will be truncated to the nearest second. This field has the same meaning as task_age_limit in queue.yaml/xml. - min
Backoff String - A task will be scheduled for retry between min_backoff and max_backoff duration after it fails, if the queue's RetryConfig specifies that the task should be retried. If unspecified when the queue is created, Cloud Tasks will pick the default. This field is output only for pull queues.
min_backoff
will be truncated to the nearest second. This field has the same meaning as min_backoff_seconds in queue.yaml/xml. - unlimited
Attempts Boolean - If true, then the number of attempts is unlimited.
- max
Attempts number - The maximum number of attempts for a task. Cloud Tasks will attempt the task
max_attempts
times (that is, if the first attempt fails, then there will bemax_attempts - 1
retries). Must be > 0. - max
Backoff string - A task will be scheduled for retry between min_backoff and max_backoff duration after it fails, if the queue's RetryConfig specifies that the task should be retried. If unspecified when the queue is created, Cloud Tasks will pick the default. This field is output only for pull queues.
max_backoff
will be truncated to the nearest second. This field has the same meaning as max_backoff_seconds in queue.yaml/xml. - max
Doublings number - The time between retries will double
max_doublings
times. A task's retry interval starts at min_backoff, then doublesmax_doublings
times, then increases linearly, and finally retries at intervals of max_backoff up to max_attempts times. For example, if min_backoff is 10s, max_backoff is 300s, andmax_doublings
is 3, then the a task will first be retried in 10s. The retry interval will double three times, and then increase linearly by 2^3 * 10s. Finally, the task will retry at intervals of max_backoff until the task has been attempted max_attempts times. Thus, the requests will retry at 10s, 20s, 40s, 80s, 160s, 240s, 300s, 300s, .... If unspecified when the queue is created, Cloud Tasks will pick the default. This field is output only for pull queues. This field has the same meaning as max_doublings in queue.yaml/xml. - max
Retry stringDuration - If positive,
max_retry_duration
specifies the time limit for retrying a failed task, measured from when the task was first attempted. Oncemax_retry_duration
time has passed and the task has been attempted max_attempts times, no further attempts will be made and the task will be deleted. If zero, then the task age is unlimited. If unspecified when the queue is created, Cloud Tasks will pick the default. This field is output only for pull queues.max_retry_duration
will be truncated to the nearest second. This field has the same meaning as task_age_limit in queue.yaml/xml. - min
Backoff string - A task will be scheduled for retry between min_backoff and max_backoff duration after it fails, if the queue's RetryConfig specifies that the task should be retried. If unspecified when the queue is created, Cloud Tasks will pick the default. This field is output only for pull queues.
min_backoff
will be truncated to the nearest second. This field has the same meaning as min_backoff_seconds in queue.yaml/xml. - unlimited
Attempts boolean - If true, then the number of attempts is unlimited.
- max_
attempts int - The maximum number of attempts for a task. Cloud Tasks will attempt the task
max_attempts
times (that is, if the first attempt fails, then there will bemax_attempts - 1
retries). Must be > 0. - max_
backoff str - A task will be scheduled for retry between min_backoff and max_backoff duration after it fails, if the queue's RetryConfig specifies that the task should be retried. If unspecified when the queue is created, Cloud Tasks will pick the default. This field is output only for pull queues.
max_backoff
will be truncated to the nearest second. This field has the same meaning as max_backoff_seconds in queue.yaml/xml. - max_
doublings int - The time between retries will double
max_doublings
times. A task's retry interval starts at min_backoff, then doublesmax_doublings
times, then increases linearly, and finally retries at intervals of max_backoff up to max_attempts times. For example, if min_backoff is 10s, max_backoff is 300s, andmax_doublings
is 3, then the a task will first be retried in 10s. The retry interval will double three times, and then increase linearly by 2^3 * 10s. Finally, the task will retry at intervals of max_backoff until the task has been attempted max_attempts times. Thus, the requests will retry at 10s, 20s, 40s, 80s, 160s, 240s, 300s, 300s, .... If unspecified when the queue is created, Cloud Tasks will pick the default. This field is output only for pull queues. This field has the same meaning as max_doublings in queue.yaml/xml. - max_
retry_ strduration - If positive,
max_retry_duration
specifies the time limit for retrying a failed task, measured from when the task was first attempted. Oncemax_retry_duration
time has passed and the task has been attempted max_attempts times, no further attempts will be made and the task will be deleted. If zero, then the task age is unlimited. If unspecified when the queue is created, Cloud Tasks will pick the default. This field is output only for pull queues.max_retry_duration
will be truncated to the nearest second. This field has the same meaning as task_age_limit in queue.yaml/xml. - min_
backoff str - A task will be scheduled for retry between min_backoff and max_backoff duration after it fails, if the queue's RetryConfig specifies that the task should be retried. If unspecified when the queue is created, Cloud Tasks will pick the default. This field is output only for pull queues.
min_backoff
will be truncated to the nearest second. This field has the same meaning as min_backoff_seconds in queue.yaml/xml. - unlimited_
attempts bool - If true, then the number of attempts is unlimited.
- max
Attempts Number - The maximum number of attempts for a task. Cloud Tasks will attempt the task
max_attempts
times (that is, if the first attempt fails, then there will bemax_attempts - 1
retries). Must be > 0. - max
Backoff String - A task will be scheduled for retry between min_backoff and max_backoff duration after it fails, if the queue's RetryConfig specifies that the task should be retried. If unspecified when the queue is created, Cloud Tasks will pick the default. This field is output only for pull queues.
max_backoff
will be truncated to the nearest second. This field has the same meaning as max_backoff_seconds in queue.yaml/xml. - max
Doublings Number - The time between retries will double
max_doublings
times. A task's retry interval starts at min_backoff, then doublesmax_doublings
times, then increases linearly, and finally retries at intervals of max_backoff up to max_attempts times. For example, if min_backoff is 10s, max_backoff is 300s, andmax_doublings
is 3, then the a task will first be retried in 10s. The retry interval will double three times, and then increase linearly by 2^3 * 10s. Finally, the task will retry at intervals of max_backoff until the task has been attempted max_attempts times. Thus, the requests will retry at 10s, 20s, 40s, 80s, 160s, 240s, 300s, 300s, .... If unspecified when the queue is created, Cloud Tasks will pick the default. This field is output only for pull queues. This field has the same meaning as max_doublings in queue.yaml/xml. - max
Retry StringDuration - If positive,
max_retry_duration
specifies the time limit for retrying a failed task, measured from when the task was first attempted. Oncemax_retry_duration
time has passed and the task has been attempted max_attempts times, no further attempts will be made and the task will be deleted. If zero, then the task age is unlimited. If unspecified when the queue is created, Cloud Tasks will pick the default. This field is output only for pull queues.max_retry_duration
will be truncated to the nearest second. This field has the same meaning as task_age_limit in queue.yaml/xml. - min
Backoff String - A task will be scheduled for retry between min_backoff and max_backoff duration after it fails, if the queue's RetryConfig specifies that the task should be retried. If unspecified when the queue is created, Cloud Tasks will pick the default. This field is output only for pull queues.
min_backoff
will be truncated to the nearest second. This field has the same meaning as min_backoff_seconds in queue.yaml/xml. - unlimited
Attempts Boolean - If true, then the number of attempts is unlimited.
UriOverrideResponse
- Host string
- Host override. When specified, replaces the host part of the task URL. For example, if the task URL is "https://www.google.com," and host value is set to "example.net", the overridden URI will be changed to "https://example.net." Host value cannot be an empty string (INVALID_ARGUMENT).
- Path
Override Pulumi.Google Native. Cloud Tasks. V2Beta2. Inputs. Path Override Response - URI path. When specified, replaces the existing path of the task URL. Setting the path value to an empty string clears the URI path segment.
- Port string
- Port override. When specified, replaces the port part of the task URI. For instance, for a URI http://www.google.com/foo and port=123, the overridden URI becomes http://www.google.com:123/foo. Note that the port value must be a positive integer. Setting the port to 0 (Zero) clears the URI port.
- Query
Override Pulumi.Google Native. Cloud Tasks. V2Beta2. Inputs. Query Override Response - URI Query. When specified, replaces the query part of the task URI. Setting the query value to an empty string clears the URI query segment.
- Scheme string
- Scheme override. When specified, the task URI scheme is replaced by the provided value (HTTP or HTTPS).
- Uri
Override stringEnforce Mode - URI Override Enforce Mode When specified, determines the Target UriOverride mode. If not specified, it defaults to ALWAYS.
- Host string
- Host override. When specified, replaces the host part of the task URL. For example, if the task URL is "https://www.google.com," and host value is set to "example.net", the overridden URI will be changed to "https://example.net." Host value cannot be an empty string (INVALID_ARGUMENT).
- Path
Override PathOverride Response - URI path. When specified, replaces the existing path of the task URL. Setting the path value to an empty string clears the URI path segment.
- Port string
- Port override. When specified, replaces the port part of the task URI. For instance, for a URI http://www.google.com/foo and port=123, the overridden URI becomes http://www.google.com:123/foo. Note that the port value must be a positive integer. Setting the port to 0 (Zero) clears the URI port.
- Query
Override QueryOverride Response - URI Query. When specified, replaces the query part of the task URI. Setting the query value to an empty string clears the URI query segment.
- Scheme string
- Scheme override. When specified, the task URI scheme is replaced by the provided value (HTTP or HTTPS).
- Uri
Override stringEnforce Mode - URI Override Enforce Mode When specified, determines the Target UriOverride mode. If not specified, it defaults to ALWAYS.
- host String
- Host override. When specified, replaces the host part of the task URL. For example, if the task URL is "https://www.google.com," and host value is set to "example.net", the overridden URI will be changed to "https://example.net." Host value cannot be an empty string (INVALID_ARGUMENT).
- path
Override PathOverride Response - URI path. When specified, replaces the existing path of the task URL. Setting the path value to an empty string clears the URI path segment.
- port String
- Port override. When specified, replaces the port part of the task URI. For instance, for a URI http://www.google.com/foo and port=123, the overridden URI becomes http://www.google.com:123/foo. Note that the port value must be a positive integer. Setting the port to 0 (Zero) clears the URI port.
- query
Override QueryOverride Response - URI Query. When specified, replaces the query part of the task URI. Setting the query value to an empty string clears the URI query segment.
- scheme String
- Scheme override. When specified, the task URI scheme is replaced by the provided value (HTTP or HTTPS).
- uri
Override StringEnforce Mode - URI Override Enforce Mode When specified, determines the Target UriOverride mode. If not specified, it defaults to ALWAYS.
- host string
- Host override. When specified, replaces the host part of the task URL. For example, if the task URL is "https://www.google.com," and host value is set to "example.net", the overridden URI will be changed to "https://example.net." Host value cannot be an empty string (INVALID_ARGUMENT).
- path
Override PathOverride Response - URI path. When specified, replaces the existing path of the task URL. Setting the path value to an empty string clears the URI path segment.
- port string
- Port override. When specified, replaces the port part of the task URI. For instance, for a URI http://www.google.com/foo and port=123, the overridden URI becomes http://www.google.com:123/foo. Note that the port value must be a positive integer. Setting the port to 0 (Zero) clears the URI port.
- query
Override QueryOverride Response - URI Query. When specified, replaces the query part of the task URI. Setting the query value to an empty string clears the URI query segment.
- scheme string
- Scheme override. When specified, the task URI scheme is replaced by the provided value (HTTP or HTTPS).
- uri
Override stringEnforce Mode - URI Override Enforce Mode When specified, determines the Target UriOverride mode. If not specified, it defaults to ALWAYS.
- host str
- Host override. When specified, replaces the host part of the task URL. For example, if the task URL is "https://www.google.com," and host value is set to "example.net", the overridden URI will be changed to "https://example.net." Host value cannot be an empty string (INVALID_ARGUMENT).
- path_
override PathOverride Response - URI path. When specified, replaces the existing path of the task URL. Setting the path value to an empty string clears the URI path segment.
- port str
- Port override. When specified, replaces the port part of the task URI. For instance, for a URI http://www.google.com/foo and port=123, the overridden URI becomes http://www.google.com:123/foo. Note that the port value must be a positive integer. Setting the port to 0 (Zero) clears the URI port.
- query_
override QueryOverride Response - URI Query. When specified, replaces the query part of the task URI. Setting the query value to an empty string clears the URI query segment.
- scheme str
- Scheme override. When specified, the task URI scheme is replaced by the provided value (HTTP or HTTPS).
- uri_
override_ strenforce_ mode - URI Override Enforce Mode When specified, determines the Target UriOverride mode. If not specified, it defaults to ALWAYS.
- host String
- Host override. When specified, replaces the host part of the task URL. For example, if the task URL is "https://www.google.com," and host value is set to "example.net", the overridden URI will be changed to "https://example.net." Host value cannot be an empty string (INVALID_ARGUMENT).
- path
Override Property Map - URI path. When specified, replaces the existing path of the task URL. Setting the path value to an empty string clears the URI path segment.
- port String
- Port override. When specified, replaces the port part of the task URI. For instance, for a URI http://www.google.com/foo and port=123, the overridden URI becomes http://www.google.com:123/foo. Note that the port value must be a positive integer. Setting the port to 0 (Zero) clears the URI port.
- query
Override Property Map - URI Query. When specified, replaces the query part of the task URI. Setting the query value to an empty string clears the URI query segment.
- scheme String
- Scheme override. When specified, the task URI scheme is replaced by the provided value (HTTP or HTTPS).
- uri
Override StringEnforce Mode - URI Override Enforce Mode When specified, determines the Target UriOverride mode. If not specified, it defaults to ALWAYS.
Package Details
- Repository
- Google Cloud Native pulumi/pulumi-google-native
- License
- Apache-2.0
Google Cloud Native is in preview. Google Cloud Classic is fully supported.
Google Cloud Native v0.32.0 published on Wednesday, Nov 29, 2023 by Pulumi