.TH "GCLOUD_ALPHA_DEPLOY_TARGETS_ROLLBACK" 1



.SH "NAME"
.HP
gcloud alpha deploy targets rollback \- rollbacks a target to a prior rollout



.SH "SYNOPSIS"
.HP
\f5gcloud alpha deploy targets rollback\fR (\fITARGET\fR\ :\ \fB\-\-region\fR=\fIREGION\fR) \fB\-\-delivery\-pipeline\fR=\fIDELIVERY_PIPELINE\fR [\fB\-\-annotations\fR=[\fIKEY\fR=\fIVALUE\fR,...]] [\fB\-\-description\fR=\fIDESCRIPTION\fR] [\fB\-\-labels\fR=[\fIKEY\fR=\fIVALUE\fR,...]] [\fB\-\-override\-deploy\-policies\fR=[\fIPOLICY\fR,...]] [\fB\-\-release\fR=\fIRELEASE\fR] [\fB\-\-rollback\-of\-rollout\fR=\fIROLLBACK_OF_ROLLOUT\fR] [\fB\-\-rollout\-id\fR=\fIROLLOUT_ID\fR] [\fB\-\-starting\-phase\-id\fR=\fISTARTING_PHASE_ID\fR] [\fIGCLOUD_WIDE_FLAG\ ...\fR]



.SH "DESCRIPTION"

\fB(ALPHA)\fR If release is not specified, the command rollbacks the target with
the last successful deployed release. If optional rollout\-id parameter is not
specified, a generated rollout ID will be used.



.SH "EXAMPLES"

To rollback a target 'prod' for delivery pipeline 'test\-pipeline' in region
\'us\-central1', run:

.RS 2m
$ gcloud alpha deploy targets rollback prod \e
    \-\-delivery\-pipeline=test\-pipeline \-\-region=us\-central1
.RE



.SH "POSITIONAL ARGUMENTS"

.RS 2m
.TP 2m

Target resource \- The name of the Target. 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 \f5target\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
\fITARGET\fR

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

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

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

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

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

To set the \f5region\fR attribute:
.RS 2m
.IP "\(bu" 2m
provide the argument \f5target\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 "REQUIRED FLAGS"

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

The name of the Cloud Deploy delivery pipeline


.RE
.sp

.SH "OPTIONAL FLAGS"

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

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

Examples:

Add annotations:

.RS 2m
$ gcloud alpha deploy targets rollback \e
    \-\-annotations="from_target=test,status=stable"
.RE

.TP 2m
\fB\-\-description\fR=\fIDESCRIPTION\fR

Description of rollout created during a rollback.

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

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

Examples:

Add labels:

.RS 2m
$ gcloud alpha deploy targets rollback \e
    \-\-labels="commit=abc123,author=foo"
.RE

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

Deploy policies to override

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

Name of the release to rollback to.

.TP 2m
\fB\-\-rollback\-of\-rollout\fR=\fIROLLBACK_OF_ROLLOUT\fR

If set, this validates whether the rollout name specified by the flag matches
the rollout on the target.

Examples:

Validate that \f5test\-rollout\fR is the rollout to rollback on the target.

.RS 2m
$ gcloud alpha deploy targets rollback \e
    \-\-rollback\-of\-rollout=projects/test\-project/locations/\e
us\-central1/deliveryPipelines/test\-pipeline/releases/test\-release/\e
rollouts/test\-rollout
.RE

.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 alpha deploy targets rollback \-\-starting\-phase\-id=stable
.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 deploy targets rollback
.RE

.RS 2m
$ gcloud beta deploy targets rollback
.RE