mirror of
https://github.com/imjasonh/gcloud-help
synced 2026-07-08 18:45:13 +00:00
65 lines
2.3 KiB
Text
65 lines
2.3 KiB
Text
NAME
|
|
gcloud alpha compute instance-groups unmanaged delete - delete Compute
|
|
Engine unmanaged instance groups
|
|
|
|
SYNOPSIS
|
|
gcloud alpha compute instance-groups unmanaged delete NAME [NAME ...]
|
|
[--zone=ZONE] [GCLOUD_WIDE_FLAG ...]
|
|
|
|
DESCRIPTION
|
|
(ALPHA) gcloud alpha compute instance-groups unmanaged delete deletes one
|
|
or more Compute Engine unmanaged instance groups. This command just deletes
|
|
the instance group and does not delete the individual virtual machine
|
|
instances in the instance group. For example:
|
|
|
|
$ gcloud alpha compute instance-groups unmanaged delete \
|
|
example-instance-group-1 example-instance-group-2 \
|
|
--zone us-central1-a
|
|
|
|
The above example deletes two instance groups, example-instance-group-1 and
|
|
example-instance-group-2, in the us-central1-a zone.
|
|
|
|
POSITIONAL ARGUMENTS
|
|
NAME [NAME ...]
|
|
Names of the instance groups to delete.
|
|
|
|
FLAGS
|
|
--zone=ZONE
|
|
Zone of the instance groups to delete. If not specified and the
|
|
compute/zone property isn't set, you might be prompted to select a zone
|
|
(interactive mode only).
|
|
|
|
To avoid prompting when this flag is omitted, you 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
|
|
This command is currently in alpha and might change without notice. If this
|
|
command fails with API permission errors despite specifying the correct
|
|
project, you might be trying to access an API with an invitation-only early
|
|
access allowlist. These variants are also available:
|
|
|
|
$ gcloud compute instance-groups unmanaged delete
|
|
|
|
$ gcloud beta compute instance-groups unmanaged delete
|
|
|