imjasonh/gcloud-help
1
0
Fork 0
mirror of https://github.com/imjasonh/gcloud-help synced 2026-07-16 20:36:39 +00:00
Code Activity

gcloud: Wed Dec 10 10:54:29 UTC 2025

Browse source
This commit is contained in:
Automated 2025-12-10 10:54:29 +00:00
parent 7b14250313
commit 6d07e70b12
313 changed files with 11521 additions and 1088 deletions
Download patch file Download diff file Expand all files Collapse all files

33
gcloud/beta/run/deploy
View file

@ -48,7 +48,7 @@ SYNOPSIS
--update-env-vars=[KEY=VALUE,...] --clear-secrets
| --set-secrets=[KEY=VALUE,...] | --remove-secrets=[KEY,...]
--update-secrets=[KEY=VALUE,...] --command=[COMMAND,...]
| --function=FUNCTION --image=IMAGE --source=SOURCE]
| --function=FUNCTION --no-build --image=IMAGE --source=SOURCE]
[--binary-authorization=POLICY | --clear-binary-authorization]
[--clear-encryption-key-shutdown-hours
| --encryption-key-shutdown-hours=ENCRYPTION_KEY_SHUTDOWN_HOURS]
@ -362,10 +362,11 @@ FLAGS
--add-volume=[KEY=VALUE,...]
Adds a volume to the Cloud Run resource. To add more than one volume,
specify this flag multiple times. Volumes must have a name and type
key. Only certain values are supported for type. Depending on the
provided type, other keys will be required. The following types are
supported with the specified additional keys:
specify this flag multiple times. Volumes must have a type key. Volumes
must have a name key if mount-path is not specified. A name key is
optional if mount-path is specified.Only certain values are supported
for type. Depending on the provided type, other keys will be required.
The following types are supported with the specified additional keys:
cloud-storage: A volume representing a Cloud Storage bucket. This
volume type is mounted using Cloud Storage FUSE. See
@ -378,11 +379,21 @@ FLAGS
◆ mount-options: (optional) A list of flags to pass to GCSFuse. Flags
should be specified without leading dashes and separated by
semicolons.
◆ mount-path: (optional) The path at which the volume should be
mounted. The mount-path parameter is only supported for single
container services which do not make use of the --container flag. For
multi-container services, specify the mount-path parameter under the
--add-volume-mount flag.
in-memory: An ephemeral volume that stores data in the instance's
memory. With this type of volume, data is not shared between instances
and all data will be lost when the instance it is on is terminated.
Additional keys:
◆ mount-path: (optional) The path at which the volume should be
mounted. The mount-path parameter is only supported for single
container services which do not make use of the --container flag. For
multi-container services, specify the mount-path parameter under the
--add-volume-mount flag.
◆ size-limit: (optional) A quantity representing the maximum amount
of memory allocated to this volume, such as "512Mi" or "3G". Data
stored in an in-memory volume consumes the memory allocation of the
@ -392,6 +403,11 @@ FLAGS
nfs: Represents a volume backed by an NFS server. Additional keys:
◆ location: (required) The location of the NFS Server, in the form
SERVER:/PATH
◆ mount-path: (optional) The path at which the volume should be
mounted. The mount-path parameter is only supported for single
container services which do not make use of the --container flag. For
multi-container services, specify the mount-path parameter under the
--add-volume-mount flag.
◆ readonly: (optional) A boolean. If true, this volume will be
read-only from all mounts.
@ -644,6 +660,13 @@ FLAGS
Specifies that the deployed object is a function. If a value is
provided, that value is used as the entrypoint.
--no-build
When set, the cloud build step will be skipped and the provided
source code will be extracted directly on the base image. Your
source code must contain all the dependencies for your application.
See https://cloud.google.com/run/docs/deploying-source-code for
more details.
--image=IMAGE
Name of the container image to deploy (e.g.
us-docker.pkg.dev/cloudrun/container/hello:latest). When used with

24
gcloud/beta/run/jobs/create
View file

@ -156,10 +156,11 @@ FLAGS
--add-volume=[KEY=VALUE,...]
Adds a volume to the Cloud Run resource. To add more than one volume,
specify this flag multiple times. Volumes must have a name and type
key. Only certain values are supported for type. Depending on the
provided type, other keys will be required. The following types are
supported with the specified additional keys:
specify this flag multiple times. Volumes must have a type key. Volumes
must have a name key if mount-path is not specified. A name key is
optional if mount-path is specified.Only certain values are supported
for type. Depending on the provided type, other keys will be required.
The following types are supported with the specified additional keys:
cloud-storage: A volume representing a Cloud Storage bucket. This
volume type is mounted using Cloud Storage FUSE. See
@ -172,11 +173,21 @@ FLAGS
◆ mount-options: (optional) A list of flags to pass to GCSFuse. Flags
should be specified without leading dashes and separated by
semicolons.
◆ mount-path: (optional) The path at which the volume should be
mounted. The mount-path parameter is only supported for single
container services which do not make use of the --container flag. For
multi-container services, specify the mount-path parameter under the
--add-volume-mount flag.
in-memory: An ephemeral volume that stores data in the instance's
memory. With this type of volume, data is not shared between instances
and all data will be lost when the instance it is on is terminated.
Additional keys:
◆ mount-path: (optional) The path at which the volume should be
mounted. The mount-path parameter is only supported for single
container services which do not make use of the --container flag. For
multi-container services, specify the mount-path parameter under the
--add-volume-mount flag.
◆ size-limit: (optional) A quantity representing the maximum amount
of memory allocated to this volume, such as "512Mi" or "3G". Data
stored in an in-memory volume consumes the memory allocation of the
@ -186,6 +197,11 @@ FLAGS
nfs: Represents a volume backed by an NFS server. Additional keys:
◆ location: (required) The location of the NFS Server, in the form
SERVER:/PATH
◆ mount-path: (optional) The path at which the volume should be
mounted. The mount-path parameter is only supported for single
container services which do not make use of the --container flag. For
multi-container services, specify the mount-path parameter under the
--add-volume-mount flag.
◆ readonly: (optional) A boolean. If true, this volume will be
read-only from all mounts.

24
gcloud/beta/run/jobs/deploy
View file

@ -161,10 +161,11 @@ FLAGS
--add-volume=[KEY=VALUE,...]
Adds a volume to the Cloud Run resource. To add more than one volume,
specify this flag multiple times. Volumes must have a name and type
key. Only certain values are supported for type. Depending on the
provided type, other keys will be required. The following types are
supported with the specified additional keys:
specify this flag multiple times. Volumes must have a type key. Volumes
must have a name key if mount-path is not specified. A name key is
optional if mount-path is specified.Only certain values are supported
for type. Depending on the provided type, other keys will be required.
The following types are supported with the specified additional keys:
cloud-storage: A volume representing a Cloud Storage bucket. This
volume type is mounted using Cloud Storage FUSE. See
@ -177,11 +178,21 @@ FLAGS
◆ mount-options: (optional) A list of flags to pass to GCSFuse. Flags
should be specified without leading dashes and separated by
semicolons.
◆ mount-path: (optional) The path at which the volume should be
mounted. The mount-path parameter is only supported for single
container services which do not make use of the --container flag. For
multi-container services, specify the mount-path parameter under the
--add-volume-mount flag.
in-memory: An ephemeral volume that stores data in the instance's
memory. With this type of volume, data is not shared between instances
and all data will be lost when the instance it is on is terminated.
Additional keys:
◆ mount-path: (optional) The path at which the volume should be
mounted. The mount-path parameter is only supported for single
container services which do not make use of the --container flag. For
multi-container services, specify the mount-path parameter under the
--add-volume-mount flag.
◆ size-limit: (optional) A quantity representing the maximum amount
of memory allocated to this volume, such as "512Mi" or "3G". Data
stored in an in-memory volume consumes the memory allocation of the
@ -191,6 +202,11 @@ FLAGS
nfs: Represents a volume backed by an NFS server. Additional keys:
◆ location: (required) The location of the NFS Server, in the form
SERVER:/PATH
◆ mount-path: (optional) The path at which the volume should be
mounted. The mount-path parameter is only supported for single
container services which do not make use of the --container flag. For
multi-container services, specify the mount-path parameter under the
--add-volume-mount flag.
◆ readonly: (optional) A boolean. If true, this volume will be
read-only from all mounts.

24
gcloud/beta/run/jobs/update
View file

@ -172,10 +172,11 @@ FLAGS
--add-volume=[KEY=VALUE,...]
Adds a volume to the Cloud Run resource. To add more than one volume,
specify this flag multiple times. Volumes must have a name and type
key. Only certain values are supported for type. Depending on the
provided type, other keys will be required. The following types are
supported with the specified additional keys:
specify this flag multiple times. Volumes must have a type key. Volumes
must have a name key if mount-path is not specified. A name key is
optional if mount-path is specified.Only certain values are supported
for type. Depending on the provided type, other keys will be required.
The following types are supported with the specified additional keys:
cloud-storage: A volume representing a Cloud Storage bucket. This
volume type is mounted using Cloud Storage FUSE. See
@ -188,11 +189,21 @@ FLAGS
◆ mount-options: (optional) A list of flags to pass to GCSFuse. Flags
should be specified without leading dashes and separated by
semicolons.
◆ mount-path: (optional) The path at which the volume should be
mounted. The mount-path parameter is only supported for single
container services which do not make use of the --container flag. For
multi-container services, specify the mount-path parameter under the
--add-volume-mount flag.
in-memory: An ephemeral volume that stores data in the instance's
memory. With this type of volume, data is not shared between instances
and all data will be lost when the instance it is on is terminated.
Additional keys:
◆ mount-path: (optional) The path at which the volume should be
mounted. The mount-path parameter is only supported for single
container services which do not make use of the --container flag. For
multi-container services, specify the mount-path parameter under the
--add-volume-mount flag.
◆ size-limit: (optional) A quantity representing the maximum amount
of memory allocated to this volume, such as "512Mi" or "3G". Data
stored in an in-memory volume consumes the memory allocation of the
@ -202,6 +213,11 @@ FLAGS
nfs: Represents a volume backed by an NFS server. Additional keys:
◆ location: (required) The location of the NFS Server, in the form
SERVER:/PATH
◆ mount-path: (optional) The path at which the volume should be
mounted. The mount-path parameter is only supported for single
container services which do not make use of the --container flag. For
multi-container services, specify the mount-path parameter under the
--add-volume-mount flag.
◆ readonly: (optional) A boolean. If true, this volume will be
read-only from all mounts.

9
gcloud/beta/run/multi-region-services/update
View file

@ -334,10 +334,11 @@ FLAGS
--add-volume=[KEY=VALUE,...]
Adds a volume to the Cloud Run resource. To add more than one volume,
specify this flag multiple times. Volumes must have a name and type
key. Only certain values are supported for type. Depending on the
provided type, other keys will be required. The following types are
supported with the specified additional keys:
specify this flag multiple times. Volumes must have a type key. Volumes
must have a name key if mount-path is not specified. A name key is
optional if mount-path is specified.Only certain values are supported
for type. Depending on the provided type, other keys will be required.
The following types are supported with the specified additional keys:
--clear-volumes
Remove all existing volumes from the Cloud Run resource, including

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

@ -332,10 +332,11 @@ FLAGS
--add-volume=[KEY=VALUE,...]
Adds a volume to the Cloud Run resource. To add more than one volume,
specify this flag multiple times. Volumes must have a name and type
key. Only certain values are supported for type. Depending on the
provided type, other keys will be required. The following types are
supported with the specified additional keys:
specify this flag multiple times. Volumes must have a type key. Volumes
must have a name key if mount-path is not specified. A name key is
optional if mount-path is specified.Only certain values are supported
for type. Depending on the provided type, other keys will be required.
The following types are supported with the specified additional keys:
cloud-storage: A volume representing a Cloud Storage bucket. This
volume type is mounted using Cloud Storage FUSE. See
@ -348,11 +349,21 @@ FLAGS
◆ mount-options: (optional) A list of flags to pass to GCSFuse. Flags
should be specified without leading dashes and separated by
semicolons.
◆ mount-path: (optional) The path at which the volume should be
mounted. The mount-path parameter is only supported for single
container services which do not make use of the --container flag. For
multi-container services, specify the mount-path parameter under the
--add-volume-mount flag.
in-memory: An ephemeral volume that stores data in the instance's
memory. With this type of volume, data is not shared between instances
and all data will be lost when the instance it is on is terminated.
Additional keys:
◆ mount-path: (optional) The path at which the volume should be
mounted. The mount-path parameter is only supported for single
container services which do not make use of the --container flag. For
multi-container services, specify the mount-path parameter under the
--add-volume-mount flag.
◆ size-limit: (optional) A quantity representing the maximum amount
of memory allocated to this volume, such as "512Mi" or "3G". Data
stored in an in-memory volume consumes the memory allocation of the
@ -362,6 +373,11 @@ FLAGS
nfs: Represents a volume backed by an NFS server. Additional keys:
◆ location: (required) The location of the NFS Server, in the form
SERVER:/PATH
◆ mount-path: (optional) The path at which the volume should be
mounted. The mount-path parameter is only supported for single
container services which do not make use of the --container flag. For
multi-container services, specify the mount-path parameter under the
--add-volume-mount flag.
◆ readonly: (optional) A boolean. If true, this volume will be
read-only from all mounts.

24
gcloud/beta/run/worker-pools/deploy
View file

@ -194,10 +194,11 @@ FLAGS
--add-volume=[KEY=VALUE,...]
Adds a volume to the Cloud Run resource. To add more than one volume,
specify this flag multiple times. Volumes must have a name and type
key. Only certain values are supported for type. Depending on the
provided type, other keys will be required. The following types are
supported with the specified additional keys:
specify this flag multiple times. Volumes must have a type key. Volumes
must have a name key if mount-path is not specified. A name key is
optional if mount-path is specified.Only certain values are supported
for type. Depending on the provided type, other keys will be required.
The following types are supported with the specified additional keys:
cloud-storage: A volume representing a Cloud Storage bucket. This
volume type is mounted using Cloud Storage FUSE. See
@ -210,11 +211,21 @@ FLAGS
◆ mount-options: (optional) A list of flags to pass to GCSFuse. Flags
should be specified without leading dashes and separated by
semicolons.
◆ mount-path: (optional) The path at which the volume should be
mounted. The mount-path parameter is only supported for single
container services which do not make use of the --container flag. For
multi-container services, specify the mount-path parameter under the
--add-volume-mount flag.
in-memory: An ephemeral volume that stores data in the instance's
memory. With this type of volume, data is not shared between instances
and all data will be lost when the instance it is on is terminated.
Additional keys:
◆ mount-path: (optional) The path at which the volume should be
mounted. The mount-path parameter is only supported for single
container services which do not make use of the --container flag. For
multi-container services, specify the mount-path parameter under the
--add-volume-mount flag.
◆ size-limit: (optional) A quantity representing the maximum amount
of memory allocated to this volume, such as "512Mi" or "3G". Data
stored in an in-memory volume consumes the memory allocation of the
@ -224,6 +235,11 @@ FLAGS
nfs: Represents a volume backed by an NFS server. Additional keys:
◆ location: (required) The location of the NFS Server, in the form
SERVER:/PATH
◆ mount-path: (optional) The path at which the volume should be
mounted. The mount-path parameter is only supported for single
container services which do not make use of the --container flag. For
multi-container services, specify the mount-path parameter under the
--add-volume-mount flag.
◆ readonly: (optional) A boolean. If true, this volume will be
read-only from all mounts.

24
gcloud/beta/run/worker-pools/update
View file

@ -190,10 +190,11 @@ FLAGS
--add-volume=[KEY=VALUE,...]
Adds a volume to the Cloud Run resource. To add more than one volume,
specify this flag multiple times. Volumes must have a name and type
key. Only certain values are supported for type. Depending on the
provided type, other keys will be required. The following types are
supported with the specified additional keys:
specify this flag multiple times. Volumes must have a type key. Volumes
must have a name key if mount-path is not specified. A name key is
optional if mount-path is specified.Only certain values are supported
for type. Depending on the provided type, other keys will be required.
The following types are supported with the specified additional keys:
cloud-storage: A volume representing a Cloud Storage bucket. This
volume type is mounted using Cloud Storage FUSE. See
@ -206,11 +207,21 @@ FLAGS
◆ mount-options: (optional) A list of flags to pass to GCSFuse. Flags
should be specified without leading dashes and separated by
semicolons.
◆ mount-path: (optional) The path at which the volume should be
mounted. The mount-path parameter is only supported for single
container services which do not make use of the --container flag. For
multi-container services, specify the mount-path parameter under the
--add-volume-mount flag.
in-memory: An ephemeral volume that stores data in the instance's
memory. With this type of volume, data is not shared between instances
and all data will be lost when the instance it is on is terminated.
Additional keys:
◆ mount-path: (optional) The path at which the volume should be
mounted. The mount-path parameter is only supported for single
container services which do not make use of the --container flag. For
multi-container services, specify the mount-path parameter under the
--add-volume-mount flag.
◆ size-limit: (optional) A quantity representing the maximum amount
of memory allocated to this volume, such as "512Mi" or "3G". Data
stored in an in-memory volume consumes the memory allocation of the
@ -220,6 +231,11 @@ FLAGS
nfs: Represents a volume backed by an NFS server. Additional keys:
◆ location: (required) The location of the NFS Server, in the form
SERVER:/PATH
◆ mount-path: (optional) The path at which the volume should be
mounted. The mount-path parameter is only supported for single
container services which do not make use of the --container flag. For
multi-container services, specify the mount-path parameter under the
--add-volume-mount flag.
◆ readonly: (optional) A boolean. If true, this volume will be
read-only from all mounts.