gcloud beta saas-runtime rollouts update

Stay organized with collections Save and categorize content based on your preferences.

gcloud beta saas-runtime rollouts update - update a Rollout

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 …]

RolloutId resource - Identifier. The resource name (full URI of the resource) following the standard naming scheme:

"projects/{project}/locations/{location}/rollout/{rollout_id}" 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 rollout 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.

ROLLOUT

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

To set the rollout attribute:

• provide the argument rollout on the command line.

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

--location=LOCATION

Location ID

To set the location attribute:

• provide the argument rollout on the command line with a fully specified name;
• provide the argument --location on the command line.

--rollout-orchestration-strategy=ROLLOUT_ORCHESTRATION_STRATEGY

The strategy to use for executing this rollout. If not provided, the strategy from 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. This filter can only reduce, but not expand the scope of the rollout. If not provided, the unit_filter from the RolloutType will be used.

RolloutControl provides a way to request a change to the execution of a Rollout by 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 the rollout 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 requested to run will progress through all natural Rollout States (such as RUNNING -> SUCCEEDED or RUNNING -> FAILED). If retriable errors are encountered during the rollout, the rollout will paused by default and can be resumed by re-requesting this RUN action.

Arguments for the action params.

Parameters for the RUN action controlling the behavior of the rollout when it is resumed from a PAUSED state.

--[no-]retry-failed-operations

If true, the rollout will retry failed operations when resumed. This is applicable only the current state of the Rollout is PAUSED and the requested action 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 for categorization. similar to Kubernetes resource labels.

KEY

Keys must start with a lowercase character and contain only hyphens (-), underscores (_), lowercase characters, and numbers.

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 can be used for categorization. similar to Kubernetes resource labels.

KEY

Keys must start with a lowercase character and contain only hyphens (-), underscores (_), lowercase characters, and numbers.

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.

Run $ gcloud help for details.