The cloudtasks2-beta3 command-line interface (CLI) allows to use most features of the Google Cloud Tasks service from the comfort of your terminal.

By default all output is printed to standard out, but flags can be set to direct it into a file independent of your shell's capabilities. Errors will be printed to standard error, and cause the program's exit code to be non-zero.

If data-structures are requested, these will be returned as pretty-printed JSON, to be useful as input to other tools.

Everything else about the Cloud Tasks API can be found at the official documentation site.

Installation and Source Code

Install the command-line interface with cargo using:

cargo install google-cloudtasks2_beta3-cli

Find the source code on github.


This documentation was generated from the Cloud Tasks API at revision 20240223. The CLI is at version 5.0.4.

cloudtasks2-beta3 [options]
                locations-get <name> [-p <v>]... [-o <out>]
                locations-get-cmek-config <name> [-p <v>]... [-o <out>]
                locations-list <name> [-p <v>]... [-o <out>]
                locations-queues-create <parent> (-r <kv>)... [-p <v>]... [-o <out>]
                locations-queues-delete <name> [-p <v>]... [-o <out>]
                locations-queues-get <name> [-p <v>]... [-o <out>]
                locations-queues-get-iam-policy <resource> (-r <kv>)... [-p <v>]... [-o <out>]
                locations-queues-list <parent> [-p <v>]... [-o <out>]
                locations-queues-patch <name> (-r <kv>)... [-p <v>]... [-o <out>]
                locations-queues-pause <name> (-r <kv>)... [-p <v>]... [-o <out>]
                locations-queues-purge <name> (-r <kv>)... [-p <v>]... [-o <out>]
                locations-queues-resume <name> (-r <kv>)... [-p <v>]... [-o <out>]
                locations-queues-set-iam-policy <resource> (-r <kv>)... [-p <v>]... [-o <out>]
                locations-queues-tasks-buffer <queue> <task-id> (-r <kv>)... [-p <v>]... [-o <out>]
                locations-queues-tasks-create <parent> (-r <kv>)... [-p <v>]... [-o <out>]
                locations-queues-tasks-delete <name> [-p <v>]... [-o <out>]
                locations-queues-tasks-get <name> [-p <v>]... [-o <out>]
                locations-queues-tasks-list <parent> [-p <v>]... [-o <out>]
                locations-queues-tasks-run <name> (-r <kv>)... [-p <v>]... [-o <out>]
                locations-queues-test-iam-permissions <resource> (-r <kv>)... [-p <v>]... [-o <out>]
                locations-update-cmek-config <name> (-r <kv>)... [-p <v>]... [-o <out>]
  cloudtasks2-beta3 --help

  [--scope <url>]...
            Specify the authentication a method should be executed in. Each scope
            requires the user to grant this application permission to use it.
            If unset, it defaults to the shortest scope url for a particular method.
  --config-dir <folder>
            A directory into which we will store our persistent data. Defaults to
            a user-writable directory that we will create during the first invocation.
            [default: ~/.google-service-cli]


The program will store all persistent data in the ~/.google-service-cli directory in JSON files prefixed with cloudtasks2-beta3-. You can change the directory used to store configuration with the --config-dir flag on a per-invocation basis.

More information about the various kinds of persistent data are given in the following paragraphs.


Most APIs require a user to authenticate any request. If this is the case, the scope determines the set of permissions granted. The granularity of these is usually no more than read-only or full-access.

If not set, the system will automatically select the smallest feasible scope, e.g. when invoking a method that is read-only, it will ask only for a read-only scope. You may use the --scope flag to specify a scope directly. All applicable scopes are documented in the respective method's CLI documentation.

The first time a scope is used, the user is asked for permission. Follow the instructions given by the CLI to grant permissions, or to decline.

If a scope was authenticated by the user, the respective information will be stored as JSON in the configuration directory, e.g. ~/.google-service-cli/cloudtasks2-beta3-token-<scope-hash>.json. No manual management of these tokens is necessary.

To revoke granted authentication, please refer to the official documentation.

Application Secrets

In order to allow any application to use Google services, it will need to be registered using the Google Developer Console. APIs the application may use are then enabled for it one by one. Most APIs can be used for free and have a daily quota.

To allow more comfortable usage of the CLI without forcing anyone to register an own application, the CLI comes with a default application secret that is configured accordingly. This also means that heavy usage all around the world may deplete the daily quota.

You can workaround this limitation by putting your own secrets file at this location: ~/.google-service-cli/cloudtasks2-beta3-secret.json, assuming that the required cloudtasks API was enabled for it. Such a secret file can be downloaded in the Google Developer Console at APIs & auth -> Credentials -> Download JSON and used as is.

Learn more about how to setup Google projects and enable APIs using the official documentation.


Even though the CLI does its best to provide usable error messages, sometimes it might be desirable to know what exactly led to a particular issue. This is done by allowing all client-server communication to be output to standard error as-is.

The --debug flag will print errors using the Debug representation to standard error.

You may consider redirecting standard error into a file for ease of use, e.g. cloudtasks2-beta3 --debug <resource> <method> [options] 2>debug.txt.