- gcloud alpha tasks create-app-engine-task - create and add a task to an App Engine queue
gcloud alpha tasks create-app-engine-task [TASK_ID] --queue=QUEUE [--header=HEADER_FIELD: HEADER_VALUE] [--method=METHOD] [--routing=KEY:VALUE,[...]] [--schedule-time=SCHEDULE_TIME] [--url=URL] [--payload-content=PAYLOAD_CONTENT | --payload-file=PAYLOAD_FILE] [GCLOUD_WIDE_FLAG ...]
(ALPHA) Create and add a task to an App Engine queue.
- The task to create.
If not specified then the system will generate a random unique task ID. 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.
Because there is an extra lookup cost to identify duplicate task names, tasks created with IDs have significantly increased latency. Using hashed strings for the task ID or for the prefix of the task ID is recommended.
- The task to create.
The queue the task belongs to.
- --header=HEADER_FIELD: HEADER_VALUE
An HTTP request header. Header values can contain commas. This flag can be
repeated. Repeated header fields will have their values overridden.
The HTTP method to use for the request. If not specified, "POST" will be used.
The route to be used for this task. KEY must be at least one of: [service,
version, instance]. Any missing keys will use the default.
Routing can be overridden by the queue-level --routing-override flag.
The time when the task is scheduled to be first attempted. Defaults to "now" if
The relative URL of the request. Must begin with "/" and must be a valid HTTP
relative URL. It can contain a path and query string arguments. If not
specified, then the root path "/" will be used.
At most one of these may be specified:
Data payload used by the task worker to process the task.
File containing data payload used by the task worker to process the task.
GCLOUD WIDE FLAGS
These flags are available to all commands: --account, --configuration, --flags-file, --flatten, --format, --help, --log-http, --project, --quiet, --trace-token, --user-output-enabled, --verbosity. Run $ gcloud help for details.
This command is currently in ALPHA and may change without notice. If this command fails with API permission errors despite specifying the right project, you will have to apply for early access and have your projects registered on the API whitelist to use it. To do so, contact Support at cloud.google.com/support This variant is also available:
- $ gcloud beta tasks create-app-engine-task