.TH "GCLOUD_TASKS_CREATE\-APP\-ENGINE\-TASK" 1



.SH "NAME"
.HP
gcloud tasks create\-app\-engine\-task \- create and add a task that targets App Engine



.SH "SYNOPSIS"
.HP
\f5gcloud tasks create\-app\-engine\-task\fR [\fITASK_ID\fR] \fB\-\-queue\fR=\fIQUEUE\fR [\fB\-\-header\fR=\fIHEADER_FIELD\fR:\ \fIHEADER_VALUE\fR] [\fB\-\-location\fR=\fILOCATION\fR] [\fB\-\-method\fR=\fIMETHOD\fR] [\fB\-\-relative\-uri\fR=\fIRELATIVE_URI\fR] [\fB\-\-routing\fR=\fIKEY\fR:\fIVALUE\fR,[...]] [\fB\-\-schedule\-time\fR=\fISCHEDULE_TIME\fR] [\fB\-\-body\-content\fR=\fIBODY_CONTENT\fR\ |\ \fB\-\-body\-file\fR=\fIBODY_FILE\fR] [\fIGCLOUD_WIDE_FLAG\ ...\fR]



.SH "DESCRIPTION"

Create and add a task that targets App Engine.



.SH "EXAMPLES"

To create a task:

.RS 2m
$ gcloud tasks create\-app\-engine\-task \-\-queue=my\-queue \e
  \-\-relative\-uri=/handler\-path my\-task
.RE



.SH "POSITIONAL ARGUMENTS"

.RS 2m
.TP 2m
[\fITASK_ID\fR]

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.


.RE
.sp

.SH "REQUIRED FLAGS"

.RS 2m
.TP 2m
\fB\-\-queue\fR=\fIQUEUE\fR

The queue the task belongs to.


.RE
.sp

.SH "OPTIONAL FLAGS"

.RS 2m
.TP 2m
\fB\-\-header\fR=\fIHEADER_FIELD\fR: \fIHEADER_VALUE\fR

An HTTP request header. Header values can contain commas. This flag can be
repeated. Repeated header fields will have their values overridden.

.TP 2m
\fB\-\-location\fR=\fILOCATION\fR

The location where we want to manage the queue or task. If not specified, uses
the location of the current project's App Engine app if there is an associated
app.

.TP 2m
\fB\-\-method\fR=\fIMETHOD\fR

The HTTP method to use for the request. If not specified, "POST" will be used.

.TP 2m
\fB\-\-relative\-uri\fR=\fIRELATIVE_URI\fR

The relative URI of the request. Must begin with "/" and must be a valid HTTP
relative URI. It can contain a path and query string arguments. If not
specified, then the root path "/" will be used.

.TP 2m
\fB\-\-routing\fR=\fIKEY\fR:\fIVALUE\fR,[...]

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 \f5\-\-routing\-override\fR flag.

.TP 2m
\fB\-\-schedule\-time\fR=\fISCHEDULE_TIME\fR

The time when the task is scheduled to be first attempted. Defaults to "now" if
not specified.

.TP 2m

At most one of these can be specified:


.RS 2m
.TP 2m
\fB\-\-body\-content\fR=\fIBODY_CONTENT\fR

HTTP Body data sent to the task worker processing the task.

.TP 2m
\fB\-\-body\-file\fR=\fIBODY_FILE\fR

File containing HTTP body data sent to the task worker processing the task.


.RE
.RE
.sp

.SH "GCLOUD WIDE FLAGS"

These flags are available to all commands: \-\-access\-token\-file, \-\-account,
\-\-billing\-project, \-\-configuration, \-\-flags\-file, \-\-flatten,
\-\-format, \-\-help, \-\-impersonate\-service\-account, \-\-log\-http,
\-\-project, \-\-quiet, \-\-trace\-token, \-\-user\-output\-enabled,
\-\-verbosity.

Run \fB$ gcloud help\fR for details.



.SH "NOTES"

These variants are also available:

.RS 2m
$ gcloud alpha tasks create\-app\-engine\-task
.RE

.RS 2m
$ gcloud beta tasks create\-app\-engine\-task
.RE