Skip to content

Commit

Permalink
docs: Update cpu_utilization_percent limit (#547)
Browse files Browse the repository at this point in the history
- [ ] Regenerate this pull request now.

docs: Remove the limitation that all clusters in a CMEK instance must use the same key

PiperOrigin-RevId: 438385300

Source-Link: googleapis/googleapis@c59f02e

Source-Link: googleapis/googleapis-gen@04d03d1
Copy-Tag: eyJwIjoiLmdpdGh1Yi8uT3dsQm90LnlhbWwiLCJoIjoiMDRkMDNkMTdhYWZhN2I0NDIyZjczYzkzNjAwZjA0MDU0MjgxN2ZjZCJ9
  • Loading branch information
gcf-owl-bot[bot] committed Apr 3, 2022
1 parent 284b060 commit f008eea
Showing 1 changed file with 4 additions and 6 deletions.
10 changes: 4 additions & 6 deletions google/cloud/bigtable_admin_v2/types/instance.py
Expand Up @@ -121,10 +121,10 @@ class AutoscalingTargets(proto.Message):
Attributes:
cpu_utilization_percent (int):
The cpu utilization that the Autoscaler
should be trying to achieve. This number is on a
scale from 0 (no utilization) to 100 (total
utilization).
The cpu utilization that the Autoscaler should be trying to
achieve. This number is on a scale from 0 (no utilization)
to 100 (total utilization), and is limited between 10 and
80, otherwise it will return INVALID_ARGUMENT error.
"""

cpu_utilization_percent = proto.Field(
Expand Down Expand Up @@ -254,8 +254,6 @@ class EncryptionConfig(proto.Message):
key.
2) Only regional keys can be used and the region of the CMEK
key must match the region of the cluster.
3) All clusters within an instance must use the same CMEK
key.
"""

kms_key_name = proto.Field(
Expand Down

0 comments on commit f008eea

Please sign in to comment.