HEX
Server: Apache/2.4.65 (Ubuntu)
System: Linux ielts-store-v2 6.8.0-1036-gcp #38~22.04.1-Ubuntu SMP Thu Aug 14 01:19:18 UTC 2025 x86_64
User: root (0)
PHP: 7.2.34-54+ubuntu20.04.1+deb.sury.org+1
Disabled: pcntl_alarm,pcntl_fork,pcntl_waitpid,pcntl_wait,pcntl_wifexited,pcntl_wifstopped,pcntl_wifsignaled,pcntl_wifcontinued,pcntl_wexitstatus,pcntl_wtermsig,pcntl_wstopsig,pcntl_signal,pcntl_signal_get_handler,pcntl_signal_dispatch,pcntl_get_last_error,pcntl_strerror,pcntl_sigprocmask,pcntl_sigwaitinfo,pcntl_sigtimedwait,pcntl_exec,pcntl_getpriority,pcntl_setpriority,pcntl_async_signals,
Upload Files
File: //snap/google-cloud-cli/396/help/man/man1/gcloud_beta_deploy_releases_promote.1
.TH "GCLOUD_BETA_DEPLOY_RELEASES_PROMOTE" 1



.SH "NAME"
.HP
gcloud beta deploy releases promote \- promotes a release from one target (source), to another (destination)



.SH "SYNOPSIS"
.HP
\f5gcloud beta deploy releases promote\fR (\fB\-\-release\fR=\fIRELEASE\fR\ :\ \fB\-\-delivery\-pipeline\fR=\fIDELIVERY_PIPELINE\fR\ \fB\-\-region\fR=\fIREGION\fR) [\fB\-\-annotations\fR=[\fIKEY\fR=\fIVALUE\fR,...]] [\fB\-\-labels\fR=[\fIKEY\fR=\fIVALUE\fR,...]] [\fB\-\-override\-deploy\-policies\fR=[\fIPOLICY\fR,...]] [\fB\-\-rollout\-id\fR=\fIROLLOUT_ID\fR] [\fB\-\-starting\-phase\-id\fR=\fISTARTING_PHASE_ID\fR] [\fB\-\-to\-target\fR=\fITO_TARGET\fR] [\fIGCLOUD_WIDE_FLAG\ ...\fR]



.SH "DESCRIPTION"

\fB(BETA)\fR If to\-target is not specified the command promotes the release
from the target that is farthest along in the promotion sequence to its next
stage in the promotion sequence.



.SH "EXAMPLES"

To promote a release called 'test\-release' for delivery pipeline
\'test\-pipeline' in region 'us\-central1' to target 'prod', run:

.RS 2m
$ gcloud beta deploy releases promote \-\-release=test\-release \e
    \-\-delivery\-pipeline=test\-pipeline \-\-region=us\-central1 \e
    \-\-to\-target=prod
.RE



.SH "REQUIRED FLAGS"

.RS 2m
.TP 2m

Release resource \- The name of the Release. The arguments in this group can be
used to specify the attributes of this resource. (NOTE) Some attributes are not
given arguments in this group but can be set in other ways.

To set the \f5project\fR attribute:
.RS 2m
.IP "\(em" 2m
provide the argument \f5\-\-release\fR on the command line with a fully
specified name;
.IP "\(em" 2m
provide the argument \f5\-\-project\fR on the command line;
.IP "\(em" 2m
set the property \f5core/project\fR.
.RE
.sp

This must be specified.


.RS 2m
.TP 2m
\fB\-\-release\fR=\fIRELEASE\fR

ID of the release or fully qualified identifier for the release.

To set the \f5release\fR attribute:
.RS 2m
.IP "\(bu" 2m
provide the argument \f5\-\-release\fR on the command line.
.RE
.sp

This flag argument must be specified if any of the other arguments in this group
are specified.

.TP 2m
\fB\-\-delivery\-pipeline\fR=\fIDELIVERY_PIPELINE\fR

The delivery pipeline associated with the release. Alternatively, set the
property [deploy/delivery\-pipeline].

To set the \f5delivery\-pipeline\fR attribute:
.RS 2m
.IP "\(bu" 2m
provide the argument \f5\-\-release\fR on the command line with a fully
specified name;
.IP "\(bu" 2m
provide the argument \f5\-\-delivery\-pipeline\fR on the command line;
.IP "\(bu" 2m
set the property \f5deploy/delivery_pipeline\fR.
.RE
.sp

.TP 2m
\fB\-\-region\fR=\fIREGION\fR

The Cloud region for the release. Alternatively, set the property
[deploy/region].

To set the \f5region\fR attribute:
.RS 2m
.IP "\(bu" 2m
provide the argument \f5\-\-release\fR on the command line with a fully
specified name;
.IP "\(bu" 2m
provide the argument \f5\-\-region\fR on the command line;
.IP "\(bu" 2m
set the property \f5deploy/region\fR.
.RE
.sp


.RE
.RE
.sp

.SH "OPTIONAL FLAGS"

.RS 2m
.TP 2m
\fB\-\-annotations\fR=[\fIKEY\fR=\fIVALUE\fR,...]

Annotations to apply to the rollout. Annotations take the form of key/value
string pairs.

Examples:

Add annotations:

.RS 2m
$ gcloud beta deploy releases promote \e
    \-\-annotations="from_target=test,status=stable"
.RE

.TP 2m
\fB\-\-labels\fR=[\fIKEY\fR=\fIVALUE\fR,...]

Labels to apply to the rollout. Labels take the form of key/value string pairs.

Examples:

Add labels:

.RS 2m
$ gcloud beta deploy releases promote \e
    \-\-labels="commit=abc123,author=foo"
.RE

.TP 2m
\fB\-\-override\-deploy\-policies\fR=[\fIPOLICY\fR,...]

Deploy policies to override

.TP 2m
\fB\-\-rollout\-id\fR=\fIROLLOUT_ID\fR

ID to assign to the generated rollout for promotion.

.TP 2m
\fB\-\-starting\-phase\-id\fR=\fISTARTING_PHASE_ID\fR

If set, starts the created rollout at the specified phase.

Start rollout at \f5stable\fR phase:

.RS 2m
$ gcloud beta deploy releases promote \-\-starting\-phase\-id=stable
.RE

.TP 2m
\fB\-\-to\-target\fR=\fITO_TARGET\fR

Destination target to promote into.


.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 beta and might change without notice. These
variants are also available:

.RS 2m
$ gcloud deploy releases promote
.RE

.RS 2m
$ gcloud alpha deploy releases promote
.RE