mirror of
https://github.com/imjasonh/gcloud-help
synced 2026-07-17 06:11:59 +00:00
gcloud: Wed Apr 26 10:24:37 UTC 2023
This commit is contained in:
parent
b33a8a3e6e
commit
2ae1bc2b12
276 changed files with 6093 additions and 833 deletions
42
gcloud/alpha/tasks/buffer
Normal file
42
gcloud/alpha/tasks/buffer
Normal file
|
|
@ -0,0 +1,42 @@
|
|||
NAME
|
||||
gcloud alpha tasks buffer - buffers a task into a queue
|
||||
|
||||
SYNOPSIS
|
||||
gcloud alpha tasks buffer --location=LOCATION --queue=QUEUE
|
||||
[--task-id=TASK_ID] [GCLOUD_WIDE_FLAG ...]
|
||||
|
||||
DESCRIPTION
|
||||
(ALPHA) Buffers a task into a queue.
|
||||
|
||||
EXAMPLES
|
||||
To buffer into a queue:
|
||||
|
||||
$ gcloud alpha tasks buffer --queue=my-queue --location=us-central1
|
||||
|
||||
REQUIRED FLAGS
|
||||
--location=LOCATION
|
||||
The location where the queue exists.
|
||||
|
||||
--queue=QUEUE
|
||||
The queue the task belongs to.
|
||||
|
||||
OPTIONAL FLAGS
|
||||
--task-id=TASK_ID
|
||||
The task ID for the task being created.
|
||||
|
||||
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 alpha and might change without notice. If this
|
||||
command fails with API permission errors despite specifying the correct
|
||||
project, you might be trying to access an API with an invitation-only early
|
||||
access allowlist. This variant is also available:
|
||||
|
||||
$ gcloud beta tasks buffer
|
||||
|
||||
|
|
@ -27,6 +27,9 @@ COMMANDS
|
|||
acknowledge
|
||||
(ALPHA) Acknowledge the lease on a task in a pull queue.
|
||||
|
||||
buffer
|
||||
(ALPHA) Buffers a task into a queue.
|
||||
|
||||
cancel-lease
|
||||
(ALPHA) Cancel the lease on a task in a pull queue.
|
||||
|
||||
|
|
|
|||
|
|
@ -33,7 +33,7 @@ POSITIONAL ARGUMENTS
|
|||
|
||||
FLAGS
|
||||
--http-header-override=HEADER_FIELD: HEADER_VALUE
|
||||
If provided, the specified HTTP headers overrides the existing headers
|
||||
If provided, the specified HTTP headers override the existing headers
|
||||
for all tasks in the queue. If a task has a header with the same Key as
|
||||
a queue-level header override, then the value of the task header will
|
||||
be overriden with the value of the queue-level header. Otherwise, the
|
||||
|
|
|
|||
|
|
@ -59,10 +59,10 @@ FLAGS
|
|||
Clear the field corresponding to --http-header-override.
|
||||
|
||||
--http-header-override=HEADER_FIELD: HEADER_VALUE
|
||||
If provided, the specified HTTP headers overrides the existing
|
||||
headers for all tasks in the queue. If a task has a header with the
|
||||
same Key as a queue-level header override, then the value of the task
|
||||
header will be overriden with the value of the queue-level header.
|
||||
If provided, the specified HTTP headers override the existing headers
|
||||
for all tasks in the queue. If a task has a header with the same Key
|
||||
as a queue-level header override, then the value of the task header
|
||||
will be overriden with the value of the queue-level header.
|
||||
Otherwise, the queue-level header will be added to the task headers.
|
||||
Header values can contain commas. This flag can be repeated. Repeated
|
||||
header fields will have their values overridden.
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue