gcloud bigtable app-profiles update

gcloud bigtable app-profiles update - update a Bigtable app profile

gcloud bigtable app-profiles update (APP_PROFILE : --instance=INSTANCE) [--async] [--description=DESCRIPTION] [--force] [--data-boost --data-boost-compute-billing-owner=DATA_BOOST_COMPUTE_BILLING_OWNER     | [--priority=PRIORITY : --standard]] [[--route-any : --restrict-to=[RESTRICT_TO,…]]     | [--route-to=ROUTE_TO : --transactional-writes]] [GCLOUD_WIDE_FLAG …]

gcloud bigtable app-profiles update my-app-profile-id --instance=my-instance-id --route-any

To update an app profile to use a single-cluster routing policy that routes all requests to my-cluster-id and allows transactional writes, run:

gcloud bigtable app-profiles update my-app-profile-id --instance=my-instance-id --route-to=my-cluster-id --transactional-writes

To update the description for an app profile, run:

gcloud bigtable app-profiles update my-app-profile-id --instance=my-instance-id --description="New description"

To update the request priority for an app profile to PRIORITY_LOW, run:

gcloud bigtable app-profiles update my-app-profile-id --instance=my-instance-id --priority=PRIORITY_LOW

To update an app profile to enable Data Boost which bills usage to the host project, run:

gcloud bigtable app-profiles update my-app-profile-id --instance=my-instance-id --data-boost --data-boost-compute-billing-owner=HOST_PAYS

App profile resource - The app profile to update. 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 app_profile 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.

APP_PROFILE

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

To set the name attribute:

• provide the argument app_profile on the command line.

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

--instance=INSTANCE

Cloud Bigtable instance for the app profile.

To set the instance attribute:

• provide the argument app_profile on the command line with a fully specified name;
• provide the argument --instance on the command line.

--async

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

--description=DESCRIPTION

Friendly name of the app profile.

--force

Ignore warnings and force update.

At most one of these can be specified:

Data Boost Read-only Isolation

--data-boost

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.

--data-boost-compute-billing-owner=DATA_BOOST_COMPUTE_BILLING_OWNER

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

HOST_PAYS

Compute billing should be accounted towards the host Cloud project (containing the targeted Bigtable instance / table).

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

Standard Isolation

--priority=PRIORITY

Specify the request priority under standard provisioned node compute capabilities. Passing this option implies standard provisioned node compute, e.g. the --standard 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. PRIORITY must be one of:

PRIORITY_HIGH

Requests are treated with high priority.

PRIORITY_LOW

Requests are treated with low priority.

PRIORITY_MEDIUM

Requests are treated with medium priority.

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

--standard

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

At most one of these can be specified:

Multi Cluster Routing Policy

--route-any

Use Multi Cluster Routing policy.

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

--restrict-to=[RESTRICT_TO,…]

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

Single Cluster Routing Policy

--route-to=ROUTE_TO

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.

--transactional-writes

Allow transactional writes with a Single Cluster Routing policy.

Run $ gcloud help for details.