gcloud alpha apigee archives list - list Apigee archive deployments
gcloud alpha apigee archives list (--environment=ENVIRONMENT : --organization=ORGANIZATION) [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...]
(ALPHA) List Apigee archive deployments.
To list all archive deployments, in an environment called my-env, for the active Cloud Platform project, run:
$ gcloud alpha apigee archives list --environment=my-env
To list all archive deployments, for an environment named my-env, in an organization called my-org, run:
$ gcloud alpha apigee archives list --environment=my-env \ --organization=my-org
To list all archive deployments formatted as a JSON array, run:
$ gcloud alpha apigee archives list --environment=my-env \ --format=json
- Environment resource - Apigee environment whose archive deployments should be
listed. The arguments in this group can be used to specify the attributes of this resource.
This must be specified.
- --environment=ENVIRONMENT
ID of the environment or fully qualified identifier for the environment. To set the environment attribute:
provide the argument --environment on the command line.
This flag argument must be specified if any of the other arguments in this group are specified.
- --organization=ORGANIZATION
Apigee organization containing the environment. If unspecified, the Cloud Platform project's associated organization will be used. To set the organization attribute:
provide the argument --environment on the command line with a fully specified name;
provide the argument --organization on the command line;
set the property [project] or provide the argument [--project] on the command line, using a Cloud Platform project with an associated Apigee organization.
- --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.
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.
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 apigee archives list