mirror of
https://github.com/imjasonh/gcloud-help
synced 2026-07-08 18:45:13 +00:00
86 lines
3.6 KiB
Text
86 lines
3.6 KiB
Text
NAME
|
|
gcloud alpha apigee developers list - list Apigee developers by email
|
|
address
|
|
|
|
SYNOPSIS
|
|
gcloud alpha apigee developers list [--organization=ORGANIZATION]
|
|
[--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE]
|
|
[--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...]
|
|
|
|
DESCRIPTION
|
|
(ALPHA) List Apigee developers by email address.
|
|
|
|
EXAMPLES
|
|
To list all developers for the active Cloud Platform project, run:
|
|
|
|
$ gcloud alpha apigee developers list
|
|
|
|
To list all developers in an Apigee organization called my-org, formatted
|
|
as JSON objects, run:
|
|
|
|
$ gcloud alpha apigee developers list --organization=my-org \
|
|
--format=json
|
|
|
|
FLAGS
|
|
Organization resource - Apigee organization whose developers should be
|
|
listed. If unspecified, the Cloud Platform project's associated
|
|
organization will be used. This represents a Cloud resource.
|
|
|
|
--organization=ORGANIZATION
|
|
ID of the organization or fully qualified identifier for the
|
|
organization. To set the organization attribute:
|
|
▸ 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.
|
|
|
|
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. These variants are also available:
|
|
|
|
$ gcloud apigee developers list
|
|
|
|
$ gcloud beta apigee developers list
|
|
|