File: //snap/google-cloud-cli/396/help/man/man1/gcloud_alpha_spanner_instance-configs_delete.1
.TH "GCLOUD_ALPHA_SPANNER_INSTANCE\-CONFIGS_DELETE" 1
.SH "NAME"
.HP
gcloud alpha spanner instance\-configs delete \- delete a Cloud Spanner instance configuration
.SH "SYNOPSIS"
.HP
\f5gcloud alpha spanner instance\-configs delete\fR \fIINSTANCE_CONFIG\fR [\fB\-\-etag\fR=\fIETAG\fR] [\fB\-\-validate\-only\fR] [\fIGCLOUD_WIDE_FLAG\ ...\fR]
.SH "DESCRIPTION"
\fB(ALPHA)\fR Delete a Cloud Spanner instance configuration.
.SH "EXAMPLES"
To delete a custom Cloud Spanner instance configuration, run:
.RS 2m
$ gcloud alpha spanner instance\-configs delete custom\-instance\-config
.RE
.SH "POSITIONAL ARGUMENTS"
.RS 2m
.TP 2m
\fIINSTANCE_CONFIG\fR
Cloud Spanner instance config.
.RE
.sp
.SH "FLAGS"
.RS 2m
.TP 2m
\fB\-\-etag\fR=\fIETAG\fR
Used for optimistic concurrency control as a way to help prevent simultaneous
deletes of an instance config from overwriting each other.
.TP 2m
\fB\-\-validate\-only\fR
If specified, validate that the deletion will succeed without deleting the
instance config.
.RE
.sp
.SH "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 \fB$ gcloud help\fR for details.
.SH "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:
.RS 2m
$ gcloud spanner instance\-configs delete
.RE
.RS 2m
$ gcloud beta spanner instance\-configs delete
.RE