feat(bigtableadmin): update the api

#### bigtableadmin:v2

The following keys were added:
- schemas.LogicalView.properties.deletionProtection.type (Total Keys: 1)

Author: yoshi-automation

docs/dyn/bigtableadmin_v2.projects.instances.appProfiles.html

@@ -123,7 +123,7 @@ <h3>Method Details</h3>
     &quot;rowAffinity&quot;: { # If enabled, Bigtable will route the request based on the row key of the request, rather than randomly. Instead, each row key will be assigned to a cluster, and will stick to that cluster. If clusters are added or removed, then this may affect which row keys stick to which clusters. To avoid this, users can use a cluster group to specify which clusters are to be used. In this case, new clusters that are not a part of the cluster group will not be routed to, and routing will be unaffected by the new cluster. Moreover, clusters specified in the cluster group cannot be deleted unless removed from the cluster group. # Row affinity sticky routing based on the row key of the request. Requests that span multiple rows are routed non-deterministically.
     },
   },
-  &quot;name&quot;: &quot;A String&quot;, # The unique name of the app profile. Values are of the form `projects/{project}/instances/{instance}/appProfiles/_a-zA-Z0-9*`.
+  &quot;name&quot;: &quot;A String&quot;, # The 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*`.
   &quot;priority&quot;: &quot;A String&quot;, # This 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.
   &quot;singleClusterRouting&quot;: { # Unconditionally routes all read/write requests to a specific cluster. This option preserves read-your-writes consistency but does not improve availability. # Use a single-cluster routing policy.
     &quot;allowTransactionalWrites&quot;: True or False, # Whether or not `CheckAndMutateRow` and `ReadModifyWriteRow` requests are allowed by this app profile. It is unsafe to send these requests to the same table/row/column in multiple clusters.
@@ -157,7 +157,7 @@ <h3>Method Details</h3>
     &quot;rowAffinity&quot;: { # If enabled, Bigtable will route the request based on the row key of the request, rather than randomly. Instead, each row key will be assigned to a cluster, and will stick to that cluster. If clusters are added or removed, then this may affect which row keys stick to which clusters. To avoid this, users can use a cluster group to specify which clusters are to be used. In this case, new clusters that are not a part of the cluster group will not be routed to, and routing will be unaffected by the new cluster. Moreover, clusters specified in the cluster group cannot be deleted unless removed from the cluster group. # Row affinity sticky routing based on the row key of the request. Requests that span multiple rows are routed non-deterministically.
     },
   },
-  &quot;name&quot;: &quot;A String&quot;, # The unique name of the app profile. Values are of the form `projects/{project}/instances/{instance}/appProfiles/_a-zA-Z0-9*`.
+  &quot;name&quot;: &quot;A String&quot;, # The 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*`.
   &quot;priority&quot;: &quot;A String&quot;, # This 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.
   &quot;singleClusterRouting&quot;: { # Unconditionally routes all read/write requests to a specific cluster. This option preserves read-your-writes consistency but does not improve availability. # Use a single-cluster routing policy.
     &quot;allowTransactionalWrites&quot;: True or False, # Whether or not `CheckAndMutateRow` and `ReadModifyWriteRow` requests are allowed by this app profile. It is unsafe to send these requests to the same table/row/column in multiple clusters.
@@ -215,7 +215,7 @@ <h3>Method Details</h3>
     &quot;rowAffinity&quot;: { # If enabled, Bigtable will route the request based on the row key of the request, rather than randomly. Instead, each row key will be assigned to a cluster, and will stick to that cluster. If clusters are added or removed, then this may affect which row keys stick to which clusters. To avoid this, users can use a cluster group to specify which clusters are to be used. In this case, new clusters that are not a part of the cluster group will not be routed to, and routing will be unaffected by the new cluster. Moreover, clusters specified in the cluster group cannot be deleted unless removed from the cluster group. # Row affinity sticky routing based on the row key of the request. Requests that span multiple rows are routed non-deterministically.
     },
   },
-  &quot;name&quot;: &quot;A String&quot;, # The unique name of the app profile. Values are of the form `projects/{project}/instances/{instance}/appProfiles/_a-zA-Z0-9*`.
+  &quot;name&quot;: &quot;A String&quot;, # The 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*`.
   &quot;priority&quot;: &quot;A String&quot;, # This 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.
   &quot;singleClusterRouting&quot;: { # Unconditionally routes all read/write requests to a specific cluster. This option preserves read-your-writes consistency but does not improve availability. # Use a single-cluster routing policy.
     &quot;allowTransactionalWrites&quot;: True or False, # Whether or not `CheckAndMutateRow` and `ReadModifyWriteRow` requests are allowed by this app profile. It is unsafe to send these requests to the same table/row/column in multiple clusters.
@@ -258,7 +258,7 @@ <h3>Method Details</h3>
         &quot;rowAffinity&quot;: { # If enabled, Bigtable will route the request based on the row key of the request, rather than randomly. Instead, each row key will be assigned to a cluster, and will stick to that cluster. If clusters are added or removed, then this may affect which row keys stick to which clusters. To avoid this, users can use a cluster group to specify which clusters are to be used. In this case, new clusters that are not a part of the cluster group will not be routed to, and routing will be unaffected by the new cluster. Moreover, clusters specified in the cluster group cannot be deleted unless removed from the cluster group. # Row affinity sticky routing based on the row key of the request. Requests that span multiple rows are routed non-deterministically.
         },
       },
-      &quot;name&quot;: &quot;A String&quot;, # The unique name of the app profile. Values are of the form `projects/{project}/instances/{instance}/appProfiles/_a-zA-Z0-9*`.
+      &quot;name&quot;: &quot;A String&quot;, # The 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*`.
       &quot;priority&quot;: &quot;A String&quot;, # This 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.
       &quot;singleClusterRouting&quot;: { # Unconditionally routes all read/write requests to a specific cluster. This option preserves read-your-writes consistency but does not improve availability. # Use a single-cluster routing policy.
         &quot;allowTransactionalWrites&quot;: True or False, # Whether or not `CheckAndMutateRow` and `ReadModifyWriteRow` requests are allowed by this app profile. It is unsafe to send these requests to the same table/row/column in multiple clusters.
@@ -295,7 +295,7 @@ <h3>Method Details</h3>
   <pre>Updates an app profile within an instance.
 
 Args:
-  name: string, The unique name of the app profile. Values are of the form `projects/{project}/instances/{instance}/appProfiles/_a-zA-Z0-9*`. (required)
+  name: string, The 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*`. (required)
   body: object, The request body.
     The object takes the form of:
 
@@ -312,7 +312,7 @@ <h3>Method Details</h3>
     &quot;rowAffinity&quot;: { # If enabled, Bigtable will route the request based on the row key of the request, rather than randomly. Instead, each row key will be assigned to a cluster, and will stick to that cluster. If clusters are added or removed, then this may affect which row keys stick to which clusters. To avoid this, users can use a cluster group to specify which clusters are to be used. In this case, new clusters that are not a part of the cluster group will not be routed to, and routing will be unaffected by the new cluster. Moreover, clusters specified in the cluster group cannot be deleted unless removed from the cluster group. # Row affinity sticky routing based on the row key of the request. Requests that span multiple rows are routed non-deterministically.
     },
   },
-  &quot;name&quot;: &quot;A String&quot;, # The unique name of the app profile. Values are of the form `projects/{project}/instances/{instance}/appProfiles/_a-zA-Z0-9*`.
+  &quot;name&quot;: &quot;A String&quot;, # The 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*`.
   &quot;priority&quot;: &quot;A String&quot;, # This 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.
   &quot;singleClusterRouting&quot;: { # Unconditionally routes all read/write requests to a specific cluster. This option preserves read-your-writes consistency but does not improve availability. # Use a single-cluster routing policy.
     &quot;allowTransactionalWrites&quot;: True or False, # Whether or not `CheckAndMutateRow` and `ReadModifyWriteRow` requests are allowed by this app profile. It is unsafe to send these requests to the same table/row/column in multiple clusters.

docs/dyn/bigtableadmin_v2.projects.instances.logicalViews.html

@@ -120,6 +120,7 @@ <h3>Method Details</h3>
     The object takes the form of:
 
 { # A SQL logical view object that can be referenced in SQL queries.
+  &quot;deletionProtection&quot;: True or False, # Optional. Set to true to make the LogicalView protected against deletion.
   &quot;etag&quot;: &quot;A String&quot;, # Optional. The etag for this logical view. This may be sent on update requests to ensure that the client has an up-to-date value before proceeding. The server returns an ABORTED error on a mismatched etag.
   &quot;name&quot;: &quot;A String&quot;, # Identifier. The unique name of the logical view. Format: `projects/{project}/instances/{instance}/logicalViews/{logical_view}`
   &quot;query&quot;: &quot;A String&quot;, # Required. The logical view&#x27;s select query.
@@ -189,6 +190,7 @@ <h3>Method Details</h3>
   An object of the form:
 
     { # A SQL logical view object that can be referenced in SQL queries.
+  &quot;deletionProtection&quot;: True or False, # Optional. Set to true to make the LogicalView protected against deletion.
   &quot;etag&quot;: &quot;A String&quot;, # Optional. The etag for this logical view. This may be sent on update requests to ensure that the client has an up-to-date value before proceeding. The server returns an ABORTED error on a mismatched etag.
   &quot;name&quot;: &quot;A String&quot;, # Identifier. The unique name of the logical view. Format: `projects/{project}/instances/{instance}/logicalViews/{logical_view}`
   &quot;query&quot;: &quot;A String&quot;, # Required. The logical view&#x27;s select query.
@@ -270,6 +272,7 @@ <h3>Method Details</h3>
     { # Response message for BigtableInstanceAdmin.ListLogicalViews.
   &quot;logicalViews&quot;: [ # The list of requested logical views.
     { # A SQL logical view object that can be referenced in SQL queries.
+      &quot;deletionProtection&quot;: True or False, # Optional. Set to true to make the LogicalView protected against deletion.
       &quot;etag&quot;: &quot;A String&quot;, # Optional. The etag for this logical view. This may be sent on update requests to ensure that the client has an up-to-date value before proceeding. The server returns an ABORTED error on a mismatched etag.
       &quot;name&quot;: &quot;A String&quot;, # Identifier. The unique name of the logical view. Format: `projects/{project}/instances/{instance}/logicalViews/{logical_view}`
       &quot;query&quot;: &quot;A String&quot;, # Required. The logical view&#x27;s select query.
@@ -303,6 +306,7 @@ <h3>Method Details</h3>
     The object takes the form of:
 
 { # A SQL logical view object that can be referenced in SQL queries.
+  &quot;deletionProtection&quot;: True or False, # Optional. Set to true to make the LogicalView protected against deletion.
   &quot;etag&quot;: &quot;A String&quot;, # Optional. The etag for this logical view. This may be sent on update requests to ensure that the client has an up-to-date value before proceeding. The server returns an ABORTED error on a mismatched etag.
   &quot;name&quot;: &quot;A String&quot;, # Identifier. The unique name of the logical view. Format: `projects/{project}/instances/{instance}/logicalViews/{logical_view}`
   &quot;query&quot;: &quot;A String&quot;, # Required. The logical view&#x27;s select query.

googleapiclient/discovery_cache/documents/bigtableadmin.v2.json

@@ -695,7 +695,7 @@
 "type": "boolean"
 },
 "name": {
-"description": "The unique name of the app profile. Values are of the form `projects/{project}/instances/{instance}/appProfiles/_a-zA-Z0-9*`.",
+"description": "The 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*`.",
 "location": "path",
 "pattern": "^projects/[^/]+/instances/[^/]+/appProfiles/[^/]+$",
 "required": true,
@@ -2777,7 +2777,7 @@
 }
 }
 },
-"revision": "20250410",
+"revision": "20250430",
 "rootUrl": "https://bigtableadmin.googleapis.com/",
 "schemas": {
 "AppProfile": {
@@ -2801,7 +2801,7 @@
 "description": "Use a multi-cluster routing policy."
 },
 "name": {
-"description": "The unique name of the app profile. Values are of the form `projects/{project}/instances/{instance}/appProfiles/_a-zA-Z0-9*`.",
+"description": "The 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*`.",
 "type": "string"
 },
 "priority": {
@@ -4541,6 +4541,10 @@
 "description": "A SQL logical view object that can be referenced in SQL queries.",
 "id": "LogicalView",
 "properties": {
+"deletionProtection": {
+"description": "Optional. Set to true to make the LogicalView protected against deletion.",
+"type": "boolean"
+},
 "etag": {
 "description": "Optional. The etag for this logical view. This may be sent on update requests to ensure that the client has an up-to-date value before proceeding. The server returns an ABORTED error on a mismatched etag.",
 "type": "string"