NAME gcloud alpha bigtable app-profiles create - create a new Bigtable app profile SYNOPSIS gcloud alpha bigtable app-profiles create (APP_PROFILE : --instance=INSTANCE) ([--route-any : --restrict-to=[RESTRICT_TO,...] --row-affinity] | [--route-to=ROUTE_TO : --transactional-writes]) [--description=DESCRIPTION] [--force] [--data-boost --data-boost-compute-billing-owner=DATA_BOOST_COMPUTE_BILLING_OWNER | [--priority=PRIORITY : --standard]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Create a new Bigtable app profile. EXAMPLES To create an app profile with a multi-cluster routing policy, run: $ gcloud alpha bigtable app-profiles create my-app-profile-id \ --instance=my-instance-id --route-any To create an app profile with a single-cluster routing policy which routes all requests to my-cluster-id, run: $ gcloud alpha bigtable app-profiles create \ my-single-cluster-app-profile --instance=my-instance-id \ --route-to=my-cluster-id To create an app profile with a friendly description, run: $ gcloud alpha bigtable app-profiles create my-app-profile-id \ --instance=my-instance-id --route-any \ --description="Routes requests for my use case" To create an app profile with a request priority of PRIORITY_MEDIUM, run: $ gcloud alpha bigtable app-profiles create my-app-profile-id \ --instance=my-instance-id --route-any --priority=PRIORITY_MEDIUM To create an app profile with Data Boost enabled which bills usage to the host project, run: $ gcloud alpha bigtable app-profiles create my-app-profile-id \ --instance=my-instance-id --data-boost \ --data-boost-compute-billing-owner=HOST_PAYS To create an app profile with row-affinity routing enabled, run: $ gcloud alpha bigtable app-profiles create my-app-profile-id \ --instance=my-instance-id --route-any --row-affinity POSITIONAL ARGUMENTS 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 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. REQUIRED FLAGS Exactly one of these must 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. --row-affinity Use row-affinity routing for this app profile. 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. OPTIONAL FLAGS --description=DESCRIPTION Friendly name of the app profile. --force Ignore warnings and force create. At most one of these can be specified: Data Boost Read-only Isolation --data-boost Use Data Boost Read-only Isolation, rather than Standard Isolation. If specified, --data-boost-compute-billing-owner is required. Specifying Data Boost Read-only Isolation on an app profile which has Standard Isolation enabled 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 Isolation. Passing this option implies Standard Isolation, e.g. the --standard option. If not specified, the app profile uses Standard Isolation with PRIORITY_HIGH by default. Specifying request priority on an app profile that has Data Boost Read-Only Isolation enabled will change the isolation to Standard and use the specified priority, which may 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 Isolation, rather than Data Boost Read-only Isolation. If specified, --priority is required. 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. 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. These variants are also available: $ gcloud bigtable app-profiles create $ gcloud beta bigtable app-profiles create