2022-03-01 04:29:52 +00:00
|
|
|
NAME
|
|
|
|
|
gcloud api-gateway api-configs list - list configs for an API
|
|
|
|
|
|
|
|
|
|
SYNOPSIS
|
|
|
|
|
gcloud api-gateway api-configs list [--api=API] [--filter=EXPRESSION]
|
|
|
|
|
[--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]]
|
|
|
|
|
[GCLOUD_WIDE_FLAG ...]
|
|
|
|
|
|
|
|
|
|
DESCRIPTION
|
|
|
|
|
List configs for an API.
|
|
|
|
|
|
|
|
|
|
EXAMPLES
|
|
|
|
|
To list all API configs, run:
|
|
|
|
|
|
|
|
|
|
$ gcloud api-gateway api-configs list
|
|
|
|
|
|
|
|
|
|
FLAGS
|
|
|
|
|
Api resource - Name for API which api configs will be listed from. This
|
|
|
|
|
represents a Cloud resource. (NOTE) Some attributes are not given
|
2023-05-04 10:43:54 +00:00
|
|
|
arguments in this group but can be set in other ways.
|
|
|
|
|
|
|
|
|
|
To set the project attribute:
|
2022-03-01 04:29:52 +00:00
|
|
|
◆ provide the argument --api on the command line with a fully specified
|
|
|
|
|
name;
|
|
|
|
|
◆ Defaults to wildcard for all APIs with a fully specified name;
|
|
|
|
|
◆ provide the argument --project on the command line;
|
2023-05-04 10:43:54 +00:00
|
|
|
◆ set the property core/project.
|
|
|
|
|
|
|
|
|
|
To set the location attribute:
|
2022-03-01 04:29:52 +00:00
|
|
|
◆ provide the argument --api on the command line with a fully specified
|
|
|
|
|
name;
|
|
|
|
|
◆ Defaults to wildcard for all APIs with a fully specified name;
|
|
|
|
|
◆ Location for API and API Configs. Defaults to global.
|
|
|
|
|
|
|
|
|
|
--api=API
|
2023-05-04 10:43:54 +00:00
|
|
|
ID of the api or fully qualified identifier for the api.
|
|
|
|
|
|
|
|
|
|
To set the api attribute:
|
2022-03-01 04:29:52 +00:00
|
|
|
▸ provide the argument --api on the command line;
|
|
|
|
|
▸ Defaults to wildcard for all APIs.
|
|
|
|
|
|
|
|
|
|
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.
|
|
|
|
|
|
|
|
|
|
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
|
|
|
|
|
These variants are also available:
|
|
|
|
|
|
|
|
|
|
$ gcloud alpha api-gateway api-configs list
|
|
|
|
|
|
|
|
|
|
$ gcloud beta api-gateway api-configs list
|
|
|
|
|
|
