imjasonh/gcloud-help
1
0
Fork 0
mirror of https://github.com/imjasonh/gcloud-help synced 2026-07-18 14:56:05 +00:00
Code Activity

gcloud: Thu Jan 19 00:56:33 UTC 2023

Browse source
This commit is contained in:
Automated 2023-01-19 00:56:33 +00:00
parent 348d9760ee
commit 1248f773ec
1462 changed files with 51835 additions and 5402 deletions
Download patch file Download diff file Expand all files Collapse all files

9
gcloud/beta/run/services/help
View file

@ -2,7 +2,8 @@ NAME
gcloud beta run services - view and manage your Cloud Run services
SYNOPSIS
gcloud beta run services COMMAND [--platform=PLATFORM; default="managed"]
gcloud beta run services GROUP | COMMAND
[--platform=PLATFORM; default="managed"]
[--region=REGION
| --cluster=CLUSTER --cluster-location=CLUSTER_LOCATION
| --context=CONTEXT --kubeconfig=KUBECONFIG] [GCLOUD_WIDE_FLAG ...]
@ -99,6 +100,12 @@ GCLOUD WIDE FLAGS
Run $ gcloud help for details.
GROUPS
GROUP is one of the following:
logs
(BETA) Read logs for Cloud Run (fully managed) services.
COMMANDS
COMMAND is one of the following:

110
gcloud/beta/run/services/logs/help Normal file
View file

@ -0,0 +1,110 @@
NAME
gcloud beta run services logs - read logs for Cloud Run (fully managed)
services
SYNOPSIS
gcloud beta run services logs COMMAND
[--platform=PLATFORM; default="managed"]
[--region=REGION
| --cluster=CLUSTER --cluster-location=CLUSTER_LOCATION
| --context=CONTEXT --kubeconfig=KUBECONFIG] [GCLOUD_WIDE_FLAG ...]
DESCRIPTION
(BETA) Read logs for Cloud Run (fully managed) services.
FLAGS
--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.
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.
GCLOUD WIDE FLAGS
These flags are available to all commands: --help.
Run $ gcloud help for details.
COMMANDS
COMMAND is one of the following:
read
(BETA) Read logs for a service.
tail
(BETA) Tail logs for a service.
NOTES
This command is currently in beta and might change without notice. This
variant is also available:
$ gcloud alpha run services logs

158
gcloud/beta/run/services/logs/read Normal file
View file

@ -0,0 +1,158 @@
NAME
gcloud beta run services logs read - read logs for a service
SYNOPSIS
gcloud beta run services logs read SERVICE
[--freshness=FRESHNESS; default="1d"] [--log-filter=LOG_FILTER]
[--order=ORDER; default="desc"]
[--platform=PLATFORM; default="managed"]
[--region=REGION
| --cluster=CLUSTER --cluster-location=CLUSTER_LOCATION
| --context=CONTEXT --kubeconfig=KUBECONFIG] [--limit=LIMIT]
[GCLOUD_WIDE_FLAG ...]
DESCRIPTION
(BETA) gcloud beta run services logs read reads log entries. Log entries
matching --log-filter are returned according to the specified --order. If
the log entries come from multiple logs, then entries from different logs
might be intermingled in the results.
EXAMPLES
To read log entries from for a Cloud Run Service, run:
$ gcloud beta run services logs read my-service
To read log entries with severity ERROR or higher, run:
$ gcloud beta run services logs read my-service \
--log-filter="severity>=ERROR"
To read log entries written in a specific time window, run:
$ gcloud beta run services logs read my-service \
--log-filter='timestamp<="2015-05-31T23:59:59Z" AND
timestamp>="2015-05-31T00:00:00Z"'
To read up to 10 log entries in your service payloads that include the word
SearchText and format the output in JSON format, run:
$ gcloud beta run services logs read my-service \
--log-filter="textPayload:SearchText" --limit=10 --format=json
Detailed information about filters can be found at:
https://cloud.google.com/logging/docs/view/advanced_filters
POSITIONAL ARGUMENTS
SERVICE
Name for a Cloud Run service.
FLAGS
--freshness=FRESHNESS; default="1d"
Return entries that are not older than this value. Works only with DESC
ordering and filters without a timestamp. See $ gcloud topic datetimes
for information on duration formats.
--log-filter=LOG_FILTER
Filter expression that specifies the log entries to return. Detailed
information about filters can be found at:
https://cloud.google.com/logging/docs/view/logging-query-language
--order=ORDER; default="desc"
Ordering of returned log entries based on timestamp field. ORDER must
be one of: desc, asc.
--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.
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
--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.
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 beta and might change without notice. This
variant is also available:
$ gcloud alpha run services logs read

127
gcloud/beta/run/services/logs/tail Normal file
View file

@ -0,0 +1,127 @@
NAME
gcloud beta run services logs tail - tail logs for a service
SYNOPSIS
gcloud beta run services logs tail SERVICE [--log-filter=LOG_FILTER]
[--platform=PLATFORM; default="managed"]
[--region=REGION
| --cluster=CLUSTER --cluster-location=CLUSTER_LOCATION
| --context=CONTEXT --kubeconfig=KUBECONFIG] [GCLOUD_WIDE_FLAG ...]
DESCRIPTION
(BETA) gcloud beta run services logs tail tails log-entries for a
particular Cloud Run service in real time. The log entries are formatted
for consumption in a terminal.
EXAMPLES
To tail log entries for a Cloud Run Service, run:
$ gcloud beta run services logs tail my-service
To tail log entries with severity ERROR or higher, run:
$ gcloud beta run services logs tail my-service \
--log-filter="severity>=ERROR"
Detailed information about filters can be found at:
https://cloud.google.com/logging/docs/view/advanced_filters
POSITIONAL ARGUMENTS
SERVICE
Name for a Cloud Run service.
FLAGS
--log-filter=LOG_FILTER
Filter expression that specifies the log entries to return. Detailed
information about filters can be found at:
https://cloud.google.com/logging/docs/view/logging-query-language
--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.
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.
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 beta and might change without notice. This
variant is also available:
$ gcloud alpha run services logs tail

7
gcloud/beta/run/services/update
View file

@ -213,7 +213,7 @@ FLAGS
--[no-]cpu-boost
Whether to allocate extra CPU to containers on startup. This can
reduce the percieved latency of a cold start request. Use --cpu-boost
reduce the perceived latency of a cold start request. Use --cpu-boost
to enable and --no-cpu-boost to disable.
--[no-]cpu-throttling
@ -328,7 +328,10 @@ FLAGS
--env-vars-file=FILE_PATH
Path to a local YAML file with definitions for all environment
variables. All existing environment variables will be removed before
the new environment variables are added.
the new environment variables are added. Example YAML content:
KEY_1: "value1"
KEY_2: "value 2"
--set-env-vars=[KEY=VALUE,...]
List of key-value pairs to set as environment variables. All existing