--account <ACCOUNT> | Google Cloud Platform user account to use for invocation. Overrides the default *core/account* property value for this command invocation |
--billing-project <BILLING_PROJECT> | The Google Cloud Platform project that will be charged quota for operations performed in gcloud. If you need to operate on one project, but need quota against a different project, you can use this flag to specify the billing project. If both `billing/quota_project` and `--billing-project` are specified, `--billing-project` takes precedence. Run `$ gcloud config set --help` to see more information about `billing/quota_project` |
--clear-log-sampling-ratio | Clear the field corresponding to `--log-sampling-ratio` |
--clear-max-attempts | Clear the field corresponding to `--max-attempts` |
--clear-max-backoff | Clear the field corresponding to `--max-backoff` |
--clear-max-concurrent-dispatches | Clear the field corresponding to `--max-concurrent-dispatches` |
--clear-max-dispatches-per-second | Clear the field corresponding to `--max-dispatches-per-second` |
--clear-max-doublings | Clear the field corresponding to `--max-doublings` |
--clear-max-retry-duration | Clear the field corresponding to `--max-retry-duration` |
--clear-min-backoff | Clear the field corresponding to `--min-backoff` |
--clear-routing-override | Clear the field corresponding to `--routing-override` |
--configuration <CONFIGURATION> | The configuration to use for this command invocation. For more
information on how to use configurations, run:
`gcloud topic configurations`. You can also use the CLOUDSDK_ACTIVE_CONFIG_NAME environment
variable to set the equivalent of this flag for a terminal
session |
--flags-file <YAML_FILE> | A YAML or JSON file that specifies a *--flag*:*value* dictionary.
Useful for specifying complex flag values with special characters
that work with any command interpreter. Additionally, each
*--flags-file* arg is replaced by its constituent flags. See
$ gcloud topic flags-file for more information |
--flatten <KEY> | Flatten _name_[] output resource slices in _KEY_ into separate records
for each item in each slice. Multiple keys and slices may be specified.
This also flattens keys for *--format* and *--filter*. For example,
*--flatten=abc.def* flattens *abc.def[].ghi* references to
*abc.def.ghi*. A resource record containing *abc.def[]* with N elements
will expand to N records in the flattened output. This flag interacts
with other flags that are applied in this order: *--flatten*,
*--sort-by*, *--filter*, *--limit* |
--format <FORMAT> | Set the format for printing command output resources. The default is a
command-specific human-friendly output format. The supported formats
are: `config`, `csv`, `default`, `diff`, `disable`, `flattened`, `get`, `json`, `list`, `multi`, `none`, `object`, `table`, `text`, `value`, `yaml`. For more details run $ gcloud topic formats |
--help | Display detailed help |
--impersonate-service-account <SERVICE_ACCOUNT_EMAIL> | For this gcloud invocation, all API requests will be made as the given service account instead of the currently selected account. This is done without needing to create, download, and activate a key for the account. In order to perform operations as the service account, your currently selected account must have an IAM role that includes the iam.serviceAccounts.getAccessToken permission for the service account. The roles/iam.serviceAccountTokenCreator role has this permission or you may create a custom role. Overrides the default *auth/impersonate_service_account* property value for this command invocation |
--log-http | Log all HTTP server requests and responses to stderr. Overrides the default *core/log_http* property value for this command invocation |
--log-sampling-ratio <LOG_SAMPLING_RATIO> | Specifies the fraction of operations to write to Cloud Logging.
This field may contain any value between 0.0 and 1.0, inclusive. 0.0 is
the default and means that no operations are logged |
--max-attempts <MAX_ATTEMPTS> | The maximum number of attempts per task in the queue |
--max-backoff <MAX_BACKOFF> | The maximum amount of time to wait before retrying a task after it
fails. Must be a string that ends in 's', such as "5s" |
--max-concurrent-dispatches <MAX_CONCURRENT_DISPATCHES> | The maximum number of concurrent tasks that Cloud Tasks allows to
be dispatched for this queue. After this threshold has been reached,
Cloud Tasks stops dispatching tasks until the number of outstanding
requests decreases |
--max-dispatches-per-second <MAX_DISPATCHES_PER_SECOND> | The maximum rate at which tasks are dispatched from this queue |
--max-doublings <MAX_DOUBLINGS> | The time between retries will double maxDoublings times.
+
A tasks retry interval starts at minBackoff, then doubles maxDoublings
times, then increases linearly, and finally retries retries at
intervals of maxBackoff up to maxAttempts times.
+
For example, if minBackoff is 10s, maxBackoff is 300s, and
maxDoublings is 3, then the a task will first be retried in 10s. The
retry interval will double three times, and then increase linearly by
2^3 * 10s. Finally, the task will retry at intervals of maxBackoff
until the task has been attempted maxAttempts times. Thus, the
requests will retry at 10s, 20s, 40s, 80s, 160s, 240s, 300s, 300s |
--max-retry-duration <MAX_RETRY_DURATION> | The time limit for retrying a failed task, measured from when the task
was first run. Once the `--max-retry-duration` time has passed and the
task has been attempted --max-attempts times, no further attempts will
be made and the task will be deleted.
+
Must be a string that ends in 's', such as "5s" |
--min-backoff <MIN_BACKOFF> | The minimum amount of time to wait before retrying a task after it
fails. Must be a string that ends in 's', such as "5s" |
--project <PROJECT_ID> | The Google Cloud Platform project ID to use for this invocation. If
omitted, then the current project is assumed; the current project can
be listed using `gcloud config list --format='text(core.project)'`
and can be set using `gcloud config set project PROJECTID`.
+
`--project` and its fallback `core/project` property play two roles
in the invocation. It specifies the project of the resource to
operate on. It also specifies the project for API enablement check,
quota, and billing. To specify a different project for quota and
billing, use `--billing-project` or `billing/quota_project` property |
--quiet | Disable all interactive prompts when running gcloud commands. If input
is required, defaults will be used, or an error will be raised.
Overrides the default core/disable_prompts property value for this
command invocation. This is equivalent to setting the environment
variable `CLOUDSDK_CORE_DISABLE_PROMPTS` to 1 |
--routing-override <KEY:VALUE> | If provided, the specified route is used for all tasks in the queue,
no matter what is set is at the task-level.
+
KEY must be at least one of: [service, version, instance]. Any missing keys will use the
default |
--trace-token <TRACE_TOKEN> | Token used to route traces of service requests for investigation of issues. Overrides the default *core/trace_token* property value for this command invocation |
--user-output-enabled | Print user intended output to the console. Overrides the default *core/user_output_enabled* property value for this command invocation. Use *--no-user-output-enabled* to disable |
--verbosity <VERBOSITY> | Override the default verbosity for this command. Overrides the default *core/verbosity* property value for this command invocation. _VERBOSITY_ must be one of: *debug*, *info*, *warning*, *error*, *critical*, *none* |