.TH "GCLOUD_ALPHA_MANAGED\-FLINK_DEPLOYMENTS_CREATE" 1



.SH "NAME"
.HP
gcloud alpha managed\-flink deployments create \- create a BigQuery Engine for Apache Flink deployment



.SH "SYNOPSIS"
.HP
\f5gcloud alpha managed\-flink deployments create\fR (\fIDEPLOYMENT\fR\ :\ \fB\-\-location\fR=\fILOCATION\fR) \fB\-\-max\-slots\fR=\fIMAX_SLOTS\fR [\fB\-\-async\fR] [\fB\-\-display\-name\fR=\fIDISPLAY_NAME\fR] [\fB\-\-workload\-identity\fR=\fIWORKLOAD_IDENTITY\fR] [\fB\-\-network\-config\-subnetwork\fR=\fINETWORK_CONFIG_SUBNETWORK\fR\ \fB\-\-network\-config\-vpc\fR=\fINETWORK_CONFIG_VPC\fR] [\fIGCLOUD_WIDE_FLAG\ ...\fR]



.SH "DESCRIPTION"

\fB(ALPHA)\fR Create a BigQuery Engine for Apache Flink deployment.



.SH "EXAMPLES"

To create a BigQuery Engine for Apache Flink deployment, run:

.RS 2m
$ gcloud alpha managed\-flink deployments create my\-deployment \e
  \-\-location=us\-central1
.RE

To create a BigQuery Engine for Apache Flink deployment with all optional
parameters set, run:

.RS 2m
$ gcloud alpha managed\-flink deployments create my\-deployment \e
  \-\-location=us\-central1 \-\-max\-slots=100 \e
  \-\-network\-config\-vpc=my\-vpc \e
  \-\-network\-config\-subnetwork=my\-subnetwork
.RE



.SH "POSITIONAL ARGUMENTS"

.RS 2m
.TP 2m

Deployment resource \- Identifies the deployment for which the command runs. 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 \f5project\fR attribute:
.RS 2m
.IP "\(em" 2m
provide the argument \f5deployment\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

This must be specified.


.RS 2m
.TP 2m
\fIDEPLOYMENT\fR

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

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

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

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

ID of the location of the Apache Flink for BigQuery resource. See
https://cloud.google.com/managed\-flink/docs/locations for a list of supported
locations.


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


.RE
.RE
.sp

.SH "REQUIRED FLAGS"

.RS 2m
.TP 2m
\fB\-\-max\-slots\fR=\fIMAX_SLOTS\fR

max slots of the Flink deployment.


.RE
.sp

.SH "OPTIONAL FLAGS"

.RS 2m
.TP 2m
\fB\-\-async\fR

Return immediately, without waiting for the operation in progress to complete.

.TP 2m
\fB\-\-display\-name\fR=\fIDISPLAY_NAME\fR

display name of the Flink deployment.

.TP 2m
\fB\-\-workload\-identity\fR=\fIWORKLOAD_IDENTITY\fR

The workload identity to use for the deployment. Managed Flink Default Workload
Identity will be used if not specified.

.TP 2m
\fB\-\-network\-config\-subnetwork\fR=\fINETWORK_CONFIG_SUBNETWORK\fR

subnetwork for the Flink deployment network config.

.TP 2m
\fB\-\-network\-config\-vpc\fR=\fINETWORK_CONFIG_VPC\fR

fully qualified VPC network for the Flink deployment network config. Formatted
as: projects/{project}/global/networks/{network_id}.


.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 \fBmanagedflink/v1alpha\fR API. The full documentation for
this API can be found at: https://cloud.google.com/managed\-flink/docs/overview



.SH "NOTES"

This command is currently in alpha and might change without notice. If this
command fails with API permission errors despite specifying the correct project,
you might be trying to access an API with an invitation\-only early access
allowlist.