.TH "GCLOUD_ALPHA_CODE_CLEAN\-UP" 1



.SH "NAME"
.HP
gcloud alpha code clean\-up \- delete the local development environment



.SH "SYNOPSIS"
.HP
\f5gcloud alpha code clean\-up\fR [\fB\-\-minikube\-profile\fR=\fIMINIKUBE_PROFILE\fR] [\fIGCLOUD_WIDE_FLAG\ ...\fR]



.SH "DESCRIPTION"

\fB(ALPHA)\fR Delete the local development environment.

Use this command to clean up a development environment. This command many also
be used remove any artifacts of developments environments that did not
successfully start up.



.SH "EXAMPLES"

.RS 2m
$ gcloud alpha code clean\-up
.RE

To clean up a specific profile:

.RS 2m
$ gcloud alpha code clean\-up \-\-minikube\-profile=<profile name>
.RE



.SH "FLAGS"

.RS 2m
.TP 2m
\fB\-\-minikube\-profile\fR=\fIMINIKUBE_PROFILE\fR

Minikube profile.


.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. This variant is also available:

.RS 2m
$ gcloud beta code clean\-up
.RE