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 Oct 23 10:01:22 UTC 2024

Browse source
This commit is contained in:
Automated 2024-10-23 10:01:22 +00:00
parent 694f6671d0
commit fc66f7f0ca
249 changed files with 5410 additions and 11408 deletions
Download patch file Download diff file Expand all files Collapse all files

9
gcloud/beta/compute/backend-buckets/create
View file

@ -11,7 +11,8 @@ SYNOPSIS
[--compression-mode=COMPRESSION_MODE]
[--custom-response-header=CUSTOM_RESPONSE_HEADER]
[--default-ttl=DEFAULT_TTL] [--description=DESCRIPTION]
[--[no-]enable-cdn] [--max-ttl=MAX_TTL] [--[no-]negative-caching]
[--[no-]enable-cdn] [--load-balancing-scheme=LOAD_BALANCING_SCHEME]
[--max-ttl=MAX_TTL] [--[no-]negative-caching]
[--negative-caching-policy=[[CODE=TTL],...]]
[--[no-]request-coalescing] [--serve-while-stale=SERVE_WHILE_STALE]
[--signed-url-cache-max-age=SIGNED_URL_CACHE_MAX_AGE]
@ -157,6 +158,12 @@ OPTIONAL FLAGS
responses from a backend bucket at the edge of the network, close to
users. Use --enable-cdn to enable and --no-enable-cdn to disable.
--load-balancing-scheme=LOAD_BALANCING_SCHEME
The load balancing scheme of the backend bucket. If left blank, the
backend bucket will be compatible with Global External Application Load
Balancer or Classic Application Load Balancer. LOAD_BALANCING_SCHEME
must be (only one value is supported): INTERNAL_MANAGED.
--max-ttl=MAX_TTL
Specifies the maximum allowed TTL for cached content served by this
origin.

5
gcloud/beta/compute/commitments/create
View file

@ -5,6 +5,7 @@ SYNOPSIS
gcloud beta compute commitments create COMMITMENT --plan=PLAN
(--resources=[local-ssd=LOCAL-SSD],[memory=MEMORY],[vcpu=VCPU]
--resources-accelerator=[count=COUNT],[type=TYPE]) [--auto-renew]
[--custom-end-time=CUSTOM_END_TIME]
[--merge-source-commitments=MERGE_SOURCE_COMMITMENTS] [--region=REGION]
[--split-source-commitment=SPLIT_SOURCE_COMMITMENT]
[--type=TYPE; default="general-purpose"]
@ -70,6 +71,10 @@ OPTIONAL FLAGS
--auto-renew
Enable auto renewal for the commitment.
--custom-end-time=CUSTOM_END_TIME
Specifies a custom future end date and extends the commitment's ongoing
term.
--merge-source-commitments=MERGE_SOURCE_COMMITMENTS
Creates the new commitment by merging the specified source commitments
and combining their resources.

7
gcloud/beta/compute/commitments/update
View file

@ -3,7 +3,8 @@ NAME
SYNOPSIS
gcloud beta compute commitments update COMMITMENT [--auto-renew]
[--plan=PLAN] [--region=REGION] [GCLOUD_WIDE_FLAG ...]
[--custom-end-time=CUSTOM_END_TIME] [--plan=PLAN] [--region=REGION]
[GCLOUD_WIDE_FLAG ...]
DESCRIPTION
(BETA) Update Compute Engine commitments.
@ -35,6 +36,10 @@ FLAGS
--auto-renew
Enable auto renewal for the commitment.
--custom-end-time=CUSTOM_END_TIME
Specifies a custom future end date and extends the commitment's ongoing
term.
--plan=PLAN
Duration of the commitment. PLAN must be (only one value is supported):
36-month.

37
gcloud/beta/compute/instance-groups/managed/resize-requests/describe
View file

@ -4,9 +4,9 @@ NAME
resource
SYNOPSIS
gcloud beta compute instance-groups managed resize-requests describe
INSTANCE_GROUP_MANAGER --resize-request=RESIZE_REQUEST_NAME
[--zone=ZONE] [GCLOUD_WIDE_FLAG ...]
gcloud beta compute instance-groups managed resize-requests describe NAME
--resize-request=RESIZE_REQUEST_NAME [--region=REGION | --zone=ZONE]
[GCLOUD_WIDE_FLAG ...]
DESCRIPTION
(BETA) gcloud beta compute instance-groups managed resize-requests describe
@ -20,7 +20,7 @@ EXAMPLES
describe my-mig --resize-request=resize-request-1
POSITIONAL ARGUMENTS
INSTANCE_GROUP_MANAGER
NAME
Name of the managed instance group to operate on.
REQUIRED FLAGS
@ -28,26 +28,29 @@ REQUIRED FLAGS
The name of the resize request to describe.
OPTIONAL FLAGS
--zone=ZONE
Zone of the managed instance group to operate on. If not specified and
the compute/zone property isn't set, you might be prompted to select a
zone (interactive mode only).
At most one of these can be specified:
To avoid prompting when this flag is omitted, you can set the
compute/zone property:
--region=REGION
Region of the managed instance group to operate on. If not specified,
you might be prompted to select a region (interactive mode only).
$ gcloud config set compute/zone ZONE
A list of regions can be fetched by running:
A list of zones can be fetched by running:
$ gcloud compute regions list
$ gcloud compute zones list
Overrides the default compute/region property value for this command
invocation.
To unset the property, run:
--zone=ZONE
Zone of the managed instance group to operate on. If not specified,
you might be prompted to select a zone (interactive mode only).
$ gcloud config unset compute/zone
A list of zones can be fetched by running:
Alternatively, the zone can be stored in the environment variable
CLOUDSDK_COMPUTE_ZONE.
$ gcloud compute zones list
Overrides the default compute/zone property value for this command
invocation.
GCLOUD WIDE FLAGS
These flags are available to all commands: --access-token-file, --account,

37
gcloud/beta/compute/instance-groups/managed/resize-requests/list
View file

@ -3,9 +3,9 @@ NAME
Compute Engine managed instance group resize requests
SYNOPSIS
gcloud beta compute instance-groups managed resize-requests list
INSTANCE_GROUP_MANAGER [--zone=ZONE] [--filter=EXPRESSION]
[--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri]
gcloud beta compute instance-groups managed resize-requests list NAME
[--region=REGION | --zone=ZONE] [--filter=EXPRESSION] [--limit=LIMIT]
[--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri]
[GCLOUD_WIDE_FLAG ...]
DESCRIPTION
@ -24,30 +24,33 @@ EXAMPLES
example-managed-instance-group --zone=us-central1-a --uri
POSITIONAL ARGUMENTS
INSTANCE_GROUP_MANAGER
NAME
Name of the managed instance group to operate on.
FLAGS
--zone=ZONE
Zone of the managed instance group to operate on. If not specified and
the compute/zone property isn't set, you might be prompted to select a
zone (interactive mode only).
At most one of these can be specified:
To avoid prompting when this flag is omitted, you can set the
compute/zone property:
--region=REGION
Region of the managed instance group to operate on. If not specified,
you might be prompted to select a region (interactive mode only).
$ gcloud config set compute/zone ZONE
A list of regions can be fetched by running:
A list of zones can be fetched by running:
$ gcloud compute regions list
$ gcloud compute zones list
Overrides the default compute/region property value for this command
invocation.
To unset the property, run:
--zone=ZONE
Zone of the managed instance group to operate on. If not specified,
you might be prompted to select a zone (interactive mode only).
$ gcloud config unset compute/zone
A list of zones can be fetched by running:
Alternatively, the zone can be stored in the environment variable
CLOUDSDK_COMPUTE_ZONE.
$ gcloud compute zones list
Overrides the default compute/zone property value for this command
invocation.
LIST COMMAND FLAGS
--filter=EXPRESSION

5
gcloud/beta/compute/snapshot-settings/describe
View file

@ -21,8 +21,9 @@ GCLOUD WIDE FLAGS
Run $ gcloud help for details.
API REFERENCE
This command uses the compute/beta API. The full documentation for this API
can be found at: https://cloud.google.com/compute/
This command uses the compute/alpha or compute/beta or comptue/v1 API. The
full documentation for this API can be found at:
https://cloud.google.com/compute/
NOTES
This command is currently in beta and might change without notice. These

14
gcloud/beta/compute/snapshot-settings/update
View file

@ -15,19 +15,20 @@ EXAMPLES
nearest multi-region as the source disk, run:
$ gcloud beta compute snapshot-settings update \
--storage-location-policy=nearest-multi-region
--storage-location-policy=nearest-multi-region
To update the snapshot settings and set the storage location policy to the
same region as the source disk, run:
$ gcloud alpha compute snapshot-settings update \ --storage-location-policy=local-region
$ gcloud beta compute snapshot-settings update \
--storage-location-policy=local-region
To update the snapshot settings and set the storage location policy to
store snapshots in a specific location like us-west1, run:
$ gcloud beta compute snapshot-settings update \
--storage-location-policy=specific-locations \
--storage-location-names=us-west1
--storage-location-policy=specific-locations \
--storage-location-names=us-west1
FLAGS
--async
@ -58,8 +59,9 @@ GCLOUD WIDE FLAGS
Run $ gcloud help for details.
API REFERENCE
This command uses the compute/beta API. The full documentation for this API
can be found at: https://cloud.google.com/compute/
This command uses the compute/alpha or compute/beta or compute/v1 API. The
full documentation for this API can be found at:
https://cloud.google.com/compute/
NOTES
This command is currently in beta and might change without notice. These