1
0
Fork 0
mirror of https://github.com/imjasonh/gcloud-help synced 2026-07-08 10:35:03 +00:00
gcloud-help/gcloud/alpha/run/revisions/list
2022-03-01 04:29:52 +00:00

166 lines
7.3 KiB
Text

NAME
gcloud alpha run revisions list - list available revisions
SYNOPSIS
gcloud alpha run revisions list [--namespace=NAMESPACE]
[--platform=PLATFORM; default="managed"] [--service=SERVICE]
[--region=REGION
| --cluster=CLUSTER --cluster-location=CLUSTER_LOCATION
| --context=CONTEXT --kubeconfig=KUBECONFIG] [--filter=EXPRESSION]
[--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri]
[GCLOUD_WIDE_FLAG ...]
DESCRIPTION
(ALPHA) List available revisions.
EXAMPLES
To list all revisions for the provided service:
$ gcloud alpha run revisions list --service=foo
FLAGS
Only applicable if connecting to Cloud Run for Anthos deployed on Google
Cloud or Cloud Run for Anthos deployed on VMware. Specify --platform=gke
or --platform=kubernetes to use:
Namespace resource - Namespace to list revisions in. This represents a
Cloud resource.
--namespace=NAMESPACE
ID of the namespace or fully qualified identifier for the
namespace. To set the namespace attribute:
▫ provide the argument --namespace on the command line;
▫ set the property run/namespace;
▫ For Cloud Run on Kubernetes Engine, defaults to "default".
Otherwise, defaults to project ID.;
▫ provide the argument project on the command line;
▫ set the property core/project.
--platform=PLATFORM; default="managed"
Target platform for running commands. Alternatively, set the property
[run/platform]. PLATFORM must be one of:
managed
Fully managed version of Cloud Run. Use with the --region flag or
set the [run/region] property to specify a Cloud Run region.
gke
Cloud Run for Anthos on Google Cloud. Use with the --cluster and
--cluster-location flags or set the [run/cluster] and
[run/cluster_location] properties to specify a cluster in a given
zone.
kubernetes
Use a Knative-compatible kubernetes cluster. Use with the
--kubeconfig and --context flags to specify a kubeconfig file and
the context for connecting.
--service=SERVICE
Limit matched revisions to the given service.
Arguments to locate resources, depending on the platform used.
At most one of these can be specified:
Only applicable if connecting to Cloud Run (fully managed). Specify
--platform=managed to use:
--region=REGION
Region in which the resource can be found. Alternatively, set the
property [run/region].
Only applicable if connecting to Cloud Run for Anthos deployed on Google
Cloud. Specify --platform=gke to use:
Cluster resource - Kubernetes Engine cluster to connect to. The
arguments in this group can be used to specify the attributes of this
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 --cluster on the command line with a fully
specified name;
▫ set the property run/cluster with a fully specified name;
▫ specify the cluster from a list of available clusters with a
fully specified name;
▫ provide the argument --project on the command line;
▫ set the property core/project.
--cluster=CLUSTER
ID of the cluster or fully qualified identifier for the cluster.
To set the cluster attribute:
◇ provide the argument --cluster on the command line;
◇ set the property run/cluster;
◇ specify the cluster from a list of available clusters.
--cluster-location=CLUSTER_LOCATION
Zone in which the cluster is located. Alternatively, set the
property [run/cluster_location]. To set the location attribute:
◇ provide the argument --cluster on the command line with a
fully specified name;
◇ set the property run/cluster with a fully specified name;
◇ specify the cluster from a list of available clusters with a
fully specified name;
◇ provide the argument --cluster-location on the command line;
◇ set the property run/cluster_location;
◇ specify the cluster location from a list of available zones.
Only applicable if connecting to Cloud Run for Anthos deployed on
VMware. Specify --platform=kubernetes to use:
--context=CONTEXT
The name of the context in your kubectl config file to use for
connecting.
--kubeconfig=KUBECONFIG
The absolute path to your kubectl config file. If not specified,
the colon- or semicolon-delimited list of paths specified by
$KUBECONFIG will be used. If $KUBECONFIG is unset, this defaults to
~/.kube/config.
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 run revisions list
$ gcloud beta run revisions list