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

gcloud: Wed Mar 23 08:27:29 UTC 2022

Browse source
This commit is contained in:
Automated 2022-03-23 08:27:29 +00:00
parent 971306823a
commit cd34e797ae
109 changed files with 1563 additions and 627 deletions
Download patch file Download diff file Expand all files Collapse all files

4
gcloud/compute/backend-services/create
View file

@ -286,7 +286,9 @@ FLAGS
--idle-timeout-sec=IDLE_TIMEOUT_SEC
Specifies how long to keep a connection tracking table entry while
there is no matching traffic (in seconds).
there is no matching traffic (in seconds). Applicable only for backend
service-based network load balancers and internal TCP/UDP load
balancers as part of a connection tracking policy.
--load-balancing-scheme=LOAD_BALANCING_SCHEME; default="EXTERNAL"
Specifies the load balancer type. Choose EXTERNAL for load balancers

4
gcloud/compute/backend-services/update
View file

@ -205,7 +205,9 @@ FLAGS
--idle-timeout-sec=IDLE_TIMEOUT_SEC
Specifies how long to keep a connection tracking table entry while
there is no matching traffic (in seconds).
there is no matching traffic (in seconds). Applicable only for backend
service-based network load balancers and internal TCP/UDP load
balancers as part of a connection tracking policy.
--logging-sample-rate=LOGGING_SAMPLE_RATE
This field can only be specified if logging is enabled for the backend

6
gcloud/compute/instances/help
View file

@ -125,6 +125,9 @@ COMMANDS
reset
Reset a virtual machine instance.
resume
Resume a virtual machine instance.
send-diagnostic-interrupt
Send a diagnostic interrupt to a virtual machine instance.
@ -153,6 +156,9 @@ COMMANDS
stop
Stop a virtual machine instance.
suspend
Suspend a virtual machine instance.
tail-serial-port-output
Periodically fetch new output from a virtual machine instance's serial
port and display it as it becomes available.

66
gcloud/compute/instances/resume Normal file
View file

@ -0,0 +1,66 @@
NAME
gcloud compute instances resume - resume a virtual machine instance
SYNOPSIS
gcloud compute instances resume INSTANCE_NAMES [INSTANCE_NAMES ...]
[--async] [--zone=ZONE] [GCLOUD_WIDE_FLAG ...]
DESCRIPTION
gcloud compute instances resume is used to resume a previously suspended
Compute Engine virtual machine.
EXAMPLES
To resume an instance named test-instance, run:
$ gcloud compute instances resume test-instance
POSITIONAL ARGUMENTS
INSTANCE_NAMES [INSTANCE_NAMES ...]
Names of the instances to operate on. For details on valid instance
names, refer to the criteria documented under the field 'name' at:
https://cloud.google.com/compute/docs/reference/rest/v1/instances
FLAGS
--async
Return immediately, without waiting for the operation in progress to
complete.
--zone=ZONE
Zone of the instances to operate on. If not specified, you might be
prompted to select a zone (interactive mode only). gcloud attempts to
identify the appropriate zone by searching for resources in your
currently active project. If the zone cannot be determined, gcloud
prompts you for a selection with all available Google Cloud Platform
zones.
To avoid prompting when this flag is omitted, the user can set the
compute/zone property:
$ gcloud config set compute/zone ZONE
A list of zones can be fetched by running:
$ gcloud compute zones list
To unset the property, run:
$ gcloud config unset compute/zone
Alternatively, the zone can be stored in the environment variable
CLOUDSDK_COMPUTE_ZONE.
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
These variants are also available:
$ gcloud alpha compute instances resume
$ gcloud beta compute instances resume

76
gcloud/compute/instances/suspend Normal file
View file

@ -0,0 +1,76 @@
NAME
gcloud compute instances suspend - suspend a virtual machine instance
SYNOPSIS
gcloud compute instances suspend INSTANCE_NAMES [INSTANCE_NAMES ...]
[--async] [--zone=ZONE] [GCLOUD_WIDE_FLAG ...]
DESCRIPTION
gcloud compute instances suspend is used to suspend a Compute Engine
virtual machine. Suspending a VM is the equivalent of sleep or standby
mode: the guest receives an ACPI S3 suspend signal, after which all VM
state is saved to temporary storage. An instance can only be suspended
while it is in the RUNNING state. A suspended instance will be put in
SUSPENDED state.
Note: A suspended instance can be resumed by running the gcloud compute
instances resume command.
Limitations: See this feature's restrictions at
https://cloud.google.com/compute/docs/instances/suspend-resume-instance#limitations
EXAMPLES
To suspend an instance named test-instance, run:
$ gcloud compute instances suspend test-instance
POSITIONAL ARGUMENTS
INSTANCE_NAMES [INSTANCE_NAMES ...]
Names of the instances to operate on. For details on valid instance
names, refer to the criteria documented under the field 'name' at:
https://cloud.google.com/compute/docs/reference/rest/v1/instances
FLAGS
--async
Return immediately, without waiting for the operation in progress to
complete.
--zone=ZONE
Zone of the instances to operate on. If not specified, you might be
prompted to select a zone (interactive mode only). gcloud attempts to
identify the appropriate zone by searching for resources in your
currently active project. If the zone cannot be determined, gcloud
prompts you for a selection with all available Google Cloud Platform
zones.
To avoid prompting when this flag is omitted, the user can set the
compute/zone property:
$ gcloud config set compute/zone ZONE
A list of zones can be fetched by running:
$ gcloud compute zones list
To unset the property, run:
$ gcloud config unset compute/zone
Alternatively, the zone can be stored in the environment variable
CLOUDSDK_COMPUTE_ZONE.
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
These variants are also available:
$ gcloud alpha compute instances suspend
$ gcloud beta compute instances suspend

5
gcloud/compute/network-endpoint-groups/create
View file

@ -52,7 +52,7 @@ FLAGS
network is used if unspecified.
This is only supported for NEGs with endpoint type gce-vm-ip-port,
non-gcp-private-ip-port, or gce-vm-ip.
non-gcp-private-ip-port, gce-vm-ip, or private-service-connect.
--network-endpoint-type=NETWORK_ENDPOINT_TYPE; default="gce-vm-ip-port"
Determines the spec of endpoints attached to this group.
@ -100,8 +100,7 @@ FLAGS
private-service-connect
The network endpoint corresponds to a service outside the VPC,
accessed via Private Service Connect. The network, subnet, and
default port must not be set.
accessed via Private Service Connect.
NETWORK_ENDPOINT_TYPE must be one of: gce-vm-ip-port,
internet-ip-port, internet-fqdn-port, non-gcp-private-ip-port,

24
gcloud/compute/url-maps/validate
View file

@ -2,7 +2,8 @@ NAME
gcloud compute url-maps validate - validate a URL map
SYNOPSIS
gcloud compute url-maps validate [--source=SOURCE]
gcloud compute url-maps validate
[--load-balancing-scheme=LOAD_BALANCING_SCHEME] [--source=SOURCE]
[--global | --region=REGION] [GCLOUD_WIDE_FLAG ...]
DESCRIPTION
@ -16,6 +17,27 @@ EXAMPLES
$ gcloud compute url-maps validate --source=<path-to-file>
FLAGS
--load-balancing-scheme=LOAD_BALANCING_SCHEME
Specifies the load balancer type(s) this validation request is for. Use
EXTERNAL_MANAGED for HTTP/HTTPS External Global Load Balancer with
Advanced Traffic Management. Use EXTERNAL for Classic HTTP/HTTPS
External Global Load Balancer.
Other load balancer types are not supported. For more information,
refer to Choosing a load balancer
(https://cloud.google.com/load-balancing/docs/choosing-load-balancer/).
If unspecified, the load balancing scheme will be inferred from the
backend service resources this URL map references. If that can not be
inferred (for example, this URL map only references backend buckets, or
this URL map is for rewrites and redirects only and doesn't reference
any backends), EXTERNAL will be used as the default type.
If specified, the scheme must not conflict with the load balancing
scheme of the backend service resources this URL map references.
LOAD_BALANCING_SCHEME must be one of: EXTERNAL, EXTERNAL_MANAGED.
--source=SOURCE
Path to a YAML file containing configuration export data. The YAML file
must not contain any output-only fields. Alternatively, you may omit