.TH "GCLOUD_BETA_BIGTABLE_APP\-PROFILES_CREATE" 1



.SH "NAME"
.HP
gcloud beta bigtable app\-profiles create \- create a new Bigtable app profile



.SH "SYNOPSIS"
.HP
\f5gcloud beta bigtable app\-profiles create\fR (\fIAPP_PROFILE\fR\ :\ \fB\-\-instance\fR=\fIINSTANCE\fR) ([\fB\-\-route\-any\fR\ :\ \fB\-\-restrict\-to\fR=[\fIRESTRICT_TO\fR,...]\ \fB\-\-row\-affinity\fR]\ |\ [\fB\-\-route\-to\fR=\fIROUTE_TO\fR\ :\ \fB\-\-transactional\-writes\fR]) [\fB\-\-description\fR=\fIDESCRIPTION\fR] [\fB\-\-force\fR] [\fB\-\-data\-boost\fR\ \fB\-\-data\-boost\-compute\-billing\-owner\fR=\fIDATA_BOOST_COMPUTE_BILLING_OWNER\fR\ |\ [\fB\-\-priority\fR=\fIPRIORITY\fR\ :\ \fB\-\-standard\fR]] [\fIGCLOUD_WIDE_FLAG\ ...\fR]



.SH "DESCRIPTION"

\fB(BETA)\fR Create a new Bigtable app profile.



.SH "EXAMPLES"

To create an app profile with a multi\-cluster routing policy, run:

.RS 2m
$ gcloud beta bigtable app\-profiles create my\-app\-profile\-id \e
    \-\-instance=my\-instance\-id \-\-route\-any
.RE

To create an app profile with a single\-cluster routing policy which routes all
requests to \f5my\-cluster\-id\fR, run:

.RS 2m
$ gcloud beta bigtable app\-profiles create \e
    my\-single\-cluster\-app\-profile \-\-instance=my\-instance\-id \e
    \-\-route\-to=my\-cluster\-id
.RE

To create an app profile with a friendly description, run:

.RS 2m
$ gcloud beta bigtable app\-profiles create my\-app\-profile\-id \e
    \-\-instance=my\-instance\-id \-\-route\-any \e
    \-\-description="Routes requests for my use case"
.RE

To create an app profile with a request priority of PRIORITY_MEDIUM, run:

.RS 2m
$ gcloud beta bigtable app\-profiles create my\-app\-profile\-id \e
    \-\-instance=my\-instance\-id \-\-route\-any \-\-priority=PRIORITY_MEDIUM
.RE

To create an app profile with Data Boost enabled which bills usage to the host
project, run:

.RS 2m
$ gcloud beta bigtable app\-profiles create my\-app\-profile\-id \e
    \-\-instance=my\-instance\-id \-\-data\-boost \e
    \-\-data\-boost\-compute\-billing\-owner=HOST_PAYS
.RE

To create an app profile with row\-affinity routing enabled, run:

.RS 2m
$ gcloud beta bigtable app\-profiles create my\-app\-profile\-id \e
    \-\-instance=my\-instance\-id \-\-route\-any \-\-row\-affinity
.RE



.SH "POSITIONAL ARGUMENTS"

.RS 2m
.TP 2m

App profile resource \- The app profile to create. 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 \f5app_profile\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
\fIAPP_PROFILE\fR

ID of the app profile or fully qualified identifier for the app profile.

To set the \f5name\fR attribute:
.RS 2m
.IP "\(bu" 2m
provide the argument \f5app_profile\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\-\-instance\fR=\fIINSTANCE\fR

Bigtable instance for the app profile.

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


.RE
.RE
.sp

.SH "REQUIRED FLAGS"

.RS 2m
.TP 2m

Exactly one of these must be specified:


.RS 2m
.TP 2m

Multi Cluster Routing Policy


.RS 2m
.TP 2m
\fB\-\-route\-any\fR

Use Multi Cluster Routing policy.

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

.TP 2m
\fB\-\-restrict\-to\fR=[\fIRESTRICT_TO\fR,...]

Cluster IDs to route to using the Multi Cluster Routing Policy. If unset, all
clusters in the instance are eligible.

.TP 2m
\fB\-\-row\-affinity\fR

Use row\-affinity routing for this app profile.

.RE
.sp
.TP 2m

Single Cluster Routing Policy


.RS 2m
.TP 2m
\fB\-\-route\-to\fR=\fIROUTE_TO\fR

Cluster ID to route to using Single Cluster Routing policy.

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

.TP 2m
\fB\-\-transactional\-writes\fR

Allow transactional writes with a Single Cluster Routing policy.


.RE
.RE
.RE
.sp

.SH "OPTIONAL FLAGS"

.RS 2m
.TP 2m
\fB\-\-description\fR=\fIDESCRIPTION\fR

Friendly name of the app profile.

.TP 2m
\fB\-\-force\fR

Ignore warnings and force create.

.TP 2m

At most one of these can be specified:


.RS 2m
.TP 2m

Data Boost Read\-only Isolation


.RS 2m
.TP 2m
\fB\-\-data\-boost\fR

Use Data Boost serverless compute option, rather than standard provisioned node
compute. If specified, \-\-data\-boost\-compute\-billing\-owner is required.
Specifying Data Boost compute on an app profile that uses standard provisioned
node compute may cause unexpected behavior for running applications.

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

.TP 2m
\fB\-\-data\-boost\-compute\-billing\-owner\fR=\fIDATA_BOOST_COMPUTE_BILLING_OWNER\fR

Specify the Data Boost compute billing owner, required if \-\-data\-boost is
passed. \fIDATA_BOOST_COMPUTE_BILLING_OWNER\fR must be (only one value is
supported):

.RS 2m
.TP 2m
\fBHOST_PAYS\fR
Compute billing should be accounted towards the host Cloud project (containing
the targeted Bigtable instance / table).
.RE
.sp


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

.RE
.sp
.TP 2m

Standard Isolation


.RS 2m
.TP 2m
\fB\-\-priority\fR=\fIPRIORITY\fR

Specify the request priority under standard provisioned node compute
capabilities. Passing this option implies standard provisioned node compute,
e.g. the \f5\-\-standard\fR option. If not specified, the app profile uses
standard provisioned node compute with PRIORITY_HIGH by default. Specifying
request priority on an app profile that has Data Boost serverless compute
enabled changes the compute option to standard and uses the specified priority,
which might cause unexpected behavior for running applications. \fIPRIORITY\fR
must be one of:

.RS 2m
.TP 2m
\fBPRIORITY_HIGH\fR
Requests are treated with high priority.
.TP 2m
\fBPRIORITY_LOW\fR
Requests are treated with low priority.
.TP 2m
\fBPRIORITY_MEDIUM\fR
Requests are treated with medium priority.
.RE
.sp


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

.TP 2m
\fB\-\-standard\fR

Use standard provisioned node compute option, rather than Data Boost compute
option. If specified, \f5\-\-priority\fR is required.


.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 "NOTES"

This command is currently in beta and might change without notice. These
variants are also available:

.RS 2m
$ gcloud bigtable app\-profiles create
.RE

.RS 2m
$ gcloud alpha bigtable app\-profiles create
.RE