Struct google_cloudtasks2_beta2::CreateTaskRequest [−][src]
Request message for CreateTask.
Activities
This type is used in activities, which are methods you may call on this type or where this type is involved in. The list links the activity name, along with information about where it is used (one of request and response).
- locations queues tasks create projects (request)
Fields
response_view: Option<String>
The response_view specifies which subset of the Task will be returned.
By default response_view is BASIC; not all information is retrieved by default because some data, such as payloads, might be desirable to return only when needed because of its large size or because of the sensitivity of data that it contains.
Authorization for FULL requires
cloudtasks.tasks.fullView
Google IAM
permission on the Task resource.
task: Option<Task>
Required.
The task to add.
Task names have the following format:
projects/PROJECT_ID/locations/LOCATION_ID/queues/QUEUE_ID/tasks/TASK_ID
.
The user can optionally specify a task name. If a
name is not specified then the system will generate a random
unique task id, which will be set in the task returned in the
response.
If schedule_time is not set or is in the past then Cloud Tasks will set it to the current time.
Task De-duplication:
Explicitly specifying a task ID enables task de-duplication. If a task's ID is identical to that of an existing task or a task that was deleted or completed recently then the call will fail with ALREADY_EXISTS. If the task's queue was created using Cloud Tasks, then another task with the same name can't be created for ~1hour after the original task was deleted or completed. If the task's queue was created using queue.yaml or queue.xml, then another task with the same name can't be created for ~9days after the original task was deleted or completed.
Because there is an extra lookup cost to identify duplicate task names, these CreateTask calls have significantly increased latency. Using hashed strings for the task id or for the prefix of the task id is recommended. Choosing task ids that are sequential or have sequential prefixes, for example using a timestamp, causes an increase in latency and error rates in all task commands. The infrastructure relies on an approximately uniform distribution of task ids to store and serve tasks efficiently.
Trait Implementations
impl Default for CreateTaskRequest
[src]
impl Default for CreateTaskRequest
fn default() -> CreateTaskRequest
[src]
fn default() -> CreateTaskRequest
Returns the "default value" for a type. Read more
impl Clone for CreateTaskRequest
[src]
impl Clone for CreateTaskRequest
fn clone(&self) -> CreateTaskRequest
[src]
fn clone(&self) -> CreateTaskRequest
Returns a copy of the value. Read more
fn clone_from(&mut self, source: &Self)
1.0.0[src]
fn clone_from(&mut self, source: &Self)
Performs copy-assignment from source
. Read more
impl Debug for CreateTaskRequest
[src]
impl Debug for CreateTaskRequest
fn fmt(&self, f: &mut Formatter) -> Result
[src]
fn fmt(&self, f: &mut Formatter) -> Result
Formats the value using the given formatter. Read more
impl RequestValue for CreateTaskRequest
[src]
impl RequestValue for CreateTaskRequest
Auto Trait Implementations
impl Send for CreateTaskRequest
impl Send for CreateTaskRequest
impl Sync for CreateTaskRequest
impl Sync for CreateTaskRequest