responseView = $responseView; } /** * @return self::RESPONSE_VIEW_* */ public function getResponseView() { return $this->responseView; } /** * Required. The task to add. Task names have the following format: * `projects/PROJECT_ID/locations/LOCATION_ID/queues/QUEUE_ID/tasks/TASK_ID`. * The user can optionally specify a task name. If a name is not specified * then the system will generate a random unique task id, which will be set in * the task returned in the response. If schedule_time is not set or is in the * past then Cloud Tasks will set it to the current time. Task De-duplication: * Explicitly specifying a task ID enables task de-duplication. If a task's ID * is identical to that of an existing task or a task that was deleted or * executed recently then the call will fail with ALREADY_EXISTS. The IDs of * deleted tasks are not immediately available for reuse. It can take up to 24 * hours (or 9 days if the task's queue was created using a queue.yaml or * queue.xml) for the task ID to be released and made available again. Because * there is an extra lookup cost to identify duplicate task names, these * CreateTask calls have significantly increased latency. Using hashed strings * for the task id or for the prefix of the task id is recommended. Choosing * task ids that are sequential or have sequential prefixes, for example using * a timestamp, causes an increase in latency and error rates in all task * commands. The infrastructure relies on an approximately uniform * distribution of task ids to store and serve tasks efficiently. * * @param Task $task */ public function setTask(Task $task) { $this->task = $task; } /** * @return Task */ public function getTask() { return $this->task; } } // Adding a class alias for backwards compatibility with the previous class name. class_alias(CreateTaskRequest::class, 'Google_Service_CloudTasks_CreateTaskRequest');