- NAME
-
- gcloud beta saas-runtime rollout-kinds update - update a Rollout Type
- SYNOPSIS
-
-
gcloud beta saas-runtime rollout-kinds update
(ROLLOUT_KIND
:--location
=LOCATION
) [--rollout-orchestration-strategy
=ROLLOUT_ORCHESTRATION_STRATEGY
] [--unit-filter
=UNIT_FILTER
] [--update-unit-kind-strategy
=UPDATE_UNIT_KIND_STRATEGY
] [--clear-error-budget
--error-budget-allowed-count
=ERROR_BUDGET_ALLOWED_COUNT
--error-budget-allowed-percentage
=ERROR_BUDGET_ALLOWED_PERCENTAGE
] [--labels
=[LABELS
,…] |--update-labels
=[UPDATE_LABELS
,…]--clear-labels
|--remove-labels
=[__REMOVE_LABELS,…]] [GCLOUD_WIDE_FLAG …
]
-
- DESCRIPTION
-
(BETA)
Update a Rollout Type - EXAMPLES
-
To update the Rollout Type, run:
gcloud beta saas-runtime rollout-kinds update
- POSITIONAL ARGUMENTS
-
-
RolloutKindId resource - Identifier. The resource name (full URI of the
resource) following the standard naming scheme:
"projects/{project}/locations/{location}/rolloutKinds/{rollout_kind_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_kind
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_KIND
-
ID of the rolloutKindId or fully qualified identifier for the rolloutKindId.
To set the
rollout_kind
attribute:-
provide the argument
rollout_kind
on the command line.
This positional argument must be specified if any of the other arguments in this group are specified.
-
provide the argument
--location
=LOCATION
-
Location ID
To set the
location
attribute:-
provide the argument
rollout_kind
on the command line with a fully specified name; -
provide the argument
--location
on the command line.
-
provide the argument
-
provide the argument
-
RolloutKindId resource - Identifier. The resource name (full URI of the
resource) following the standard naming scheme:
- FLAGS
-
--rollout-orchestration-strategy
=ROLLOUT_ORCHESTRATION_STRATEGY
- The strategy to use for executing rollouts.
--unit-filter
=UNIT_FILTER
- AIP/160 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.
--update-unit-kind-strategy
=UPDATE_UNIT_KIND_STRATEGY
-
The config for updating the unit kind. By default, the unit kind will be updated
on the rollout start.
UPDATE_UNIT_KIND_STRATEGY
must be one of:never
- Never update the unit kind.
on-start
- Update the unit kind strategy on the rollout start.
-
Arguments for the error budget.
-
The configuration for error budget. If the number of failed units exceeds
max(allowed_count, allowed_ratio * total_units), the rollout will be paused.
--clear-error-budget
- Set rolloutKind.errorBudget back to default value.
--error-budget-allowed-count
=ERROR_BUDGET_ALLOWED_COUNT
- The maximum number of failed units allowed in a location without pausing the rollout.
--error-budget-allowed-percentage
=ERROR_BUDGET_ALLOWED_PERCENTAGE
- The maximum percentage of units allowed to fail (0, 100] within a location without pausing the rollout.
-
The configuration for error budget. If the number of failed units exceeds
max(allowed_count, allowed_ratio * total_units), the rollout will be paused.
-
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.
- 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 the
saasservicemgmt/v1beta1
API. The full documentation for this API can be found at: https://cloud.google.com/ - NOTES
- This command is currently in beta and might change without notice.
gcloud beta saas-runtime rollout-kinds update
Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License, and code samples are licensed under the Apache 2.0 License. For details, see the Google Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.
Last updated 2025-03-25 UTC.