gcloud beta deploy targets rollback

NAME
gcloud beta deploy targets rollback - rollbacks a target to a prior rollout
SYNOPSIS
gcloud beta deploy targets rollback(TARGET :--region=REGION)--delivery-pipeline=DELIVERY_PIPELINE[--annotations=[KEY=VALUE,…]][--description=DESCRIPTION][--labels=[KEY=VALUE,…]][--override-deploy-policies=[POLICY,…]][--release=RELEASE][--rollout-id=ROLLOUT_ID][--starting-phase-id=STARTING_PHASE_ID][GCLOUD_WIDE_FLAG]
DESCRIPTION
(BETA) If release is not specified, the command rollbacks thetarget with the last successful deployed release. If optional rollout-idparameter is not specified, a generated rollout ID will be used.
EXAMPLES
To rollback a target 'prod' for delivery pipeline 'test-pipeline' in region'us-central1', run:
gcloudbetadeploytargetsrollbackprod--delivery-pipeline=test-pipeline--region=us-central1
POSITIONAL ARGUMENTS
Target resource - The name of the Target. The arguments in this group can beused to specify the attributes of this resource. (NOTE) Some attributes are notgiven arguments in this group but can be set in other ways.

To set theproject attribute:

  • provide the argumenttarget on the command line with a fullyspecified name;
  • provide the argument--project on the command line;
  • set the propertycore/project.

This must be specified.

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

To set thetarget attribute:

  • provide the argumenttarget on the command line.

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

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

To set theregion attribute:

  • provide the argumenttarget on the command line with a fullyspecified name;
  • provide the argument--region on the command line;
  • set the propertydeploy/region.
REQUIRED FLAGS
--delivery-pipeline=DELIVERY_PIPELINE
The name of the Cloud Deploy delivery pipeline
OPTIONAL FLAGS
--annotations=[KEY=VALUE,…]
Annotations to apply to the rollback. Annotations take the form of key/valuestring pairs.

Examples:

Add annotations:

gcloudbetadeploytargetsrollback--annotations="from_target=test,status=stable"
--description=DESCRIPTION
Description of rollout created during a rollback.
--labels=[KEY=VALUE,…]
Labels to apply to the rollback. Labels take the form of key/value string pairs.

Examples:

Add labels:

gcloudbetadeploytargetsrollback--labels="commit=abc123,author=foo"
--override-deploy-policies=[POLICY,…]
Deploy policies to override
--release=RELEASE
Name of the release to rollback to.
--rollout-id=ROLLOUT_ID
ID to assign to the generated rollout for promotion.
--starting-phase-id=STARTING_PHASE_ID
If set, starts the created rollout at the specified phase.

Start rollout atstable phase:

gcloudbetadeploytargetsrollback--starting-phase-id=stable
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$gcloud help for details.

NOTES
This command is currently in beta and might change without notice. Thesevariants are also available:
gclouddeploytargetsrollback
gcloudalphadeploytargetsrollback

Except as otherwise noted, the content of this page is licensed under theCreative Commons Attribution 4.0 License, and code samples are licensed under theApache 2.0 License. For details, see theGoogle Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.

Last updated 2025-05-13 UTC.