.TH "GCLOUD_BETA_SAAS\-RUNTIME_ROLLOUTS_CREATE" 1



.SH "NAME"
.HP
gcloud beta saas\-runtime rollouts create \- create a Rollout



.SH "SYNOPSIS"
.HP
\f5gcloud beta saas\-runtime rollouts create\fR \fIROLLOUT\fR \fB\-\-release\fR=\fIRELEASE\fR [\fB\-\-labels\fR=[\fILABELS\fR,...]] [\fB\-\-location\fR=\fILOCATION\fR] [\fB\-\-rollout\-kind\fR=\fIROLLOUT_KIND\fR] [\fB\-\-rollout\-orchestration\-strategy\fR=\fIROLLOUT_ORCHESTRATION_STRATEGY\fR] [\fB\-\-unit\-filter\fR=\fIUNIT_FILTER\fR] [\fB\-\-control\-action\fR=\fICONTROL_ACTION\fR\ :\ \fB\-\-[no\-]retry\-failed\-operations\fR] [\fIGCLOUD_WIDE_FLAG\ ...\fR]



.SH "DESCRIPTION"

\fB(BETA)\fR Create a Rollout



.SH "EXAMPLES"

To create the Rollout, run:

.RS 2m
$ gcloud beta saas\-runtime rollouts create
.RE



.SH "POSITIONAL ARGUMENTS"

.RS 2m
.TP 2m

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

.RS 2m
"projects/{project}/locations/{location}/rollout/{rollout_id}" This represents a Cloud resource. (NOTE) Some attributes are not given arguments in this group but can be set in other ways.
.RE

To set the \f5project\fR attribute:
.RS 2m
.IP "\(em" 2m
provide the argument \f5rollout\fR on the command line with a fully specified
name;
.IP "\(em" 2m
provide the argument \f5\-\-project\fR on the command line;
.IP "\(em" 2m
set the property \f5core/project\fR.
.RE
.sp

To set the \f5location\fR attribute:
.RS 2m
.IP "\(em" 2m
provide the argument \f5rollout\fR on the command line with a fully specified
name;
.IP "\(em" 2m
provide the argument \f5\-\-location\fR on the command line.
.RE
.sp

This must be specified.


.RS 2m
.TP 2m
\fIROLLOUT\fR

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

To set the \f5rollout\fR attribute:
.RS 2m
.IP "\(bu" 2m
provide the argument \f5rollout\fR on the command line.
.RE
.sp


.RE
.RE
.sp

.SH "REQUIRED FLAGS"

.RS 2m
.TP 2m
\fB\-\-release\fR=\fIRELEASE\fR

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

To set the \f5release\fR attribute:
.RS 2m
.IP "\(em" 2m
provide the argument \f5\-\-release\fR on the command line.
.RE
.sp


.RE
.sp

.SH "OPTIONAL FLAGS"

.RS 2m
.TP 2m
\fB\-\-labels\fR=[\fILABELS\fR,...]

The labels on the resource, which can be used for categorization. similar to
Kubernetes resource labels.

.RS 2m
.TP 2m
\fBKEY\fR
Keys must start with a lowercase character and contain only hyphens (\f5\-\fR),
underscores (\f5_\fR), lowercase characters, and numbers.

.TP 2m
\fBVALUE\fR
Values must contain only hyphens (\f5\-\fR), underscores (\f5_\fR), lowercase
characters, and numbers.

.RE
.sp
\fBShorthand Example:\fR


.RS 2m
\-\-labels=string=string
.RE


\fBJSON Example:\fR


.RS 2m
\-\-labels='{"string": "string"}'
.RE


\fBFile Example:\fR


.RS 2m
\-\-labels=path_to_file.(yaml|json)
.RE


.TP 2m
\fB\-\-location\fR=\fILOCATION\fR

For resources [release, rollout, rollout\-kind], provides fallback value for
resource location attribute. When the resource's full URI path is not provided,
location will fallback to this flag value.

.TP 2m

RolloutKindId resource \- Name of the RolloutKind this rollout is stemming from
and adhering to. This represents a Cloud resource. (NOTE) Some attributes are
not given arguments in this group but can be set in other ways.

To set the \f5project\fR attribute:
.RS 2m
.IP "\(em" 2m
provide the argument \f5\-\-rollout\-kind\fR on the command line with a fully
specified name;
.IP "\(em" 2m
provide the argument \f5\-\-project\fR on the command line;
.IP "\(em" 2m
set the property \f5core/project\fR.
.RE
.sp

To set the \f5location\fR attribute:
.RS 2m
.IP "\(em" 2m
provide the argument \f5\-\-rollout\-kind\fR on the command line with a fully
specified name;
.IP "\(em" 2m
provide the argument \f5\-\-location\fR on the command line.
.RE
.sp


.RS 2m
.TP 2m
\fB\-\-rollout\-kind\fR=\fIROLLOUT_KIND\fR

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

To set the \f5rollout\-kind\fR attribute:
.RS 2m
.IP "\(bu" 2m
provide the argument \f5\-\-rollout\-kind\fR on the command line.
.RE
.sp

.RE
.sp
.TP 2m
\fB\-\-rollout\-orchestration\-strategy\fR=\fIROLLOUT_ORCHESTRATION_STRATEGY\fR

The strategy to use for executing this rollout. If not provided, the strategy
from Rollout Type will be used.

.TP 2m
\fB\-\-unit\-filter\fR=\fIUNIT_FILTER\fR

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.

.TP 2m

RolloutControl provides a way to request a change to the execution of a Rollout
by pausing or canceling it.


.RS 2m
.TP 2m
\fB\-\-control\-action\fR=\fICONTROL_ACTION\fR

Action to be performed on the Rollout. The default behavior is to run the
rollout until it naturally reaches a terminal state. \fICONTROL_ACTION\fR must
be one of:

.RS 2m
.TP 2m
\fBcancel\fR
Cancel the Rollout permanently.
.TP 2m
\fBpause\fR
Pause the Rollout until it is resumed (i.e. RUN is requested).
.TP 2m
\fBrun\fR
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.
.RE
.sp


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

.TP 2m

Arguments for the action params.


.RS 2m
.TP 2m

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


.RS 2m
.TP 2m
\fB\-\-[no\-]retry\-failed\-operations\fR

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 \fB\-\-retry\-failed\-operations\fR to enable and
\fB\-\-no\-retry\-failed\-operations\fR to disable.


.RE
.RE
.RE
.RE
.sp

.SH "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 \fB$ gcloud help\fR for details.



.SH "API REFERENCE"

This command uses the \fBsaasservicemgmt/v1beta1\fR API. The full documentation
for this API can be found at: https://cloud.google.com/saas\-runtime/docs



.SH "NOTES"

This command is currently in beta and might change without notice.