1
0
Fork 0
mirror of https://github.com/imjasonh/gcloud-help synced 2026-07-08 10:35:03 +00:00
gcloud-help/gcloud/deploy/releases/promote
2023-03-29 10:40:15 +00:00

112 lines
4 KiB
Text

NAME
gcloud deploy releases promote - promotes a release from one target
(source), to another (destination)
SYNOPSIS
gcloud deploy releases promote
(--release=RELEASE
: --delivery-pipeline=DELIVERY_PIPELINE --region=REGION)
[--annotations=[KEY=VALUE,...]] [--labels=[KEY=VALUE,...]]
[--rollout-id=ROLLOUT_ID] [--starting-phase-id=STARTING_PHASE_ID]
[--to-target=TO_TARGET] [GCLOUD_WIDE_FLAG ...]
DESCRIPTION
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.
EXAMPLES
To promote a release called 'test-release' for delivery pipeline
'test-pipeline' in region 'us-central1' to target 'prod', run:
$ gcloud deploy releases promote --release=test-release \
--delivery-pipeline=test-pipeline --region=us-central1 \
--to-target=prod
REQUIRED FLAGS
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 project attribute:
◆ provide the argument --release on the command line with a fully
specified name;
◆ provide the argument --project on the command line;
◆ set the property core/project.
This must be specified.
--release=RELEASE
ID of the release or fully qualified identifier for the release. To
set the release attribute:
▸ provide the argument --release on the command line.
This flag argument must be specified if any of the other arguments in
this group are specified.
--delivery-pipeline=DELIVERY_PIPELINE
The delivery pipeline associated with the release. Alternatively, set
the property [deploy/delivery-pipeline]. To set the delivery-pipeline
attribute:
▸ provide the argument --release on the command line with a fully
specified name;
▸ provide the argument --delivery-pipeline on the command line;
▸ set the property deploy/delivery_pipeline.
--region=REGION
The Cloud region for the release. Alternatively, set the property
[deploy/region]. To set the region attribute:
▸ provide the argument --release on the command line with a fully
specified name;
▸ provide the argument --region on the command line;
▸ set the property deploy/region.
OPTIONAL FLAGS
--annotations=[KEY=VALUE,...]
Annotations to apply to the rollout. Annotations take the form of
key/value string pairs.
Examples:
Add annotations:
$ gcloud deploy releases promote \
--annotations="from_target=test,status=stable"
--labels=[KEY=VALUE,...]
Labels to apply to the rollout. Labels take the form of key/value
string pairs.
Examples:
Add labels:
$ gcloud deploy releases promote --labels="commit=abc123,author=foo"
--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 at stable phase:
$ gcloud deploy releases promote --starting-phase-id=stable
--to-target=TO_TARGET
Destination target to promote into.
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
These variants are also available:
$ gcloud alpha deploy releases promote
$ gcloud beta deploy releases promote