.TH "GCLOUD_ALPHA_DATASTORE_OPERATIONS_DELETE" 1



.SH "NAME"
.HP
gcloud alpha datastore operations delete \- delete a completed Cloud Datastore admin operation



.SH "SYNOPSIS"
.HP
\f5gcloud alpha datastore operations delete\fR \fINAME\fR [\fIGCLOUD_WIDE_FLAG\ ...\fR]



.SH "DESCRIPTION"

\fB(ALPHA)\fR Delete a completed Cloud Datastore admin operation.



.SH "EXAMPLES"

To delete the completed operation with id \f5exampleId\fR, run:

.RS 2m
$ gcloud alpha datastore operations delete exampleId
.RE

or

.RS 2m
$ gcloud alpha datastore operations delete \e
    projects/your\-project\-id/operations/exampleId
.RE



.SH "POSITIONAL ARGUMENTS"

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

The unique name of the Operation to delete, formatted as either the full or
relative resource path:

.RS 2m
projects/my\-app\-id/operations/foo
.RE

or:

.RS 2m
foo
.RE


.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 datastore operations delete
.RE

.RS 2m
$ gcloud beta datastore operations delete
.RE