mirror of
https://github.com/imjasonh/gcloud-help
synced 2026-07-08 10:35:03 +00:00
94 lines
3.3 KiB
Text
94 lines
3.3 KiB
Text
|
|
NAME
|
||
|
|
gcloud beta tasks create-app-engine-task - create and add a task that
|
||
|
|
targets App Engine
|
||
|
|
|
||
|
|
SYNOPSIS
|
||
|
|
gcloud beta tasks create-app-engine-task [TASK_ID] --queue=QUEUE
|
||
|
|
[--header=HEADER_FIELD: HEADER_VALUE] [--location=LOCATION]
|
||
|
|
[--method=METHOD] [--relative-uri=RELATIVE_URI]
|
||
|
|
[--routing=KEY:VALUE,[...]] [--schedule-time=SCHEDULE_TIME]
|
||
|
|
[--body-content=BODY_CONTENT | --body-file=BODY_FILE]
|
||
|
|
[GCLOUD_WIDE_FLAG ...]
|
||
|
|
|
||
|
|
DESCRIPTION
|
||
|
|
(BETA) Create and add a task that targets App Engine.
|
||
|
|
|
||
|
|
EXAMPLES
|
||
|
|
To create a task:
|
||
|
|
|
||
|
|
$ gcloud beta tasks create-app-engine-task --queue=my-queue \
|
||
|
|
--relative-uri=/handler-path my-task
|
||
|
|
|
||
|
|
POSITIONAL ARGUMENTS
|
||
|
|
[TASK_ID]
|
||
|
|
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.
|
||
|
|
|
||
|
|
REQUIRED FLAGS
|
||
|
|
--queue=QUEUE
|
||
|
|
The queue the task belongs to.
|
||
|
|
|
||
|
|
OPTIONAL FLAGS
|
||
|
|
--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.
|
||
|
|
|
||
|
|
--location=LOCATION
|
||
|
|
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.
|
||
|
|
|
||
|
|
--method=METHOD
|
||
|
|
The HTTP method to use for the request. If not specified, "POST" will
|
||
|
|
be used.
|
||
|
|
|
||
|
|
--relative-uri=RELATIVE_URI
|
||
|
|
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.
|
||
|
|
|
||
|
|
--routing=KEY:VALUE,[...]
|
||
|
|
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.
|
||
|
|
|
||
|
|
--schedule-time=SCHEDULE_TIME
|
||
|
|
The time when the task is scheduled to be first attempted. Defaults to
|
||
|
|
"now" if not specified.
|
||
|
|
|
||
|
|
At most one of these can be specified:
|
||
|
|
|
||
|
|
--body-content=BODY_CONTENT
|
||
|
|
HTTP Body data sent to the task worker processing the task.
|
||
|
|
|
||
|
|
--body-file=BODY_FILE
|
||
|
|
File containing HTTP body data sent to the task worker processing the
|
||
|
|
task.
|
||
|
|
|
||
|
|
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 $ gcloud help for details.
|
||
|
|
|
||
|
|
NOTES
|
||
|
|
This command is currently in beta and might change without notice. These
|
||
|
|
variants are also available:
|
||
|
|
|
||
|
|
$ gcloud tasks create-app-engine-task
|
||
|
|
|
||
|
|
$ gcloud alpha tasks create-app-engine-task
|
||
|
|
|