1
0
Fork 0
mirror of https://github.com/imjasonh/gcloud-help synced 2026-07-13 16:37:00 +00:00
gcloud-help/gcloud/beta/app-lifecycle-manager/flags/revisions/list
2026-05-13 13:12:23 +00:00

112 lines
4.5 KiB
Text

NAME
gcloud beta app-lifecycle-manager flags revisions list - list Flag
Revisions
SYNOPSIS
gcloud beta app-lifecycle-manager flags revisions list
[--location=LOCATION] [--filter=EXPRESSION] [--limit=LIMIT]
[--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri]
[GCLOUD_WIDE_FLAG ...]
DESCRIPTION
(BETA) List all flag revisions available in a specific location. Flag
revisions are immutable, point-in-time snapshots of a flag's configuration.
Use this command to audit configuration history, verify revision creation
success, or identify specific revision IDs for manual recovery or inclusion
in a Flag Release.
EXAMPLES
To list all flag revisions across all locations in the current project,
run:
$ gcloud beta app-lifecycle-manager flags revisions list
To list all flag revisions in the global location, run:
$ gcloud beta app-lifecycle-manager flags revisions list \
--location=global
To list revisions specifically for a flag named my-flag, run:
$ gcloud beta app-lifecycle-manager flags revisions list \
--location=global --filter="flag:my-flag"
To list the 5 most recent revisions to identify the latest configuration
state, run:
$ gcloud beta app-lifecycle-manager flags revisions list \
--location=global --limit=5 --sort-by=~createTime
To list revisions and output in JSON format for automation/scripting, run:
$ gcloud beta app-lifecycle-manager flags revisions list \
--format=json
FLAGS
Location resource - Location in which to list Flag Revisions. 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 --location on the command line with a fully
specified name;
◆ if left empty, will use the wildcard '-' to list all locations with a
fully specified name;
◆ provide the argument --project on the command line;
◆ set the property core/project.
--location=LOCATION
ID of the location or fully qualified identifier for the location.
To set the location attribute:
◆ provide the argument --location on the command line;
◆ if left empty, will use the wildcard '-' to list all locations.
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.
API REFERENCE
This command uses the saasservicemgmt/v1beta1 API. The full documentation
for this API can be found at: https://cloud.google.com/saas-runtime/docs
NOTES
This command is currently in beta and might change without notice.