.TH "GCLOUD_ALPHA_ENDPOINTS_OPERATIONS_WAIT" 1



.SH "NAME"
.HP
gcloud alpha endpoints operations wait \- waits for an operation to complete



.SH "SYNOPSIS"
.HP
\f5gcloud alpha endpoints operations wait\fR \fIOPERATION\fR [\fIGCLOUD_WIDE_FLAG\ ...\fR]



.SH "DESCRIPTION"

\fB(ALPHA)\fR This command will block until an operation has been marked as
complete.

Note that the \f5operations/\fR prefix of the operation name is optional and may
be omitted.



.SH "EXAMPLES"

To wait on an operation named \f5operations/serviceConfigs.my\-service.1\fR to
complete, run:

.RS 2m
$ gcloud alpha endpoints operations wait serviceConfigs.my\-service.1
.RE



.SH "POSITIONAL ARGUMENTS"

.RS 2m
.TP 2m
\fIOPERATION\fR

The name of the operation on which to wait.


.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 endpoints operations wait
.RE

.RS 2m
$ gcloud beta endpoints operations wait
.RE