1
0
Fork 0
mirror of https://github.com/imjasonh/gcloud-help synced 2026-07-13 16:37:00 +00:00

gcloud: Thu Jan 18 10:21:20 UTC 2024

This commit is contained in:
Automated 2024-01-18 10:21:20 +00:00
parent 5fec13c692
commit a47e1e835a
156 changed files with 4341 additions and 674 deletions

View file

@ -75,6 +75,9 @@ COMMANDS
resize
(BETA) Set managed instance group size.
resume-instances
(BETA) Resume the suspended instances in a managed instance group.
set-autohealing
(BETA) (DEPRECATED) Set autohealing policy for managed instance group.
@ -90,9 +93,18 @@ COMMANDS
set-target-pools
(BETA) Set target pools of managed instance group.
start-instances
(BETA) Start the stopped instances in a managed instance group.
stop-autoscaling
(BETA) Stop autoscaling a managed instance group.
stop-instances
(BETA) Stop instances owned by a managed instance group.
suspend-instances
(BETA) Suspend instances owned by a managed instance group.
update
(BETA) Update a Compute Engine managed instance group.

View file

@ -0,0 +1,74 @@
NAME
gcloud beta compute instance-groups managed resume-instances - resume the
suspended instances in a managed instance group
SYNOPSIS
gcloud beta compute instance-groups managed resume-instances NAME
--instances=INSTANCE,[INSTANCE,...] [--region=REGION | --zone=ZONE]
[GCLOUD_WIDE_FLAG ...]
DESCRIPTION
(BETA) gcloud beta compute instance-groups managed resume-instances resumes
one or more instances from a managed instance group, thereby increasing the
targetSize and reducing the targetSuspendedSize of the group.
The command returns the operation status per instance, which might be FAIL,
SUCCESS, or MEMBER_NOT_FOUND. MEMBER_NOT_FOUND is returned only for
regional groups when the gcloud command-line tool wasn't able to resolve
the zone from the instance name.
EXAMPLES
To resume an instance from a managed instance group in the us-central1-a
zone, run:
$ gcloud beta compute instance-groups managed resume-instances \
example-managed-instance-group --zone=us-central1-a \
--instances=example-instance
POSITIONAL ARGUMENTS
NAME
Name of the managed instance group to operate on.
REQUIRED FLAGS
--instances=INSTANCE,[INSTANCE,...]
Names of instances to resume.
OPTIONAL FLAGS
At most one of these can be specified:
--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).
A list of regions can be fetched by running:
$ gcloud compute regions list
Overrides the default compute/region property value for this command
invocation.
--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).
A list of zones can be fetched by running:
$ 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,
--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 compute instance-groups managed resume-instances

View file

@ -0,0 +1,74 @@
NAME
gcloud beta compute instance-groups managed start-instances - start the
stopped instances in a managed instance group
SYNOPSIS
gcloud beta compute instance-groups managed start-instances NAME
--instances=INSTANCE,[INSTANCE,...] [--region=REGION | --zone=ZONE]
[GCLOUD_WIDE_FLAG ...]
DESCRIPTION
(BETA) gcloud beta compute instance-groups managed start-instances starts
one or more instances from a managed instance group, thereby increasing the
targetSize and reducing the targetStoppedSize of the group.
The command returns the operation status per instance, which might be FAIL,
SUCCESS, or MEMBER_NOT_FOUND. MEMBER_NOT_FOUND is returned only for
regional groups when the gcloud command-line tool wasn't able to resolve
the zone from the instance name.
EXAMPLES
To start an instance from a managed instance group in the us-central1-a
zone, run:
$ gcloud beta compute instance-groups managed start-instances \
example-managed-instance-group --zone=us-central1-a \
--instances=example-instance
POSITIONAL ARGUMENTS
NAME
Name of the managed instance group to operate on.
REQUIRED FLAGS
--instances=INSTANCE,[INSTANCE,...]
Names of instances to start.
OPTIONAL FLAGS
At most one of these can be specified:
--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).
A list of regions can be fetched by running:
$ gcloud compute regions list
Overrides the default compute/region property value for this command
invocation.
--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).
A list of zones can be fetched by running:
$ 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,
--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 compute instance-groups managed start-instances

View file

@ -0,0 +1,72 @@
NAME
gcloud beta compute instance-groups managed stop-instances - stop instances
owned by a managed instance group
SYNOPSIS
gcloud beta compute instance-groups managed stop-instances NAME
--instances=INSTANCE,[INSTANCE,...] [--force]
[--region=REGION | --zone=ZONE] [GCLOUD_WIDE_FLAG ...]
DESCRIPTION
(BETA) gcloud beta compute instance-groups managed stop-instances stops one
or more instances from a managed instance group
EXAMPLES
To stop an instance from a managed instance group in the us-central1-a
zone, run:
$ gcloud beta compute instance-groups managed stop-instances \
example-managed-instance-group --zone=us-central1-a \
--instances=example-instance
POSITIONAL ARGUMENTS
NAME
Name of the managed instance group to operate on.
REQUIRED FLAGS
--instances=INSTANCE,[INSTANCE,...]
Names of instances to stop.
OPTIONAL FLAGS
--force
Immediately stop the specified instances, skipping the initial delay,
if one is specified in the standby policy.
At most one of these can be specified:
--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).
A list of regions can be fetched by running:
$ gcloud compute regions list
Overrides the default compute/region property value for this command
invocation.
--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).
A list of zones can be fetched by running:
$ 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,
--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 compute instance-groups managed stop-instances

View file

@ -0,0 +1,79 @@
NAME
gcloud beta compute instance-groups managed suspend-instances - suspend
instances owned by a managed instance group
SYNOPSIS
gcloud beta compute instance-groups managed suspend-instances NAME
--instances=INSTANCE,[INSTANCE,...] [--force]
[--region=REGION | --zone=ZONE] [GCLOUD_WIDE_FLAG ...]
DESCRIPTION
(BETA) gcloud beta compute instance-groups managed suspend-instances
suspends one or more instances from a managed instance group, thereby
reducing the targetSize and increasing the targetSuspendedSize of the
group.
The command returns the operation status per instance, which might be FAIL,
SUCCESS, or MEMBER_NOT_FOUND. MEMBER_NOT_FOUND is returned only for
regional groups when the gcloud command-line tool wasn't able to resolve
the zone from the instance name.
EXAMPLES
To suspend an instance from a managed instance group in the us-central1-a
zone, run:
$ gcloud beta compute instance-groups managed suspend-instances \
example-managed-instance-group --zone=us-central1-a \
--instances=example-instance
POSITIONAL ARGUMENTS
NAME
Name of the managed instance group to operate on.
REQUIRED FLAGS
--instances=INSTANCE,[INSTANCE,...]
Names of instances to suspend.
OPTIONAL FLAGS
--force
Immediately suspend the specified instances, skipping the initial
delay, if one is specified in the standby policy.
At most one of these can be specified:
--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).
A list of regions can be fetched by running:
$ gcloud compute regions list
Overrides the default compute/region property value for this command
invocation.
--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).
A list of zones can be fetched by running:
$ 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,
--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 compute instance-groups managed suspend-instances