An App Profile in Google Cloud is a configuration for a Cloud Bigtable instance that defines how requests are routed to clusters. It allows you to control aspects such as multi-cluster routing, failover behavior, and application isolation. By using different app profiles, you can optimize performance, availability, and workload management for various applications accessing the same Bigtable instance.

gcp.bigtableadmin_app_profile

Fields

TitleIDTypeData TypeDescription
_keycorestring
ancestorscorearray<string>
data_boost_isolation_read_onlycorejsonSpecifies that this app profile is intended for read-only usage via the Data Boost feature.
datadog_display_namecorestring
descriptioncorestringLong form description of the use case for this AppProfile.
etagcorestringStrongly validated etag for optimistic concurrency control. Preserve the value returned from `GetAppProfile` when calling `UpdateAppProfile` to fail the request if there has been a modification in the mean time. The `update_mask` of the request need not include `etag` for this protection to apply. See [Wikipedia](https://en.wikipedia.org/wiki/HTTP_ETag) and [RFC 7232](https://tools.ietf.org/html/rfc7232#section-2.3) for more details.
labelscorearray<string>
multi_cluster_routing_use_anycorejsonUse a multi-cluster routing policy.
namecorestringThe unique name of the app profile, up to 50 characters long. Values are of the form `projects/{project}/instances/{instance}/appProfiles/_a-zA-Z0-9*`.
organization_idcorestring
parentcorestring
prioritycorestringThis field has been deprecated in favor of `standard_isolation.priority`. If you set this field, `standard_isolation.priority` will be set instead. The priority of requests sent using this app profile.
project_idcorestring
project_numbercorestring
region_idcorestring
resource_namecorestring
single_cluster_routingcorejsonUse a single-cluster routing policy.
standard_isolationcorejsonThe standard options used for isolating this app profile's traffic from other use cases.
tagscorehstore_csv
zone_idcorestring