.TH "GCLOUD_ALPHA_COMPUTE_ROUTES_DELETE" 1



.SH "NAME"
.HP
gcloud alpha compute routes delete \- delete routes



.SH "SYNOPSIS"
.HP
\f5gcloud alpha compute routes delete\fR \fINAME\fR [\fINAME\fR\ ...] [\fIGCLOUD_WIDE_FLAG\ ...\fR]



.SH "DESCRIPTION"

\fB(ALPHA)\fR \fBgcloud alpha compute routes delete\fR deletes one or more
Compute Engine routes.



.SH "EXAMPLES"

To delete a route with the name 'route\-name', run:

.RS 2m
$ gcloud alpha compute routes delete route\-name
.RE

To delete two routes with the names 'route\-name1' and 'route\-name2', run:

.RS 2m
$ gcloud alpha compute routes delete route\-name1 route\-name2
.RE



.SH "POSITIONAL ARGUMENTS"

.RS 2m
.TP 2m
\fINAME\fR [\fINAME\fR ...]

Names of the routes to delete.


.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 compute routes delete
.RE

.RS 2m
$ gcloud beta compute routes delete
.RE