gcloud beta saas-runtime rollouts update

NAME
gcloud beta saas-runtime rollouts update - update a Rollout
SYNOPSIS
gcloud beta saas-runtime rollouts update(ROLLOUT :--location=LOCATION)[--rollout-orchestration-strategy=ROLLOUT_ORCHESTRATION_STRATEGY][--unit-filter=UNIT_FILTER][--clear-control--control-action=CONTROL_ACTION--[no-]retry-failed-operations][--labels=[LABELS,…]    |--update-labels=[UPDATE_LABELS,…]--clear-labels    |--remove-labels=REMOVE_LABELS][GCLOUD_WIDE_FLAG]
DESCRIPTION
(BETA) Update a Rollout
EXAMPLES
To update the Rollout, run:
gcloudbetasaas-runtimerolloutsupdate
POSITIONAL ARGUMENTS
RolloutId resource - Identifier. The resource name (full URI of the resource)following the standard naming scheme:
"projects/{project}/locations/{location}/rollout/{rollout_id}"Theargumentsinthisgroupcanbeusedtospecifytheattributesofthisresource.(NOTE)Someattributesarenotgivenargumentsinthisgroupbutcanbesetinotherways.

To set theproject attribute:

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

This must be specified.

ROLLOUT
ID of the rolloutId or fully qualified identifier for the rolloutId.

To set therollout attribute:

  • provide the argumentrollout on the command line.

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

--location=LOCATION
Location ID

To set thelocation attribute:

  • provide the argumentrollout on the command line with a fullyspecified name;
  • provide the argument--location on the command line.
FLAGS
--rollout-orchestration-strategy=ROLLOUT_ORCHESTRATION_STRATEGY
The strategy to use for executing this rollout. If not provided, the strategyfrom Rollout Type will be used.
--unit-filter=UNIT_FILTER
CEL(https://github.com/google/cel-spec) formatted filter string against Unit.The filter will be applied to determine the eligible unit population. Thisfilter can only reduce, but not expand the scope of the rollout. If notprovided, the unit_filter from the RolloutType will be used.
RolloutControl provides a way to request a change to the execution of a Rolloutby pausing or canceling it.
--clear-control
Set rollout.control back to default value.
--control-action=CONTROL_ACTION
Action to be performed on the Rollout. The default behavior is to run therollout until it naturally reaches a terminal state.CONTROL_ACTION must be one of:
cancel
Cancel the Rollout permanently.
pause
Pause the Rollout until it is resumed (i.e. RUN is requested).
run
Run the Rollout until it naturally reaches a terminal state. A rollout requestedto run will progress through all natural Rollout States (such as RUNNING ->SUCCEEDED or RUNNING -> FAILED). If retriable errors are encountered duringthe rollout, the rollout will paused by default and can be resumed byre-requesting this RUN action.
Arguments for the action params.
Parameters for the RUN action controlling the behavior of the rollout when it isresumed from a PAUSED state.
--[no-]retry-failed-operations
If true, the rollout will retry failed operations when resumed. This isapplicable only the current state of the Rollout is PAUSED and the requestedaction is RUN. Use--retry-failed-operations to enable and--no-retry-failed-operations to disable.
Update labels.

At most one of these can be specified:

--labels=[LABELS,…]
Set labels to new value. The labels on the resource, which can be used forcategorization. similar to Kubernetes resource labels.
KEY
Keys must start with a lowercase character and contain only hyphens(-), underscores (_), lowercase characters, andnumbers.
VALUE
Values must contain only hyphens (-), underscores (_),lowercase characters, and numbers.
Shorthand Example:
--labels=string=string

JSON Example:

--labels='{"string": "string"}'

File Example:

--labels=path_to_file.(yaml|json)
--update-labels=[UPDATE_LABELS,…]
Update labels value or add key value pair. The labels on the resource, which canbe used for categorization. similar to Kubernetes resource labels.
KEY
Keys must start with a lowercase character and contain only hyphens(-), underscores (_), lowercase characters, andnumbers.
VALUE
Values must contain only hyphens (-), underscores (_),lowercase characters, and numbers.
Shorthand Example:
--update-labels=string=string

JSON Example:

--update-labels='{"string": "string"}'

File Example:

--update-labels=path_to_file.(yaml|json)
At most one of these can be specified:
--clear-labels
Clear labels value and set to empty map.
--remove-labels=REMOVE_LABELS
Remove existing value from map labels. Setsremove_labels value.Shorthand Example:
--remove-labels=string,string

JSON Example:

--remove-labels=["string"]

File Example:

--remove-labels=path_to_file.(yaml|json)
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.

API REFERENCE
This command uses thesaasservicemgmt/v1beta1 API. The fulldocumentation for this API can be found at:https://cloud.google.com/saas-runtime/docs
NOTES
This command is currently in beta and might change without notice.

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-10-07 UTC.