Google Cloud Native is in preview. Google Cloud Classic is fully supported.
google-native.cloudtasks/v2.Queue
Explore with Pulumi AI
Google Cloud Native is in preview. Google Cloud Classic is fully supported.
Creates a queue. Queues created with this method allow tasks to live for a maximum of 31 days. After a task is 31 days old, the task will be deleted regardless of whether it was dispatched or not. WARNING: Using this method may have unintended side effects if you are using an App Engine queue.yaml or queue.xml file to manage your queues. Read Overview of Queue Management and queue.yaml before using this method.
Create Queue Resource
Resources are created with functions called constructors. To learn more about declaring and configuring resources, see Resources.
Constructor syntax
new Queue(name: string, args?: QueueArgs, opts?: CustomResourceOptions);@overload
def Queue(resource_name: str,
          args: Optional[QueueArgs] = None,
          opts: Optional[ResourceOptions] = None)
@overload
def Queue(resource_name: str,
          opts: Optional[ResourceOptions] = None,
          app_engine_routing_override: Optional[AppEngineRoutingArgs] = None,
          http_target: Optional[HttpTargetArgs] = None,
          location: Optional[str] = None,
          name: Optional[str] = None,
          project: Optional[str] = None,
          rate_limits: Optional[RateLimitsArgs] = None,
          retry_config: Optional[RetryConfigArgs] = None,
          stackdriver_logging_config: Optional[StackdriverLoggingConfigArgs] = None)func NewQueue(ctx *Context, name string, args *QueueArgs, opts ...ResourceOption) (*Queue, error)public Queue(string name, QueueArgs? args = null, CustomResourceOptions? opts = null)type: google-native:cloudtasks/v2:Queue
properties: # The arguments to resource properties.
options: # Bag of options to control resource's behavior.
Parameters
- name string
- The unique name of the resource.
- args QueueArgs
- The arguments to resource properties.
- opts CustomResourceOptions
- Bag of options to control resource's behavior.
- resource_name str
- The unique name of the resource.
- args QueueArgs
- The arguments to resource properties.
- opts ResourceOptions
- Bag of options to control resource's behavior.
- ctx Context
- Context object for the current deployment.
- name string
- The unique name of the resource.
- args QueueArgs
- The arguments to resource properties.
- opts ResourceOption
- Bag of options to control resource's behavior.
- name string
- The unique name of the resource.
- args QueueArgs
- The arguments to resource properties.
- opts CustomResourceOptions
- Bag of options to control resource's behavior.
- name String
- The unique name of the resource.
- args QueueArgs
- The arguments to resource properties.
- options CustomResourceOptions
- Bag of options to control resource's behavior.
Constructor example
The following reference example uses placeholder values for all input properties.
var queueResource = new GoogleNative.CloudTasks.V2.Queue("queueResource", new()
{
    AppEngineRoutingOverride = new GoogleNative.CloudTasks.V2.Inputs.AppEngineRoutingArgs
    {
        Instance = "string",
        Service = "string",
        Version = "string",
    },
    HttpTarget = new GoogleNative.CloudTasks.V2.Inputs.HttpTargetArgs
    {
        HeaderOverrides = new[]
        {
            new GoogleNative.CloudTasks.V2.Inputs.HeaderOverrideArgs
            {
                Header = new GoogleNative.CloudTasks.V2.Inputs.HeaderArgs
                {
                    Key = "string",
                    Value = "string",
                },
            },
        },
        HttpMethod = GoogleNative.CloudTasks.V2.HttpTargetHttpMethod.HttpMethodUnspecified,
        OauthToken = new GoogleNative.CloudTasks.V2.Inputs.OAuthTokenArgs
        {
            Scope = "string",
            ServiceAccountEmail = "string",
        },
        OidcToken = new GoogleNative.CloudTasks.V2.Inputs.OidcTokenArgs
        {
            Audience = "string",
            ServiceAccountEmail = "string",
        },
        UriOverride = new GoogleNative.CloudTasks.V2.Inputs.UriOverrideArgs
        {
            Host = "string",
            PathOverride = new GoogleNative.CloudTasks.V2.Inputs.PathOverrideArgs
            {
                Path = "string",
            },
            Port = "string",
            QueryOverride = new GoogleNative.CloudTasks.V2.Inputs.QueryOverrideArgs
            {
                QueryParams = "string",
            },
            Scheme = GoogleNative.CloudTasks.V2.UriOverrideScheme.SchemeUnspecified,
            UriOverrideEnforceMode = GoogleNative.CloudTasks.V2.UriOverrideUriOverrideEnforceMode.UriOverrideEnforceModeUnspecified,
        },
    },
    Location = "string",
    Name = "string",
    Project = "string",
    RateLimits = new GoogleNative.CloudTasks.V2.Inputs.RateLimitsArgs
    {
        MaxConcurrentDispatches = 0,
        MaxDispatchesPerSecond = 0,
    },
    RetryConfig = new GoogleNative.CloudTasks.V2.Inputs.RetryConfigArgs
    {
        MaxAttempts = 0,
        MaxBackoff = "string",
        MaxDoublings = 0,
        MaxRetryDuration = "string",
        MinBackoff = "string",
    },
    StackdriverLoggingConfig = new GoogleNative.CloudTasks.V2.Inputs.StackdriverLoggingConfigArgs
    {
        SamplingRatio = 0,
    },
});
example, err := cloudtasks.NewQueue(ctx, "queueResource", &cloudtasks.QueueArgs{
	AppEngineRoutingOverride: &cloudtasks.AppEngineRoutingArgs{
		Instance: pulumi.String("string"),
		Service:  pulumi.String("string"),
		Version:  pulumi.String("string"),
	},
	HttpTarget: &cloudtasks.HttpTargetArgs{
		HeaderOverrides: cloudtasks.HeaderOverrideArray{
			&cloudtasks.HeaderOverrideArgs{
				Header: &cloudtasks.HeaderArgs{
					Key:   pulumi.String("string"),
					Value: pulumi.String("string"),
				},
			},
		},
		HttpMethod: cloudtasks.HttpTargetHttpMethodHttpMethodUnspecified,
		OauthToken: &cloudtasks.OAuthTokenArgs{
			Scope:               pulumi.String("string"),
			ServiceAccountEmail: pulumi.String("string"),
		},
		OidcToken: &cloudtasks.OidcTokenArgs{
			Audience:            pulumi.String("string"),
			ServiceAccountEmail: pulumi.String("string"),
		},
		UriOverride: &cloudtasks.UriOverrideArgs{
			Host: pulumi.String("string"),
			PathOverride: &cloudtasks.PathOverrideArgs{
				Path: pulumi.String("string"),
			},
			Port: pulumi.String("string"),
			QueryOverride: &cloudtasks.QueryOverrideArgs{
				QueryParams: pulumi.String("string"),
			},
			Scheme:                 cloudtasks.UriOverrideSchemeSchemeUnspecified,
			UriOverrideEnforceMode: cloudtasks.UriOverrideUriOverrideEnforceModeUriOverrideEnforceModeUnspecified,
		},
	},
	Location: pulumi.String("string"),
	Name:     pulumi.String("string"),
	Project:  pulumi.String("string"),
	RateLimits: &cloudtasks.RateLimitsArgs{
		MaxConcurrentDispatches: pulumi.Int(0),
		MaxDispatchesPerSecond:  pulumi.Float64(0),
	},
	RetryConfig: &cloudtasks.RetryConfigArgs{
		MaxAttempts:      pulumi.Int(0),
		MaxBackoff:       pulumi.String("string"),
		MaxDoublings:     pulumi.Int(0),
		MaxRetryDuration: pulumi.String("string"),
		MinBackoff:       pulumi.String("string"),
	},
	StackdriverLoggingConfig: &cloudtasks.StackdriverLoggingConfigArgs{
		SamplingRatio: pulumi.Float64(0),
	},
})
var queueResource = new Queue("queueResource", QueueArgs.builder()
    .appEngineRoutingOverride(AppEngineRoutingArgs.builder()
        .instance("string")
        .service("string")
        .version("string")
        .build())
    .httpTarget(HttpTargetArgs.builder()
        .headerOverrides(HeaderOverrideArgs.builder()
            .header(HeaderArgs.builder()
                .key("string")
                .value("string")
                .build())
            .build())
        .httpMethod("HTTP_METHOD_UNSPECIFIED")
        .oauthToken(OAuthTokenArgs.builder()
            .scope("string")
            .serviceAccountEmail("string")
            .build())
        .oidcToken(OidcTokenArgs.builder()
            .audience("string")
            .serviceAccountEmail("string")
            .build())
        .uriOverride(UriOverrideArgs.builder()
            .host("string")
            .pathOverride(PathOverrideArgs.builder()
                .path("string")
                .build())
            .port("string")
            .queryOverride(QueryOverrideArgs.builder()
                .queryParams("string")
                .build())
            .scheme("SCHEME_UNSPECIFIED")
            .uriOverrideEnforceMode("URI_OVERRIDE_ENFORCE_MODE_UNSPECIFIED")
            .build())
        .build())
    .location("string")
    .name("string")
    .project("string")
    .rateLimits(RateLimitsArgs.builder()
        .maxConcurrentDispatches(0)
        .maxDispatchesPerSecond(0)
        .build())
    .retryConfig(RetryConfigArgs.builder()
        .maxAttempts(0)
        .maxBackoff("string")
        .maxDoublings(0)
        .maxRetryDuration("string")
        .minBackoff("string")
        .build())
    .stackdriverLoggingConfig(StackdriverLoggingConfigArgs.builder()
        .samplingRatio(0)
        .build())
    .build());
queue_resource = google_native.cloudtasks.v2.Queue("queueResource",
    app_engine_routing_override={
        "instance": "string",
        "service": "string",
        "version": "string",
    },
    http_target={
        "header_overrides": [{
            "header": {
                "key": "string",
                "value": "string",
            },
        }],
        "http_method": google_native.cloudtasks.v2.HttpTargetHttpMethod.HTTP_METHOD_UNSPECIFIED,
        "oauth_token": {
            "scope": "string",
            "service_account_email": "string",
        },
        "oidc_token": {
            "audience": "string",
            "service_account_email": "string",
        },
        "uri_override": {
            "host": "string",
            "path_override": {
                "path": "string",
            },
            "port": "string",
            "query_override": {
                "query_params": "string",
            },
            "scheme": google_native.cloudtasks.v2.UriOverrideScheme.SCHEME_UNSPECIFIED,
            "uri_override_enforce_mode": google_native.cloudtasks.v2.UriOverrideUriOverrideEnforceMode.URI_OVERRIDE_ENFORCE_MODE_UNSPECIFIED,
        },
    },
    location="string",
    name="string",
    project="string",
    rate_limits={
        "max_concurrent_dispatches": 0,
        "max_dispatches_per_second": 0,
    },
    retry_config={
        "max_attempts": 0,
        "max_backoff": "string",
        "max_doublings": 0,
        "max_retry_duration": "string",
        "min_backoff": "string",
    },
    stackdriver_logging_config={
        "sampling_ratio": 0,
    })
const queueResource = new google_native.cloudtasks.v2.Queue("queueResource", {
    appEngineRoutingOverride: {
        instance: "string",
        service: "string",
        version: "string",
    },
    httpTarget: {
        headerOverrides: [{
            header: {
                key: "string",
                value: "string",
            },
        }],
        httpMethod: google_native.cloudtasks.v2.HttpTargetHttpMethod.HttpMethodUnspecified,
        oauthToken: {
            scope: "string",
            serviceAccountEmail: "string",
        },
        oidcToken: {
            audience: "string",
            serviceAccountEmail: "string",
        },
        uriOverride: {
            host: "string",
            pathOverride: {
                path: "string",
            },
            port: "string",
            queryOverride: {
                queryParams: "string",
            },
            scheme: google_native.cloudtasks.v2.UriOverrideScheme.SchemeUnspecified,
            uriOverrideEnforceMode: google_native.cloudtasks.v2.UriOverrideUriOverrideEnforceMode.UriOverrideEnforceModeUnspecified,
        },
    },
    location: "string",
    name: "string",
    project: "string",
    rateLimits: {
        maxConcurrentDispatches: 0,
        maxDispatchesPerSecond: 0,
    },
    retryConfig: {
        maxAttempts: 0,
        maxBackoff: "string",
        maxDoublings: 0,
        maxRetryDuration: "string",
        minBackoff: "string",
    },
    stackdriverLoggingConfig: {
        samplingRatio: 0,
    },
});
type: google-native:cloudtasks/v2:Queue
properties:
    appEngineRoutingOverride:
        instance: string
        service: string
        version: string
    httpTarget:
        headerOverrides:
            - header:
                key: string
                value: string
        httpMethod: HTTP_METHOD_UNSPECIFIED
        oauthToken:
            scope: string
            serviceAccountEmail: string
        oidcToken:
            audience: string
            serviceAccountEmail: string
        uriOverride:
            host: string
            pathOverride:
                path: string
            port: string
            queryOverride:
                queryParams: string
            scheme: SCHEME_UNSPECIFIED
            uriOverrideEnforceMode: URI_OVERRIDE_ENFORCE_MODE_UNSPECIFIED
    location: string
    name: string
    project: string
    rateLimits:
        maxConcurrentDispatches: 0
        maxDispatchesPerSecond: 0
    retryConfig:
        maxAttempts: 0
        maxBackoff: string
        maxDoublings: 0
        maxRetryDuration: string
        minBackoff: string
    stackdriverLoggingConfig:
        samplingRatio: 0
Queue Resource Properties
To learn more about resource properties and how to use them, see Inputs and Outputs in the Architecture and Concepts docs.
Inputs
In Python, inputs that are objects can be passed either as argument classes or as dictionary literals.
The Queue resource accepts the following input properties:
- AppEngine Pulumi.Routing Override Google Native. Cloud Tasks. V2. Inputs. App Engine Routing 
- Overrides for task-level app_engine_routing. These settings apply only to App Engine tasks in this queue. Http tasks are not affected. If set, app_engine_routing_overrideis used for all App Engine tasks in the queue, no matter what the setting is for the task-level app_engine_routing.
- HttpTarget Pulumi.Google Native. Cloud Tasks. V2. Inputs. Http Target 
- Modifies HTTP target for HTTP tasks.
- Location string
- 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_IDcan contain letters ([A-Za-z]), numbers ([0-9]), hyphens (-), colons (:), or periods (.). For more information, see Identifying projects *LOCATION_IDis 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_IDcan contain letters ([A-Za-z]), numbers ([0-9]), or hyphens (-). The maximum length is 100 characters.
- Project string
- RateLimits Pulumi.Google Native. Cloud Tasks. V2. Inputs. Rate Limits 
- Rate limits for task dispatches. rate_limits and retry_config are related because they both control task attempts. However they control task attempts 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). The queue's actual dispatch rate is the result of: * Number of tasks in the queue * User-specified throttling: rate_limits, retry_config, and the queue's state. * System throttling due to 429(Too Many Requests) or503(Service Unavailable) responses from the worker, high error rates, or to smooth sudden large traffic spikes.
- RetryConfig Pulumi.Google Native. Cloud Tasks. V2. Inputs. Retry Config 
- 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.
- StackdriverLogging Pulumi.Config Google Native. Cloud Tasks. V2. Inputs. Stackdriver Logging Config 
- Configuration options for writing logs to Stackdriver Logging. If this field is unset, then no logs are written.
- AppEngine AppRouting Override Engine Routing Args 
- Overrides for task-level app_engine_routing. These settings apply only to App Engine tasks in this queue. Http tasks are not affected. If set, app_engine_routing_overrideis used for all App Engine tasks in the queue, no matter what the setting is for the task-level app_engine_routing.
- HttpTarget HttpTarget Args 
- Modifies HTTP target for HTTP tasks.
- Location string
- 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_IDcan contain letters ([A-Za-z]), numbers ([0-9]), hyphens (-), colons (:), or periods (.). For more information, see Identifying projects *LOCATION_IDis 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_IDcan contain letters ([A-Za-z]), numbers ([0-9]), or hyphens (-). The maximum length is 100 characters.
- Project string
- RateLimits RateLimits Args 
- Rate limits for task dispatches. rate_limits and retry_config are related because they both control task attempts. However they control task attempts 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). The queue's actual dispatch rate is the result of: * Number of tasks in the queue * User-specified throttling: rate_limits, retry_config, and the queue's state. * System throttling due to 429(Too Many Requests) or503(Service Unavailable) responses from the worker, high error rates, or to smooth sudden large traffic spikes.
- RetryConfig RetryConfig Args 
- 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.
- StackdriverLogging StackdriverConfig Logging Config Args 
- Configuration options for writing logs to Stackdriver Logging. If this field is unset, then no logs are written.
- appEngine AppRouting Override Engine Routing 
- Overrides for task-level app_engine_routing. These settings apply only to App Engine tasks in this queue. Http tasks are not affected. If set, app_engine_routing_overrideis used for all App Engine tasks in the queue, no matter what the setting is for the task-level app_engine_routing.
- httpTarget HttpTarget 
- Modifies HTTP target for HTTP tasks.
- location String
- 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_IDcan contain letters ([A-Za-z]), numbers ([0-9]), hyphens (-), colons (:), or periods (.). For more information, see Identifying projects *LOCATION_IDis 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_IDcan contain letters ([A-Za-z]), numbers ([0-9]), or hyphens (-). The maximum length is 100 characters.
- project String
- rateLimits RateLimits 
- Rate limits for task dispatches. rate_limits and retry_config are related because they both control task attempts. However they control task attempts 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). The queue's actual dispatch rate is the result of: * Number of tasks in the queue * User-specified throttling: rate_limits, retry_config, and the queue's state. * System throttling due to 429(Too Many Requests) or503(Service Unavailable) responses from the worker, high error rates, or to smooth sudden large traffic spikes.
- retryConfig RetryConfig 
- 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.
- stackdriverLogging StackdriverConfig Logging Config 
- Configuration options for writing logs to Stackdriver Logging. If this field is unset, then no logs are written.
- appEngine AppRouting Override Engine Routing 
- Overrides for task-level app_engine_routing. These settings apply only to App Engine tasks in this queue. Http tasks are not affected. If set, app_engine_routing_overrideis used for all App Engine tasks in the queue, no matter what the setting is for the task-level app_engine_routing.
- httpTarget HttpTarget 
- Modifies HTTP target for HTTP tasks.
- location string
- 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_IDcan contain letters ([A-Za-z]), numbers ([0-9]), hyphens (-), colons (:), or periods (.). For more information, see Identifying projects *LOCATION_IDis 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_IDcan contain letters ([A-Za-z]), numbers ([0-9]), or hyphens (-). The maximum length is 100 characters.
- project string
- rateLimits RateLimits 
- Rate limits for task dispatches. rate_limits and retry_config are related because they both control task attempts. However they control task attempts 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). The queue's actual dispatch rate is the result of: * Number of tasks in the queue * User-specified throttling: rate_limits, retry_config, and the queue's state. * System throttling due to 429(Too Many Requests) or503(Service Unavailable) responses from the worker, high error rates, or to smooth sudden large traffic spikes.
- retryConfig RetryConfig 
- 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.
- stackdriverLogging StackdriverConfig Logging Config 
- Configuration options for writing logs to Stackdriver Logging. If this field is unset, then no logs are written.
- app_engine_ Approuting_ override Engine Routing Args 
- Overrides for task-level app_engine_routing. These settings apply only to App Engine tasks in this queue. Http tasks are not affected. If set, app_engine_routing_overrideis used for all App Engine tasks in the queue, no matter what the setting is for the task-level app_engine_routing.
- http_target HttpTarget Args 
- Modifies HTTP target for HTTP tasks.
- location str
- 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_IDcan contain letters ([A-Za-z]), numbers ([0-9]), hyphens (-), colons (:), or periods (.). For more information, see Identifying projects *LOCATION_IDis 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_IDcan contain letters ([A-Za-z]), numbers ([0-9]), or hyphens (-). The maximum length is 100 characters.
- project str
- rate_limits RateLimits Args 
- Rate limits for task dispatches. rate_limits and retry_config are related because they both control task attempts. However they control task attempts 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). The queue's actual dispatch rate is the result of: * Number of tasks in the queue * User-specified throttling: rate_limits, retry_config, and the queue's state. * System throttling due to 429(Too Many Requests) or503(Service Unavailable) responses from the worker, high error rates, or to smooth sudden large traffic spikes.
- retry_config RetryConfig Args 
- 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.
- stackdriver_logging_ Stackdriverconfig Logging Config Args 
- Configuration options for writing logs to Stackdriver Logging. If this field is unset, then no logs are written.
- appEngine Property MapRouting Override 
- Overrides for task-level app_engine_routing. These settings apply only to App Engine tasks in this queue. Http tasks are not affected. If set, app_engine_routing_overrideis used for all App Engine tasks in the queue, no matter what the setting is for the task-level app_engine_routing.
- httpTarget Property Map
- Modifies HTTP target for HTTP tasks.
- location String
- 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_IDcan contain letters ([A-Za-z]), numbers ([0-9]), hyphens (-), colons (:), or periods (.). For more information, see Identifying projects *LOCATION_IDis 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_IDcan contain letters ([A-Za-z]), numbers ([0-9]), or hyphens (-). The maximum length is 100 characters.
- project String
- rateLimits Property Map
- Rate limits for task dispatches. rate_limits and retry_config are related because they both control task attempts. However they control task attempts 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). The queue's actual dispatch rate is the result of: * Number of tasks in the queue * User-specified throttling: rate_limits, retry_config, and the queue's state. * System throttling due to 429(Too Many Requests) or503(Service Unavailable) responses from the worker, high error rates, or to smooth sudden large traffic spikes.
- retryConfig 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.
- stackdriverLogging Property MapConfig 
- Configuration options for writing logs to Stackdriver Logging. If this field is unset, then no logs are written.
Outputs
All input properties are implicitly available as output properties. Additionally, the Queue resource produces the following output properties:
- Id string
- The provider-assigned unique ID for this managed resource.
- PurgeTime 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.
- State string
- The state of the queue. statecan only be changed by calling PauseQueue, ResumeQueue, or uploading queue.yaml/xml. UpdateQueue cannot be used to changestate.
- Id string
- The provider-assigned unique ID for this managed resource.
- PurgeTime 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.
- State string
- The state of the queue. statecan only be changed by calling PauseQueue, ResumeQueue, or uploading queue.yaml/xml. UpdateQueue cannot be used to changestate.
- id String
- The provider-assigned unique ID for this managed resource.
- purgeTime 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.
- state String
- The state of the queue. statecan only be changed by calling PauseQueue, ResumeQueue, or uploading queue.yaml/xml. UpdateQueue cannot be used to changestate.
- id string
- The provider-assigned unique ID for this managed resource.
- purgeTime 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.
- state string
- The state of the queue. statecan only be changed by calling PauseQueue, ResumeQueue, or uploading queue.yaml/xml. UpdateQueue cannot be used to changestate.
- id str
- The provider-assigned unique ID for this managed resource.
- 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.
- state str
- The state of the queue. statecan only be changed by calling PauseQueue, ResumeQueue, or uploading queue.yaml/xml. UpdateQueue cannot be used to changestate.
- id String
- The provider-assigned unique ID for this managed resource.
- purgeTime 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.
- state String
- The state of the queue. statecan only be changed by calling PauseQueue, ResumeQueue, or uploading queue.yaml/xml. UpdateQueue cannot be used to changestate.
Supporting Types
AppEngineRouting, AppEngineRoutingArgs      
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
AppEngineRoutingResponse, AppEngineRoutingResponseArgs        
- Host string
- The host that the task is sent to. The host is constructed from the domain name of the app associated with the queue's project ID (for example .appspot.com), and the service, version, and instance. Tasks which were created using the App Engine SDK might have a custom domain name. For more information, see How Requests are Routed.
- 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. The host is constructed from the domain name of the app associated with the queue's project ID (for example .appspot.com), and the service, version, and instance. Tasks which were created using the App Engine SDK might have a custom domain name. For more information, see How Requests are Routed.
- 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. The host is constructed from the domain name of the app associated with the queue's project ID (for example .appspot.com), and the service, version, and instance. Tasks which were created using the App Engine SDK might have a custom domain name. For more information, see How Requests are Routed.
- 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. The host is constructed from the domain name of the app associated with the queue's project ID (for example .appspot.com), and the service, version, and instance. Tasks which were created using the App Engine SDK might have a custom domain name. For more information, see How Requests are Routed.
- 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. The host is constructed from the domain name of the app associated with the queue's project ID (for example .appspot.com), and the service, version, and instance. Tasks which were created using the App Engine SDK might have a custom domain name. For more information, see How Requests are Routed.
- 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. The host is constructed from the domain name of the app associated with the queue's project ID (for example .appspot.com), and the service, version, and instance. Tasks which were created using the App Engine SDK might have a custom domain name. For more information, see How Requests are Routed.
- 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.
Header, HeaderArgs  
HeaderOverride, HeaderOverrideArgs    
- Header
Pulumi.Google Native. Cloud Tasks. V2. Inputs. Header 
- header embodying a key and a value.
- header Property Map
- header embodying a key and a value.
HeaderOverrideResponse, HeaderOverrideResponseArgs      
- Header
Pulumi.Google Native. Cloud Tasks. V2. Inputs. Header Response 
- header embodying a key and a value.
- Header
HeaderResponse 
- header embodying a key and a value.
- header
HeaderResponse 
- header embodying a key and a value.
- header
HeaderResponse 
- header embodying a key and a value.
- header
HeaderResponse 
- header embodying a key and a value.
- header Property Map
- header embodying a key and a value.
HeaderResponse, HeaderResponseArgs    
HttpTarget, HttpTargetArgs    
- HeaderOverrides List<Pulumi.Google Native. Cloud Tasks. V2. Inputs. Header Override> 
- HTTP target headers. This map contains the header field names and values. Headers will be set when running the CreateTask and/or BufferTask. These headers represent a subset of the headers that will be configured for 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: * Several predefined headers, prefixed with "X-CloudTasks-", can be used to define properties of the task. * Host: This will be computed by Cloud Tasks and derived from HttpRequest.url. * Content-Length: This will be computed by Cloud Tasks. Content-Typewon't be set by Cloud Tasks. You can explicitly setContent-Typeto a media type when the task is created. For example,Content-Typecan be set to"application/octet-stream"or"application/json". The default value is set to "application/json". * User-Agent: This will be set to"Google-Cloud-Tasks"`. 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.
- HttpMethod Pulumi.Google Native. Cloud Tasks. V2. Http Target Http Method 
- 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.
- OauthToken Pulumi.Google Native. Cloud Tasks. V2. Inputs. OAuth Token 
- If specified, an OAuth token will be generated and attached as the Authorizationheader in the HTTP request. This type of authorization should generally only be used when calling Google APIs hosted on *.googleapis.com.
- OidcToken Pulumi.Google Native. Cloud Tasks. V2. Inputs. Oidc Token 
- If specified, an OIDC token will be generated and attached as an Authorizationheader 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.
- UriOverride Pulumi.Google Native. Cloud Tasks. V2. Inputs. Uri Override 
- URI override. When specified, overrides the execution URI for all the tasks in the queue.
- HeaderOverrides []HeaderOverride 
- HTTP target headers. This map contains the header field names and values. Headers will be set when running the CreateTask and/or BufferTask. These headers represent a subset of the headers that will be configured for 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: * Several predefined headers, prefixed with "X-CloudTasks-", can be used to define properties of the task. * Host: This will be computed by Cloud Tasks and derived from HttpRequest.url. * Content-Length: This will be computed by Cloud Tasks. Content-Typewon't be set by Cloud Tasks. You can explicitly setContent-Typeto a media type when the task is created. For example,Content-Typecan be set to"application/octet-stream"or"application/json". The default value is set to "application/json". * User-Agent: This will be set to"Google-Cloud-Tasks"`. 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.
- HttpMethod HttpTarget Http Method 
- 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.
- OauthToken OAuthToken 
- If specified, an OAuth token will be generated and attached as the Authorizationheader in the HTTP request. This type of authorization should generally only be used when calling Google APIs hosted on *.googleapis.com.
- OidcToken OidcToken 
- If specified, an OIDC token will be generated and attached as an Authorizationheader 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.
- UriOverride UriOverride 
- URI override. When specified, overrides the execution URI for all the tasks in the queue.
- headerOverrides List<HeaderOverride> 
- HTTP target headers. This map contains the header field names and values. Headers will be set when running the CreateTask and/or BufferTask. These headers represent a subset of the headers that will be configured for 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: * Several predefined headers, prefixed with "X-CloudTasks-", can be used to define properties of the task. * Host: This will be computed by Cloud Tasks and derived from HttpRequest.url. * Content-Length: This will be computed by Cloud Tasks. Content-Typewon't be set by Cloud Tasks. You can explicitly setContent-Typeto a media type when the task is created. For example,Content-Typecan be set to"application/octet-stream"or"application/json". The default value is set to "application/json". * User-Agent: This will be set to"Google-Cloud-Tasks"`. 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.
- httpMethod HttpTarget Http Method 
- 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.
- oauthToken OAuthToken 
- If specified, an OAuth token will be generated and attached as the Authorizationheader in the HTTP request. This type of authorization should generally only be used when calling Google APIs hosted on *.googleapis.com.
- oidcToken OidcToken 
- If specified, an OIDC token will be generated and attached as an Authorizationheader 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.
- uriOverride UriOverride 
- URI override. When specified, overrides the execution URI for all the tasks in the queue.
- headerOverrides HeaderOverride[] 
- HTTP target headers. This map contains the header field names and values. Headers will be set when running the CreateTask and/or BufferTask. These headers represent a subset of the headers that will be configured for 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: * Several predefined headers, prefixed with "X-CloudTasks-", can be used to define properties of the task. * Host: This will be computed by Cloud Tasks and derived from HttpRequest.url. * Content-Length: This will be computed by Cloud Tasks. Content-Typewon't be set by Cloud Tasks. You can explicitly setContent-Typeto a media type when the task is created. For example,Content-Typecan be set to"application/octet-stream"or"application/json". The default value is set to "application/json". * User-Agent: This will be set to"Google-Cloud-Tasks"`. 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.
- httpMethod HttpTarget Http Method 
- 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.
- oauthToken OAuthToken 
- If specified, an OAuth token will be generated and attached as the Authorizationheader in the HTTP request. This type of authorization should generally only be used when calling Google APIs hosted on *.googleapis.com.
- oidcToken OidcToken 
- If specified, an OIDC token will be generated and attached as an Authorizationheader 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.
- uriOverride UriOverride 
- URI override. When specified, overrides the execution URI for all the tasks in the queue.
- header_overrides Sequence[HeaderOverride] 
- HTTP target headers. This map contains the header field names and values. Headers will be set when running the CreateTask and/or BufferTask. These headers represent a subset of the headers that will be configured for 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: * Several predefined headers, prefixed with "X-CloudTasks-", can be used to define properties of the task. * Host: This will be computed by Cloud Tasks and derived from HttpRequest.url. * Content-Length: This will be computed by Cloud Tasks. Content-Typewon't be set by Cloud Tasks. You can explicitly setContent-Typeto a media type when the task is created. For example,Content-Typecan be set to"application/octet-stream"or"application/json". The default value is set to "application/json". * User-Agent: This will be set to"Google-Cloud-Tasks"`. 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 HttpTarget Http Method 
- 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 
- If specified, an OAuth token will be generated and attached as the Authorizationheader in the HTTP request. This type of authorization should generally only be used when calling Google APIs hosted on *.googleapis.com.
- oidc_token OidcToken 
- If specified, an OIDC token will be generated and attached as an Authorizationheader 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 
- URI override. When specified, overrides the execution URI for all the tasks in the queue.
- headerOverrides List<Property Map>
- HTTP target headers. This map contains the header field names and values. Headers will be set when running the CreateTask and/or BufferTask. These headers represent a subset of the headers that will be configured for 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: * Several predefined headers, prefixed with "X-CloudTasks-", can be used to define properties of the task. * Host: This will be computed by Cloud Tasks and derived from HttpRequest.url. * Content-Length: This will be computed by Cloud Tasks. Content-Typewon't be set by Cloud Tasks. You can explicitly setContent-Typeto a media type when the task is created. For example,Content-Typecan be set to"application/octet-stream"or"application/json". The default value is set to "application/json". * User-Agent: This will be set to"Google-Cloud-Tasks"`. 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.
- httpMethod "HTTP_METHOD_UNSPECIFIED" | "POST" | "GET" | "HEAD" | "PUT" | "DELETE" | "PATCH" | "OPTIONS"
- 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.
- oauthToken Property Map
- If specified, an OAuth token will be generated and attached as the Authorizationheader in the HTTP request. This type of authorization should generally only be used when calling Google APIs hosted on *.googleapis.com.
- oidcToken Property Map
- If specified, an OIDC token will be generated and attached as an Authorizationheader 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.
- uriOverride Property Map
- URI override. When specified, overrides the execution URI for all the tasks in the queue.
HttpTargetHttpMethod, HttpTargetHttpMethodArgs        
- HttpMethod Unspecified 
- HTTP_METHOD_UNSPECIFIEDHTTP method unspecified
- Post
- POSTHTTP POST
- Get
- GETHTTP GET
- Head
- HEADHTTP HEAD
- Put
- PUTHTTP PUT
- Delete
- DELETEHTTP DELETE
- Patch
- PATCHHTTP PATCH
- Options
- OPTIONSHTTP OPTIONS
- HttpTarget Http Method Http Method Unspecified 
- HTTP_METHOD_UNSPECIFIEDHTTP method unspecified
- HttpTarget Http Method Post 
- POSTHTTP POST
- HttpTarget Http Method Get 
- GETHTTP GET
- HttpTarget Http Method Head 
- HEADHTTP HEAD
- HttpTarget Http Method Put 
- PUTHTTP PUT
- HttpTarget Http Method Delete 
- DELETEHTTP DELETE
- HttpTarget Http Method Patch 
- PATCHHTTP PATCH
- HttpTarget Http Method Options 
- OPTIONSHTTP OPTIONS
- HttpMethod Unspecified 
- HTTP_METHOD_UNSPECIFIEDHTTP method unspecified
- Post
- POSTHTTP POST
- Get
- GETHTTP GET
- Head
- HEADHTTP HEAD
- Put
- PUTHTTP PUT
- Delete
- DELETEHTTP DELETE
- Patch
- PATCHHTTP PATCH
- Options
- OPTIONSHTTP OPTIONS
- HttpMethod Unspecified 
- HTTP_METHOD_UNSPECIFIEDHTTP method unspecified
- Post
- POSTHTTP POST
- Get
- GETHTTP GET
- Head
- HEADHTTP HEAD
- Put
- PUTHTTP PUT
- Delete
- DELETEHTTP DELETE
- Patch
- PATCHHTTP PATCH
- Options
- OPTIONSHTTP OPTIONS
- HTTP_METHOD_UNSPECIFIED
- HTTP_METHOD_UNSPECIFIEDHTTP method unspecified
- POST
- POSTHTTP POST
- GET
- GETHTTP GET
- HEAD
- HEADHTTP HEAD
- PUT
- PUTHTTP PUT
- DELETE
- DELETEHTTP DELETE
- PATCH
- PATCHHTTP PATCH
- OPTIONS
- OPTIONSHTTP OPTIONS
- "HTTP_METHOD_UNSPECIFIED"
- HTTP_METHOD_UNSPECIFIEDHTTP method unspecified
- "POST"
- POSTHTTP POST
- "GET"
- GETHTTP GET
- "HEAD"
- HEADHTTP HEAD
- "PUT"
- PUTHTTP PUT
- "DELETE"
- DELETEHTTP DELETE
- "PATCH"
- PATCHHTTP PATCH
- "OPTIONS"
- OPTIONSHTTP OPTIONS
HttpTargetResponse, HttpTargetResponseArgs      
- HeaderOverrides List<Pulumi.Google Native. Cloud Tasks. V2. Inputs. Header Override Response> 
- HTTP target headers. This map contains the header field names and values. Headers will be set when running the CreateTask and/or BufferTask. These headers represent a subset of the headers that will be configured for 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: * Several predefined headers, prefixed with "X-CloudTasks-", can be used to define properties of the task. * Host: This will be computed by Cloud Tasks and derived from HttpRequest.url. * Content-Length: This will be computed by Cloud Tasks. Content-Typewon't be set by Cloud Tasks. You can explicitly setContent-Typeto a media type when the task is created. For example,Content-Typecan be set to"application/octet-stream"or"application/json". The default value is set to "application/json". * User-Agent: This will be set to"Google-Cloud-Tasks"`. 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.
- HttpMethod 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.
- OauthToken Pulumi.Google Native. Cloud Tasks. V2. Inputs. OAuth Token Response 
- If specified, an OAuth token will be generated and attached as the Authorizationheader in the HTTP request. This type of authorization should generally only be used when calling Google APIs hosted on *.googleapis.com.
- OidcToken Pulumi.Google Native. Cloud Tasks. V2. Inputs. Oidc Token Response 
- If specified, an OIDC token will be generated and attached as an Authorizationheader 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.
- UriOverride Pulumi.Google Native. Cloud Tasks. V2. Inputs. Uri Override Response 
- URI override. When specified, overrides the execution URI for all the tasks in the queue.
- HeaderOverrides []HeaderOverride Response 
- HTTP target headers. This map contains the header field names and values. Headers will be set when running the CreateTask and/or BufferTask. These headers represent a subset of the headers that will be configured for 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: * Several predefined headers, prefixed with "X-CloudTasks-", can be used to define properties of the task. * Host: This will be computed by Cloud Tasks and derived from HttpRequest.url. * Content-Length: This will be computed by Cloud Tasks. Content-Typewon't be set by Cloud Tasks. You can explicitly setContent-Typeto a media type when the task is created. For example,Content-Typecan be set to"application/octet-stream"or"application/json". The default value is set to "application/json". * User-Agent: This will be set to"Google-Cloud-Tasks"`. 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.
- HttpMethod 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.
- OauthToken OAuthToken Response 
- If specified, an OAuth token will be generated and attached as the Authorizationheader in the HTTP request. This type of authorization should generally only be used when calling Google APIs hosted on *.googleapis.com.
- OidcToken OidcToken Response 
- If specified, an OIDC token will be generated and attached as an Authorizationheader 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.
- UriOverride UriOverride Response 
- URI override. When specified, overrides the execution URI for all the tasks in the queue.
- headerOverrides List<HeaderOverride Response> 
- HTTP target headers. This map contains the header field names and values. Headers will be set when running the CreateTask and/or BufferTask. These headers represent a subset of the headers that will be configured for 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: * Several predefined headers, prefixed with "X-CloudTasks-", can be used to define properties of the task. * Host: This will be computed by Cloud Tasks and derived from HttpRequest.url. * Content-Length: This will be computed by Cloud Tasks. Content-Typewon't be set by Cloud Tasks. You can explicitly setContent-Typeto a media type when the task is created. For example,Content-Typecan be set to"application/octet-stream"or"application/json". The default value is set to "application/json". * User-Agent: This will be set to"Google-Cloud-Tasks"`. 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.
- httpMethod 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.
- oauthToken OAuthToken Response 
- If specified, an OAuth token will be generated and attached as the Authorizationheader in the HTTP request. This type of authorization should generally only be used when calling Google APIs hosted on *.googleapis.com.
- oidcToken OidcToken Response 
- If specified, an OIDC token will be generated and attached as an Authorizationheader 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.
- uriOverride UriOverride Response 
- URI override. When specified, overrides the execution URI for all the tasks in the queue.
- headerOverrides HeaderOverride Response[] 
- HTTP target headers. This map contains the header field names and values. Headers will be set when running the CreateTask and/or BufferTask. These headers represent a subset of the headers that will be configured for 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: * Several predefined headers, prefixed with "X-CloudTasks-", can be used to define properties of the task. * Host: This will be computed by Cloud Tasks and derived from HttpRequest.url. * Content-Length: This will be computed by Cloud Tasks. Content-Typewon't be set by Cloud Tasks. You can explicitly setContent-Typeto a media type when the task is created. For example,Content-Typecan be set to"application/octet-stream"or"application/json". The default value is set to "application/json". * User-Agent: This will be set to"Google-Cloud-Tasks"`. 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.
- httpMethod 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.
- oauthToken OAuthToken Response 
- If specified, an OAuth token will be generated and attached as the Authorizationheader in the HTTP request. This type of authorization should generally only be used when calling Google APIs hosted on *.googleapis.com.
- oidcToken OidcToken Response 
- If specified, an OIDC token will be generated and attached as an Authorizationheader 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.
- uriOverride 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 CreateTask and/or BufferTask. These headers represent a subset of the headers that will be configured for 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: * Several predefined headers, prefixed with "X-CloudTasks-", can be used to define properties of the task. * Host: This will be computed by Cloud Tasks and derived from HttpRequest.url. * Content-Length: This will be computed by Cloud Tasks. Content-Typewon't be set by Cloud Tasks. You can explicitly setContent-Typeto a media type when the task is created. For example,Content-Typecan be set to"application/octet-stream"or"application/json". The default value is set to "application/json". * User-Agent: This will be set to"Google-Cloud-Tasks"`. 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 the Authorizationheader 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 Authorizationheader 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.
- headerOverrides List<Property Map>
- HTTP target headers. This map contains the header field names and values. Headers will be set when running the CreateTask and/or BufferTask. These headers represent a subset of the headers that will be configured for 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: * Several predefined headers, prefixed with "X-CloudTasks-", can be used to define properties of the task. * Host: This will be computed by Cloud Tasks and derived from HttpRequest.url. * Content-Length: This will be computed by Cloud Tasks. Content-Typewon't be set by Cloud Tasks. You can explicitly setContent-Typeto a media type when the task is created. For example,Content-Typecan be set to"application/octet-stream"or"application/json". The default value is set to "application/json". * User-Agent: This will be set to"Google-Cloud-Tasks"`. 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.
- httpMethod 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.
- oauthToken Property Map
- If specified, an OAuth token will be generated and attached as the Authorizationheader in the HTTP request. This type of authorization should generally only be used when calling Google APIs hosted on *.googleapis.com.
- oidcToken Property Map
- If specified, an OIDC token will be generated and attached as an Authorizationheader 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.
- uriOverride Property Map
- URI override. When specified, overrides the execution URI for all the tasks in the queue.
OAuthToken, OAuthTokenArgs    
- 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.
- ServiceAccount 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.
- ServiceAccount 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.
- serviceAccount 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.
- serviceAccount 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.
- serviceAccount 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.
OAuthTokenResponse, OAuthTokenResponseArgs      
- 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.
- ServiceAccount 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.
- ServiceAccount 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.
- serviceAccount 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.
- serviceAccount 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.
- serviceAccount 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.
OidcToken, OidcTokenArgs    
- Audience string
- Audience to be used when generating OIDC token. If not specified, the URI specified in target will be used.
- ServiceAccount 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.
- ServiceAccount 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.
- serviceAccount 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.
- serviceAccount 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.
- serviceAccount 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.
OidcTokenResponse, OidcTokenResponseArgs      
- Audience string
- Audience to be used when generating OIDC token. If not specified, the URI specified in target will be used.
- ServiceAccount 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.
- ServiceAccount 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.
- serviceAccount 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.
- serviceAccount 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.
- serviceAccount 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.
PathOverride, PathOverrideArgs    
- 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.
PathOverrideResponse, PathOverrideResponseArgs      
- 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.
QueryOverride, QueryOverrideArgs    
- QueryParams string
- The query parameters (e.g., qparam1=123&qparam2=456). Default is an empty string.
- QueryParams string
- The query parameters (e.g., qparam1=123&qparam2=456). Default is an empty string.
- queryParams String
- The query parameters (e.g., qparam1=123&qparam2=456). Default is an empty string.
- queryParams 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.
- queryParams String
- The query parameters (e.g., qparam1=123&qparam2=456). Default is an empty string.
QueryOverrideResponse, QueryOverrideResponseArgs      
- QueryParams string
- The query parameters (e.g., qparam1=123&qparam2=456). Default is an empty string.
- QueryParams string
- The query parameters (e.g., qparam1=123&qparam2=456). Default is an empty string.
- queryParams String
- The query parameters (e.g., qparam1=123&qparam2=456). Default is an empty string.
- queryParams 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.
- queryParams String
- The query parameters (e.g., qparam1=123&qparam2=456). Default is an empty string.
RateLimits, RateLimitsArgs    
- MaxConcurrent intDispatches 
- 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 has the same meaning as max_concurrent_requests in queue.yaml/xml.
- MaxDispatches doublePer 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. * The maximum allowed value is 500. This field has the same meaning as rate in queue.yaml/xml.
- MaxConcurrent intDispatches 
- 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 has the same meaning as max_concurrent_requests in queue.yaml/xml.
- MaxDispatches float64Per 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. * The maximum allowed value is 500. This field has the same meaning as rate in queue.yaml/xml.
- maxConcurrent IntegerDispatches 
- 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 has the same meaning as max_concurrent_requests in queue.yaml/xml.
- maxDispatches DoublePer 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. * The maximum allowed value is 500. This field has the same meaning as rate in queue.yaml/xml.
- maxConcurrent numberDispatches 
- 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 has the same meaning as max_concurrent_requests in queue.yaml/xml.
- maxDispatches numberPer 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. * The maximum allowed value is 500. This field has the same meaning as rate in queue.yaml/xml.
- max_concurrent_ intdispatches 
- 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 has the same meaning as max_concurrent_requests in queue.yaml/xml.
- max_dispatches_ floatper_ 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. * The maximum allowed value is 500. This field has the same meaning as rate in queue.yaml/xml.
- maxConcurrent NumberDispatches 
- 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 has the same meaning as max_concurrent_requests in queue.yaml/xml.
- maxDispatches NumberPer 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. * The maximum allowed value is 500. This field has the same meaning as rate in queue.yaml/xml.
RateLimitsResponse, RateLimitsResponseArgs      
- MaxBurst 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. Cloud Tasks will pick the value ofmax_burst_sizebased on the value of max_dispatches_per_second. For queues that were created or updated usingqueue.yaml/xml,max_burst_sizeis equal to bucket_size. Sincemax_burst_sizeis output only, if UpdateQueue is called on a queue created byqueue.yaml/xml,max_burst_sizewill be reset based on the value of max_dispatches_per_second, regardless of whether max_dispatches_per_second is updated.
- MaxConcurrent intDispatches 
- 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 has the same meaning as max_concurrent_requests in queue.yaml/xml.
- MaxDispatches doublePer 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. * The maximum allowed value is 500. This field has the same meaning as rate in queue.yaml/xml.
- MaxBurst 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. Cloud Tasks will pick the value ofmax_burst_sizebased on the value of max_dispatches_per_second. For queues that were created or updated usingqueue.yaml/xml,max_burst_sizeis equal to bucket_size. Sincemax_burst_sizeis output only, if UpdateQueue is called on a queue created byqueue.yaml/xml,max_burst_sizewill be reset based on the value of max_dispatches_per_second, regardless of whether max_dispatches_per_second is updated.
- MaxConcurrent intDispatches 
- 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 has the same meaning as max_concurrent_requests in queue.yaml/xml.
- MaxDispatches float64Per 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. * The maximum allowed value is 500. This field has the same meaning as rate in queue.yaml/xml.
- maxBurst 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. Cloud Tasks will pick the value ofmax_burst_sizebased on the value of max_dispatches_per_second. For queues that were created or updated usingqueue.yaml/xml,max_burst_sizeis equal to bucket_size. Sincemax_burst_sizeis output only, if UpdateQueue is called on a queue created byqueue.yaml/xml,max_burst_sizewill be reset based on the value of max_dispatches_per_second, regardless of whether max_dispatches_per_second is updated.
- maxConcurrent IntegerDispatches 
- 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 has the same meaning as max_concurrent_requests in queue.yaml/xml.
- maxDispatches DoublePer 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. * The maximum allowed value is 500. This field has the same meaning as rate in queue.yaml/xml.
- maxBurst 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. Cloud Tasks will pick the value ofmax_burst_sizebased on the value of max_dispatches_per_second. For queues that were created or updated usingqueue.yaml/xml,max_burst_sizeis equal to bucket_size. Sincemax_burst_sizeis output only, if UpdateQueue is called on a queue created byqueue.yaml/xml,max_burst_sizewill be reset based on the value of max_dispatches_per_second, regardless of whether max_dispatches_per_second is updated.
- maxConcurrent numberDispatches 
- 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 has the same meaning as max_concurrent_requests in queue.yaml/xml.
- maxDispatches numberPer 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. * The maximum allowed value is 500. 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. Cloud Tasks will pick the value ofmax_burst_sizebased on the value of max_dispatches_per_second. For queues that were created or updated usingqueue.yaml/xml,max_burst_sizeis equal to bucket_size. Sincemax_burst_sizeis output only, if UpdateQueue is called on a queue created byqueue.yaml/xml,max_burst_sizewill be reset based on the value of max_dispatches_per_second, regardless of whether max_dispatches_per_second is updated.
- max_concurrent_ intdispatches 
- 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 has the same meaning as max_concurrent_requests in queue.yaml/xml.
- max_dispatches_ floatper_ 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. * The maximum allowed value is 500. This field has the same meaning as rate in queue.yaml/xml.
- maxBurst 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. Cloud Tasks will pick the value ofmax_burst_sizebased on the value of max_dispatches_per_second. For queues that were created or updated usingqueue.yaml/xml,max_burst_sizeis equal to bucket_size. Sincemax_burst_sizeis output only, if UpdateQueue is called on a queue created byqueue.yaml/xml,max_burst_sizewill be reset based on the value of max_dispatches_per_second, regardless of whether max_dispatches_per_second is updated.
- maxConcurrent NumberDispatches 
- 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 has the same meaning as max_concurrent_requests in queue.yaml/xml.
- maxDispatches NumberPer 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. * The maximum allowed value is 500. This field has the same meaning as rate in queue.yaml/xml.
RetryConfig, RetryConfigArgs    
- MaxAttempts int
- Number of attempts per task. Cloud Tasks will attempt the task max_attemptstimes (that is, if the first attempt fails, then there will bemax_attempts - 1retries). Must be >= -1. If unspecified when the queue is created, Cloud Tasks will pick the default. -1 indicates unlimited attempts. This field has the same meaning as task_retry_limit in queue.yaml/xml.
- MaxBackoff 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. The value must be given as a string that indicates the length of time (in seconds) followed by s(for "seconds"). For more information on the format, see the documentation for Duration.max_backoffwill be truncated to the nearest second. This field has the same meaning as max_backoff_seconds in queue.yaml/xml.
- MaxDoublings int
- The time between retries will double max_doublingstimes. A task's retry interval starts at min_backoff, then doublesmax_doublingstimes, 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_doublingsis 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 has the same meaning as max_doublings in queue.yaml/xml.
- MaxRetry stringDuration 
- If positive, max_retry_durationspecifies the time limit for retrying a failed task, measured from when the task was first attempted. Oncemax_retry_durationtime 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. The value must be given as a string that indicates the length of time (in seconds) followed bys(for "seconds"). For the maximum possible value or the format, see the documentation for Duration.max_retry_durationwill be truncated to the nearest second. This field has the same meaning as task_age_limit in queue.yaml/xml.
- MinBackoff 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. The value must be given as a string that indicates the length of time (in seconds) followed by s(for "seconds"). For more information on the format, see the documentation for Duration.min_backoffwill be truncated to the nearest second. This field has the same meaning as min_backoff_seconds in queue.yaml/xml.
- MaxAttempts int
- Number of attempts per task. Cloud Tasks will attempt the task max_attemptstimes (that is, if the first attempt fails, then there will bemax_attempts - 1retries). Must be >= -1. If unspecified when the queue is created, Cloud Tasks will pick the default. -1 indicates unlimited attempts. This field has the same meaning as task_retry_limit in queue.yaml/xml.
- MaxBackoff 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. The value must be given as a string that indicates the length of time (in seconds) followed by s(for "seconds"). For more information on the format, see the documentation for Duration.max_backoffwill be truncated to the nearest second. This field has the same meaning as max_backoff_seconds in queue.yaml/xml.
- MaxDoublings int
- The time between retries will double max_doublingstimes. A task's retry interval starts at min_backoff, then doublesmax_doublingstimes, 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_doublingsis 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 has the same meaning as max_doublings in queue.yaml/xml.
- MaxRetry stringDuration 
- If positive, max_retry_durationspecifies the time limit for retrying a failed task, measured from when the task was first attempted. Oncemax_retry_durationtime 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. The value must be given as a string that indicates the length of time (in seconds) followed bys(for "seconds"). For the maximum possible value or the format, see the documentation for Duration.max_retry_durationwill be truncated to the nearest second. This field has the same meaning as task_age_limit in queue.yaml/xml.
- MinBackoff 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. The value must be given as a string that indicates the length of time (in seconds) followed by s(for "seconds"). For more information on the format, see the documentation for Duration.min_backoffwill be truncated to the nearest second. This field has the same meaning as min_backoff_seconds in queue.yaml/xml.
- maxAttempts Integer
- Number of attempts per task. Cloud Tasks will attempt the task max_attemptstimes (that is, if the first attempt fails, then there will bemax_attempts - 1retries). Must be >= -1. If unspecified when the queue is created, Cloud Tasks will pick the default. -1 indicates unlimited attempts. This field has the same meaning as task_retry_limit in queue.yaml/xml.
- maxBackoff 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. The value must be given as a string that indicates the length of time (in seconds) followed by s(for "seconds"). For more information on the format, see the documentation for Duration.max_backoffwill be truncated to the nearest second. This field has the same meaning as max_backoff_seconds in queue.yaml/xml.
- maxDoublings Integer
- The time between retries will double max_doublingstimes. A task's retry interval starts at min_backoff, then doublesmax_doublingstimes, 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_doublingsis 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 has the same meaning as max_doublings in queue.yaml/xml.
- maxRetry StringDuration 
- If positive, max_retry_durationspecifies the time limit for retrying a failed task, measured from when the task was first attempted. Oncemax_retry_durationtime 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. The value must be given as a string that indicates the length of time (in seconds) followed bys(for "seconds"). For the maximum possible value or the format, see the documentation for Duration.max_retry_durationwill be truncated to the nearest second. This field has the same meaning as task_age_limit in queue.yaml/xml.
- minBackoff 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. The value must be given as a string that indicates the length of time (in seconds) followed by s(for "seconds"). For more information on the format, see the documentation for Duration.min_backoffwill be truncated to the nearest second. This field has the same meaning as min_backoff_seconds in queue.yaml/xml.
- maxAttempts number
- Number of attempts per task. Cloud Tasks will attempt the task max_attemptstimes (that is, if the first attempt fails, then there will bemax_attempts - 1retries). Must be >= -1. If unspecified when the queue is created, Cloud Tasks will pick the default. -1 indicates unlimited attempts. This field has the same meaning as task_retry_limit in queue.yaml/xml.
- maxBackoff 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. The value must be given as a string that indicates the length of time (in seconds) followed by s(for "seconds"). For more information on the format, see the documentation for Duration.max_backoffwill be truncated to the nearest second. This field has the same meaning as max_backoff_seconds in queue.yaml/xml.
- maxDoublings number
- The time between retries will double max_doublingstimes. A task's retry interval starts at min_backoff, then doublesmax_doublingstimes, 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_doublingsis 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 has the same meaning as max_doublings in queue.yaml/xml.
- maxRetry stringDuration 
- If positive, max_retry_durationspecifies the time limit for retrying a failed task, measured from when the task was first attempted. Oncemax_retry_durationtime 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. The value must be given as a string that indicates the length of time (in seconds) followed bys(for "seconds"). For the maximum possible value or the format, see the documentation for Duration.max_retry_durationwill be truncated to the nearest second. This field has the same meaning as task_age_limit in queue.yaml/xml.
- minBackoff 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. The value must be given as a string that indicates the length of time (in seconds) followed by s(for "seconds"). For more information on the format, see the documentation for Duration.min_backoffwill be truncated to the nearest second. This field has the same meaning as min_backoff_seconds in queue.yaml/xml.
- max_attempts int
- Number of attempts per task. Cloud Tasks will attempt the task max_attemptstimes (that is, if the first attempt fails, then there will bemax_attempts - 1retries). Must be >= -1. If unspecified when the queue is created, Cloud Tasks will pick the default. -1 indicates unlimited attempts. This field has the same meaning as task_retry_limit in queue.yaml/xml.
- 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. The value must be given as a string that indicates the length of time (in seconds) followed by s(for "seconds"). For more information on the format, see the documentation for Duration.max_backoffwill 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_doublingstimes. A task's retry interval starts at min_backoff, then doublesmax_doublingstimes, 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_doublingsis 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 has the same meaning as max_doublings in queue.yaml/xml.
- max_retry_ strduration 
- If positive, max_retry_durationspecifies the time limit for retrying a failed task, measured from when the task was first attempted. Oncemax_retry_durationtime 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. The value must be given as a string that indicates the length of time (in seconds) followed bys(for "seconds"). For the maximum possible value or the format, see the documentation for Duration.max_retry_durationwill 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. The value must be given as a string that indicates the length of time (in seconds) followed by s(for "seconds"). For more information on the format, see the documentation for Duration.min_backoffwill be truncated to the nearest second. This field has the same meaning as min_backoff_seconds in queue.yaml/xml.
- maxAttempts Number
- Number of attempts per task. Cloud Tasks will attempt the task max_attemptstimes (that is, if the first attempt fails, then there will bemax_attempts - 1retries). Must be >= -1. If unspecified when the queue is created, Cloud Tasks will pick the default. -1 indicates unlimited attempts. This field has the same meaning as task_retry_limit in queue.yaml/xml.
- maxBackoff 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. The value must be given as a string that indicates the length of time (in seconds) followed by s(for "seconds"). For more information on the format, see the documentation for Duration.max_backoffwill be truncated to the nearest second. This field has the same meaning as max_backoff_seconds in queue.yaml/xml.
- maxDoublings Number
- The time between retries will double max_doublingstimes. A task's retry interval starts at min_backoff, then doublesmax_doublingstimes, 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_doublingsis 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 has the same meaning as max_doublings in queue.yaml/xml.
- maxRetry StringDuration 
- If positive, max_retry_durationspecifies the time limit for retrying a failed task, measured from when the task was first attempted. Oncemax_retry_durationtime 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. The value must be given as a string that indicates the length of time (in seconds) followed bys(for "seconds"). For the maximum possible value or the format, see the documentation for Duration.max_retry_durationwill be truncated to the nearest second. This field has the same meaning as task_age_limit in queue.yaml/xml.
- minBackoff 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. The value must be given as a string that indicates the length of time (in seconds) followed by s(for "seconds"). For more information on the format, see the documentation for Duration.min_backoffwill be truncated to the nearest second. This field has the same meaning as min_backoff_seconds in queue.yaml/xml.
RetryConfigResponse, RetryConfigResponseArgs      
- MaxAttempts int
- Number of attempts per task. Cloud Tasks will attempt the task max_attemptstimes (that is, if the first attempt fails, then there will bemax_attempts - 1retries). Must be >= -1. If unspecified when the queue is created, Cloud Tasks will pick the default. -1 indicates unlimited attempts. This field has the same meaning as task_retry_limit in queue.yaml/xml.
- MaxBackoff 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. The value must be given as a string that indicates the length of time (in seconds) followed by s(for "seconds"). For more information on the format, see the documentation for Duration.max_backoffwill be truncated to the nearest second. This field has the same meaning as max_backoff_seconds in queue.yaml/xml.
- MaxDoublings int
- The time between retries will double max_doublingstimes. A task's retry interval starts at min_backoff, then doublesmax_doublingstimes, 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_doublingsis 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 has the same meaning as max_doublings in queue.yaml/xml.
- MaxRetry stringDuration 
- If positive, max_retry_durationspecifies the time limit for retrying a failed task, measured from when the task was first attempted. Oncemax_retry_durationtime 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. The value must be given as a string that indicates the length of time (in seconds) followed bys(for "seconds"). For the maximum possible value or the format, see the documentation for Duration.max_retry_durationwill be truncated to the nearest second. This field has the same meaning as task_age_limit in queue.yaml/xml.
- MinBackoff 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. The value must be given as a string that indicates the length of time (in seconds) followed by s(for "seconds"). For more information on the format, see the documentation for Duration.min_backoffwill be truncated to the nearest second. This field has the same meaning as min_backoff_seconds in queue.yaml/xml.
- MaxAttempts int
- Number of attempts per task. Cloud Tasks will attempt the task max_attemptstimes (that is, if the first attempt fails, then there will bemax_attempts - 1retries). Must be >= -1. If unspecified when the queue is created, Cloud Tasks will pick the default. -1 indicates unlimited attempts. This field has the same meaning as task_retry_limit in queue.yaml/xml.
- MaxBackoff 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. The value must be given as a string that indicates the length of time (in seconds) followed by s(for "seconds"). For more information on the format, see the documentation for Duration.max_backoffwill be truncated to the nearest second. This field has the same meaning as max_backoff_seconds in queue.yaml/xml.
- MaxDoublings int
- The time between retries will double max_doublingstimes. A task's retry interval starts at min_backoff, then doublesmax_doublingstimes, 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_doublingsis 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 has the same meaning as max_doublings in queue.yaml/xml.
- MaxRetry stringDuration 
- If positive, max_retry_durationspecifies the time limit for retrying a failed task, measured from when the task was first attempted. Oncemax_retry_durationtime 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. The value must be given as a string that indicates the length of time (in seconds) followed bys(for "seconds"). For the maximum possible value or the format, see the documentation for Duration.max_retry_durationwill be truncated to the nearest second. This field has the same meaning as task_age_limit in queue.yaml/xml.
- MinBackoff 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. The value must be given as a string that indicates the length of time (in seconds) followed by s(for "seconds"). For more information on the format, see the documentation for Duration.min_backoffwill be truncated to the nearest second. This field has the same meaning as min_backoff_seconds in queue.yaml/xml.
- maxAttempts Integer
- Number of attempts per task. Cloud Tasks will attempt the task max_attemptstimes (that is, if the first attempt fails, then there will bemax_attempts - 1retries). Must be >= -1. If unspecified when the queue is created, Cloud Tasks will pick the default. -1 indicates unlimited attempts. This field has the same meaning as task_retry_limit in queue.yaml/xml.
- maxBackoff 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. The value must be given as a string that indicates the length of time (in seconds) followed by s(for "seconds"). For more information on the format, see the documentation for Duration.max_backoffwill be truncated to the nearest second. This field has the same meaning as max_backoff_seconds in queue.yaml/xml.
- maxDoublings Integer
- The time between retries will double max_doublingstimes. A task's retry interval starts at min_backoff, then doublesmax_doublingstimes, 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_doublingsis 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 has the same meaning as max_doublings in queue.yaml/xml.
- maxRetry StringDuration 
- If positive, max_retry_durationspecifies the time limit for retrying a failed task, measured from when the task was first attempted. Oncemax_retry_durationtime 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. The value must be given as a string that indicates the length of time (in seconds) followed bys(for "seconds"). For the maximum possible value or the format, see the documentation for Duration.max_retry_durationwill be truncated to the nearest second. This field has the same meaning as task_age_limit in queue.yaml/xml.
- minBackoff 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. The value must be given as a string that indicates the length of time (in seconds) followed by s(for "seconds"). For more information on the format, see the documentation for Duration.min_backoffwill be truncated to the nearest second. This field has the same meaning as min_backoff_seconds in queue.yaml/xml.
- maxAttempts number
- Number of attempts per task. Cloud Tasks will attempt the task max_attemptstimes (that is, if the first attempt fails, then there will bemax_attempts - 1retries). Must be >= -1. If unspecified when the queue is created, Cloud Tasks will pick the default. -1 indicates unlimited attempts. This field has the same meaning as task_retry_limit in queue.yaml/xml.
- maxBackoff 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. The value must be given as a string that indicates the length of time (in seconds) followed by s(for "seconds"). For more information on the format, see the documentation for Duration.max_backoffwill be truncated to the nearest second. This field has the same meaning as max_backoff_seconds in queue.yaml/xml.
- maxDoublings number
- The time between retries will double max_doublingstimes. A task's retry interval starts at min_backoff, then doublesmax_doublingstimes, 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_doublingsis 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 has the same meaning as max_doublings in queue.yaml/xml.
- maxRetry stringDuration 
- If positive, max_retry_durationspecifies the time limit for retrying a failed task, measured from when the task was first attempted. Oncemax_retry_durationtime 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. The value must be given as a string that indicates the length of time (in seconds) followed bys(for "seconds"). For the maximum possible value or the format, see the documentation for Duration.max_retry_durationwill be truncated to the nearest second. This field has the same meaning as task_age_limit in queue.yaml/xml.
- minBackoff 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. The value must be given as a string that indicates the length of time (in seconds) followed by s(for "seconds"). For more information on the format, see the documentation for Duration.min_backoffwill be truncated to the nearest second. This field has the same meaning as min_backoff_seconds in queue.yaml/xml.
- max_attempts int
- Number of attempts per task. Cloud Tasks will attempt the task max_attemptstimes (that is, if the first attempt fails, then there will bemax_attempts - 1retries). Must be >= -1. If unspecified when the queue is created, Cloud Tasks will pick the default. -1 indicates unlimited attempts. This field has the same meaning as task_retry_limit in queue.yaml/xml.
- 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. The value must be given as a string that indicates the length of time (in seconds) followed by s(for "seconds"). For more information on the format, see the documentation for Duration.max_backoffwill 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_doublingstimes. A task's retry interval starts at min_backoff, then doublesmax_doublingstimes, 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_doublingsis 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 has the same meaning as max_doublings in queue.yaml/xml.
- max_retry_ strduration 
- If positive, max_retry_durationspecifies the time limit for retrying a failed task, measured from when the task was first attempted. Oncemax_retry_durationtime 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. The value must be given as a string that indicates the length of time (in seconds) followed bys(for "seconds"). For the maximum possible value or the format, see the documentation for Duration.max_retry_durationwill 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. The value must be given as a string that indicates the length of time (in seconds) followed by s(for "seconds"). For more information on the format, see the documentation for Duration.min_backoffwill be truncated to the nearest second. This field has the same meaning as min_backoff_seconds in queue.yaml/xml.
- maxAttempts Number
- Number of attempts per task. Cloud Tasks will attempt the task max_attemptstimes (that is, if the first attempt fails, then there will bemax_attempts - 1retries). Must be >= -1. If unspecified when the queue is created, Cloud Tasks will pick the default. -1 indicates unlimited attempts. This field has the same meaning as task_retry_limit in queue.yaml/xml.
- maxBackoff 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. The value must be given as a string that indicates the length of time (in seconds) followed by s(for "seconds"). For more information on the format, see the documentation for Duration.max_backoffwill be truncated to the nearest second. This field has the same meaning as max_backoff_seconds in queue.yaml/xml.
- maxDoublings Number
- The time between retries will double max_doublingstimes. A task's retry interval starts at min_backoff, then doublesmax_doublingstimes, 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_doublingsis 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 has the same meaning as max_doublings in queue.yaml/xml.
- maxRetry StringDuration 
- If positive, max_retry_durationspecifies the time limit for retrying a failed task, measured from when the task was first attempted. Oncemax_retry_durationtime 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. The value must be given as a string that indicates the length of time (in seconds) followed bys(for "seconds"). For the maximum possible value or the format, see the documentation for Duration.max_retry_durationwill be truncated to the nearest second. This field has the same meaning as task_age_limit in queue.yaml/xml.
- minBackoff 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. The value must be given as a string that indicates the length of time (in seconds) followed by s(for "seconds"). For more information on the format, see the documentation for Duration.min_backoffwill be truncated to the nearest second. This field has the same meaning as min_backoff_seconds in queue.yaml/xml.
StackdriverLoggingConfig, StackdriverLoggingConfigArgs      
- SamplingRatio double
- Specifies the fraction of operations to write to Stackdriver Logging. This field may contain any value between 0.0 and 1.0, inclusive. 0.0 is the default and means that no operations are logged.
- SamplingRatio float64
- Specifies the fraction of operations to write to Stackdriver Logging. This field may contain any value between 0.0 and 1.0, inclusive. 0.0 is the default and means that no operations are logged.
- samplingRatio Double
- Specifies the fraction of operations to write to Stackdriver Logging. This field may contain any value between 0.0 and 1.0, inclusive. 0.0 is the default and means that no operations are logged.
- samplingRatio number
- Specifies the fraction of operations to write to Stackdriver Logging. This field may contain any value between 0.0 and 1.0, inclusive. 0.0 is the default and means that no operations are logged.
- sampling_ratio float
- Specifies the fraction of operations to write to Stackdriver Logging. This field may contain any value between 0.0 and 1.0, inclusive. 0.0 is the default and means that no operations are logged.
- samplingRatio Number
- Specifies the fraction of operations to write to Stackdriver Logging. This field may contain any value between 0.0 and 1.0, inclusive. 0.0 is the default and means that no operations are logged.
StackdriverLoggingConfigResponse, StackdriverLoggingConfigResponseArgs        
- SamplingRatio double
- Specifies the fraction of operations to write to Stackdriver Logging. This field may contain any value between 0.0 and 1.0, inclusive. 0.0 is the default and means that no operations are logged.
- SamplingRatio float64
- Specifies the fraction of operations to write to Stackdriver Logging. This field may contain any value between 0.0 and 1.0, inclusive. 0.0 is the default and means that no operations are logged.
- samplingRatio Double
- Specifies the fraction of operations to write to Stackdriver Logging. This field may contain any value between 0.0 and 1.0, inclusive. 0.0 is the default and means that no operations are logged.
- samplingRatio number
- Specifies the fraction of operations to write to Stackdriver Logging. This field may contain any value between 0.0 and 1.0, inclusive. 0.0 is the default and means that no operations are logged.
- sampling_ratio float
- Specifies the fraction of operations to write to Stackdriver Logging. This field may contain any value between 0.0 and 1.0, inclusive. 0.0 is the default and means that no operations are logged.
- samplingRatio Number
- Specifies the fraction of operations to write to Stackdriver Logging. This field may contain any value between 0.0 and 1.0, inclusive. 0.0 is the default and means that no operations are logged.
UriOverride, UriOverrideArgs    
- 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).
- PathOverride Pulumi.Google Native. Cloud Tasks. V2. Inputs. Path Override 
- 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.
- QueryOverride Pulumi.Google Native. Cloud Tasks. V2. Inputs. Query Override 
- 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
Pulumi.Google Native. Cloud Tasks. V2. Uri Override Scheme 
- Scheme override. When specified, the task URI scheme is replaced by the provided value (HTTP or HTTPS).
- UriOverride Pulumi.Enforce Mode Google Native. Cloud Tasks. V2. Uri Override Uri Override Enforce 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).
- PathOverride PathOverride 
- 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.
- QueryOverride QueryOverride 
- 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
UriOverride Scheme 
- Scheme override. When specified, the task URI scheme is replaced by the provided value (HTTP or HTTPS).
- UriOverride UriEnforce Mode Override Uri Override Enforce 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).
- pathOverride PathOverride 
- 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.
- queryOverride QueryOverride 
- 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
UriOverride Scheme 
- Scheme override. When specified, the task URI scheme is replaced by the provided value (HTTP or HTTPS).
- uriOverride UriEnforce Mode Override Uri Override Enforce 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).
- pathOverride PathOverride 
- 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.
- queryOverride QueryOverride 
- 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
UriOverride Scheme 
- Scheme override. When specified, the task URI scheme is replaced by the provided value (HTTP or HTTPS).
- uriOverride UriEnforce Mode Override Uri Override Enforce 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 
- 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 
- 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
UriOverride Scheme 
- Scheme override. When specified, the task URI scheme is replaced by the provided value (HTTP or HTTPS).
- uri_override_ Urienforce_ mode Override Uri Override Enforce 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).
- pathOverride 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.
- queryOverride 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 "SCHEME_UNSPECIFIED" | "HTTP" | "HTTPS"
- Scheme override. When specified, the task URI scheme is replaced by the provided value (HTTP or HTTPS).
- uriOverride "URI_OVERRIDE_ENFORCE_MODE_UNSPECIFIED" | "IF_NOT_EXISTS" | "ALWAYS"Enforce Mode 
- URI Override Enforce Mode When specified, determines the Target UriOverride mode. If not specified, it defaults to ALWAYS.
UriOverrideResponse, UriOverrideResponseArgs      
- 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).
- PathOverride Pulumi.Google Native. Cloud Tasks. V2. 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.
- QueryOverride Pulumi.Google Native. Cloud Tasks. V2. 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).
- UriOverride 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).
- PathOverride 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.
- QueryOverride 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).
- UriOverride 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).
- pathOverride 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.
- queryOverride 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).
- uriOverride 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).
- pathOverride 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.
- queryOverride 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).
- uriOverride 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).
- pathOverride 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.
- queryOverride 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).
- uriOverride StringEnforce Mode 
- URI Override Enforce Mode When specified, determines the Target UriOverride mode. If not specified, it defaults to ALWAYS.
UriOverrideScheme, UriOverrideSchemeArgs      
- SchemeUnspecified 
- SCHEME_UNSPECIFIEDScheme unspecified. Defaults to HTTPS.
- Http
- HTTPConvert the scheme to HTTP, e.g., https://www.google.ca will change to http://www.google.ca.
- Https
- HTTPSConvert the scheme to HTTPS, e.g., http://www.google.ca will change to https://www.google.ca.
- UriOverride Scheme Scheme Unspecified 
- SCHEME_UNSPECIFIEDScheme unspecified. Defaults to HTTPS.
- UriOverride Scheme Http 
- HTTPConvert the scheme to HTTP, e.g., https://www.google.ca will change to http://www.google.ca.
- UriOverride Scheme Https 
- HTTPSConvert the scheme to HTTPS, e.g., http://www.google.ca will change to https://www.google.ca.
- SchemeUnspecified 
- SCHEME_UNSPECIFIEDScheme unspecified. Defaults to HTTPS.
- Http
- HTTPConvert the scheme to HTTP, e.g., https://www.google.ca will change to http://www.google.ca.
- Https
- HTTPSConvert the scheme to HTTPS, e.g., http://www.google.ca will change to https://www.google.ca.
- SchemeUnspecified 
- SCHEME_UNSPECIFIEDScheme unspecified. Defaults to HTTPS.
- Http
- HTTPConvert the scheme to HTTP, e.g., https://www.google.ca will change to http://www.google.ca.
- Https
- HTTPSConvert the scheme to HTTPS, e.g., http://www.google.ca will change to https://www.google.ca.
- SCHEME_UNSPECIFIED
- SCHEME_UNSPECIFIEDScheme unspecified. Defaults to HTTPS.
- HTTP
- HTTPConvert the scheme to HTTP, e.g., https://www.google.ca will change to http://www.google.ca.
- HTTPS
- HTTPSConvert the scheme to HTTPS, e.g., http://www.google.ca will change to https://www.google.ca.
- "SCHEME_UNSPECIFIED"
- SCHEME_UNSPECIFIEDScheme unspecified. Defaults to HTTPS.
- "HTTP"
- HTTPConvert the scheme to HTTP, e.g., https://www.google.ca will change to http://www.google.ca.
- "HTTPS"
- HTTPSConvert the scheme to HTTPS, e.g., http://www.google.ca will change to https://www.google.ca.
UriOverrideUriOverrideEnforceMode, UriOverrideUriOverrideEnforceModeArgs            
- UriOverride Enforce Mode Unspecified 
- URI_OVERRIDE_ENFORCE_MODE_UNSPECIFIEDUriOverrideEnforceMode Unspecified. Defaults to ALWAYS.
- IfNot Exists 
- IF_NOT_EXISTSIn the IF_NOT_EXISTS mode, queue-level configuration is only applied where task-level configuration does not exist.
- Always
- ALWAYSIn the ALWAYS mode, queue-level configuration overrides all task-level configuration
- UriOverride Uri Override Enforce Mode Uri Override Enforce Mode Unspecified 
- URI_OVERRIDE_ENFORCE_MODE_UNSPECIFIEDUriOverrideEnforceMode Unspecified. Defaults to ALWAYS.
- UriOverride Uri Override Enforce Mode If Not Exists 
- IF_NOT_EXISTSIn the IF_NOT_EXISTS mode, queue-level configuration is only applied where task-level configuration does not exist.
- UriOverride Uri Override Enforce Mode Always 
- ALWAYSIn the ALWAYS mode, queue-level configuration overrides all task-level configuration
- UriOverride Enforce Mode Unspecified 
- URI_OVERRIDE_ENFORCE_MODE_UNSPECIFIEDUriOverrideEnforceMode Unspecified. Defaults to ALWAYS.
- IfNot Exists 
- IF_NOT_EXISTSIn the IF_NOT_EXISTS mode, queue-level configuration is only applied where task-level configuration does not exist.
- Always
- ALWAYSIn the ALWAYS mode, queue-level configuration overrides all task-level configuration
- UriOverride Enforce Mode Unspecified 
- URI_OVERRIDE_ENFORCE_MODE_UNSPECIFIEDUriOverrideEnforceMode Unspecified. Defaults to ALWAYS.
- IfNot Exists 
- IF_NOT_EXISTSIn the IF_NOT_EXISTS mode, queue-level configuration is only applied where task-level configuration does not exist.
- Always
- ALWAYSIn the ALWAYS mode, queue-level configuration overrides all task-level configuration
- URI_OVERRIDE_ENFORCE_MODE_UNSPECIFIED
- URI_OVERRIDE_ENFORCE_MODE_UNSPECIFIEDUriOverrideEnforceMode Unspecified. Defaults to ALWAYS.
- IF_NOT_EXISTS
- IF_NOT_EXISTSIn the IF_NOT_EXISTS mode, queue-level configuration is only applied where task-level configuration does not exist.
- ALWAYS
- ALWAYSIn the ALWAYS mode, queue-level configuration overrides all task-level configuration
- "URI_OVERRIDE_ENFORCE_MODE_UNSPECIFIED"
- URI_OVERRIDE_ENFORCE_MODE_UNSPECIFIEDUriOverrideEnforceMode Unspecified. Defaults to ALWAYS.
- "IF_NOT_EXISTS"
- IF_NOT_EXISTSIn the IF_NOT_EXISTS mode, queue-level configuration is only applied where task-level configuration does not exist.
- "ALWAYS"
- ALWAYSIn the ALWAYS mode, queue-level configuration overrides all task-level configuration
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.