gcloud beta apigee applications list - list Apigee applications
gcloud beta apigee applications list [--developer=DEVELOPER --organization=ORGANIZATION] [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...]
(BETA) List Apigee applications.
To list all Apigee applications in the active Cloud Platform project, run:
$ gcloud beta apigee applications list
To list all Apigee applications belonging to the developer horse@example.com in an Apigee organization called my-org, formatted as JSON, run:
$ gcloud beta apigee applications list \ --developer=horse@example.com --organization=my-org \ --format=json
- Developer resource - Apigee organization, and optionally developer, whose
applications should be listed. If developer is not specified, all developers will be listed.
To get a list of valid developers, run:
$ gcloud beta apigee developers list
The arguments in this group can be used to specify the attributes of this resource.
- --developer=DEVELOPER
ID of the developer or fully qualified identifier for the developer. To set the developer attribute:
provide the argument --developer on the command line;
leave the argument unspecified for it to be chosen automatically.
- --organization=ORGANIZATION
Apigee organization containing the developer. If unspecified, the Cloud Platform project's associated organization will be used. To set the organization attribute:
provide the argument --developer on the command line with a fully specified name;
leave the argument unspecified for it to be chosen automatically 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 beta and might change without notice. These variants are also available:
$ gcloud apigee applications list
$ gcloud alpha apigee applications list