gcloud alpha transfer appliances orders list

NAME
gcloud alpha transfer appliances orders list - list Transfer Appliance orders
SYNOPSIS
gcloud alpha transfer appliances orders list [--appliances=[APPLIANCES,…]] [--orders=[ORDERS,…]] [--region=REGION] [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,…]] [--uri] [GCLOUD_WIDE_FLAG]
DESCRIPTION
(ALPHA) List Transfer Appliances in a given project to show their state and corresponding orders.
EXAMPLES
To list all appliances in your current project, run:
gcloud alpha transfer appliances orders list

To list all information about all jobs formatted as JSON, run:

gcloud alpha transfer appliances orders list --format=json
FLAGS
Appliances resource - The appliances associated with the orders to list. This represents a Cloud resource. (NOTE) Some attributes are not given arguments in this group but can be set in other ways.

To set the project attribute:

  • provide the argument --appliances on the command line with a fully specified name;
  • provide the argument --project on the command line;
  • set the property core/project.

To set the region attribute:

  • provide the argument --appliances on the command line with a fully specified name;
  • provide the argument --region on the command line.
--appliances=[APPLIANCES,…]
IDs of the appliancess or fully qualified identifiers for the appliancess.

To set the appliances attribute:

  • provide the argument --appliances on the command line.
Orders resource - The orders to list. This represents a Cloud resource. (NOTE) Some attributes are not given arguments in this group but can be set in other ways.

To set the project attribute:

  • provide the argument --orders on the command line with a fully specified name;
  • provide the argument --project on the command line;
  • set the property core/project.

To set the region attribute:

  • provide the argument --orders on the command line with a fully specified name;
  • provide the argument --region on the command line.
--orders=[ORDERS,…]
IDs of the orderss or fully qualified identifiers for the orderss.

To set the orders attribute:

  • provide the argument --orders on the command line.
--region=REGION
The location affiliated with the appliance order to list. REGION must be one of: us-central1, europe-west1, asia-southeast1.
LIST COMMAND FLAGS
--filter=EXPRESSION
Apply a Boolean filter EXPRESSION to each resource item to be listed. If the expression evaluates True, then that item is listed. For more details and examples of filter expressions, run $ gcloud topic filters. This flag interacts with other flags that are applied in this order: --flatten, --sort-by, --filter, --limit.
--limit=LIMIT
Maximum number of resources to list. The default is unlimited. This flag interacts with other flags that are applied in this order: --flatten, --sort-by, --filter, --limit.
--page-size=PAGE_SIZE
Some services group resource list output into pages. This flag specifies the maximum number of resources per page. The default is determined by the service if it supports paging, otherwise it is unlimited (no paging). Paging may be applied before or after --filter and --limit depending on the service.
--sort-by=[FIELD,…]
Comma-separated list of resource field key names to sort by. The default order is ascending. Prefix a field with ``~´´ for descending order on that field. This flag interacts with other flags that are applied in this order: --flatten, --sort-by, --filter, --limit.
--uri
Print a list of resource URIs instead of the default output, and change the command output to a list of URIs. If this flag is used with --format, the formatting is applied on this URI list. To display URIs alongside other keys instead, use the uri() transform.
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.