Skip to content
Permalink
Browse files
chore: Update discovery artifacts (#1603)
## Deleted keys were detected in the following stable discovery artifacts:
containeranalysis v1 618985b
documentai v1 3ba3182
recaptchaenterprise v1 ff95700

## Deleted keys were detected in the following pre-stable discovery artifacts:
containeranalysis v1alpha1 618985b
containeranalysis v1beta1 618985b
documentai v1beta3 3ba3182

## Discovery Artifact Change Summary:
feat(bigtableadmin): update the api be7ffcc
feat(chromemanagement): update the api 59c9799
feat(cloudasset): update the api 60f5758
feat(cloudfunctions): update the api c517033
feat(contactcenterinsights): update the api 9ac9faa
feat(containeranalysis): update the api 618985b
feat(datapipelines): update the api a39bb0f
feat(datastore): update the api 5050adb
feat(dialogflow): update the api fd46c12
feat(documentai): update the api 3ba3182
feat(drive): update the api b1840b0
feat(file): update the api b13a249
feat(gkehub): update the api 37cce48
feat(healthcare): update the api 8d1f955
feat(metastore): update the api 9c90df7
feat(monitoring): update the api bf890b6
feat(mybusinessbusinessinformation): update the api 90e206c
feat(paymentsresellersubscription): update the api c879654
feat(recaptchaenterprise): update the api ff95700
feat(recommender): update the api d85fe38
feat(securitycenter): update the api 35a6d4e
feat(speech): update the api 13f1bcb
feat(sqladmin): update the api 770bc14
feat(tpu): update the api ea30e3a
feat(vmmigration): update the api 80e2090
  • Loading branch information
yoshi-code-bot committed Nov 16, 2021
1 parent 5844ca2 commit 815c1ac7e3f7c7ea6df920645adb8cba84b05c22
Showing 589 changed files with 19,695 additions and 5,978 deletions.
@@ -295,7 +295,7 @@ <h3>Method Details</h3>
Allowed values
BASIC - Includes only the basic metadata fields (e.g., deviceId, serialNumber, status, and user)
FULL - Includes all metadata fields
query: string, Search string in the format given at http://support.google.com/chromeos/a/bin/answer.py?answer=1698333
query: string, Search string in the format given at https://developers.google.com/admin-sdk/directory/v1/list-query-operators
sortOrder: string, Whether to return results in ascending or descending order. Must be used with the `orderBy` parameter.
Allowed values
ASCENDING - Ascending order.

Large diffs are not rendered by default.

@@ -834,7 +834,7 @@ <h3>Method Details</h3>
The object takes the form of:

{ # Request message for pausing a finalized deal.
&quot;reason&quot;: &quot;A String&quot;, # The reason to pause the finalized deal, will be displayed to the seller. Maximum length is 1000 characters.
&quot;reason&quot;: &quot;A String&quot;, # Required. The reason to pause the finalized deal, will be displayed to the seller. Maximum length is 1000 characters.
}

x__xgafv: string, V1 error format.

Large diffs are not rendered by default.

@@ -119,6 +119,17 @@ <h3>Method Details</h3>
The object takes the form of:

{ # A resizable group of nodes in a particular cloud location, capable of serving all Tables in the parent Instance.
&quot;clusterConfig&quot;: { # Configuration for a cluster. # Configuration for this cluster.
&quot;clusterAutoscalingConfig&quot;: { # Autoscaling config for a cluster. # Autoscaling configuration for this cluster. Note that when creating or updating a cluster, exactly one of serve_nodes or cluster_autoscaling_config must be set. If serve_nodes is set, then serve_nodes is fixed and autoscaling is turned off. If cluster_autoscaling_config is set, then serve_nodes will be autoscaled.
&quot;autoscalingLimits&quot;: { # Limits for the number of nodes a Cluster can autoscale up/down to. # Required. Autoscaling limits for this cluster.
&quot;maxServeNodes&quot;: 42, # Required. Maximum number of nodes to scale up to.
&quot;minServeNodes&quot;: 42, # Required. Minimum number of nodes to scale down to.
},
&quot;autoscalingTargets&quot;: { # The Autoscaling targets for a Cluster. These determine the recommended nodes. # Required. Autoscaling targets for this cluster.
&quot;cpuUtilizationPercent&quot;: 42, # 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).
},
},
},
&quot;defaultStorageType&quot;: &quot;A String&quot;, # Immutable. The type of storage used by this cluster to serve its parent instance&#x27;s tables, unless explicitly overridden.
&quot;encryptionConfig&quot;: { # Cloud Key Management Service (Cloud KMS) settings for a CMEK-protected cluster. # Immutable. The encryption configuration for CMEK-protected clusters.
&quot;kmsKeyName&quot;: &quot;A String&quot;, # Describes the Cloud KMS encryption key that will be used to protect the destination Bigtable cluster. The requirements for this key are: 1) The Cloud Bigtable service account associated with the project that contains this cluster must be granted the `cloudkms.cryptoKeyEncrypterDecrypter` role on the CMEK 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. Values are of the form `projects/{project}/locations/{location}/keyRings/{keyring}/cryptoKeys/{key}`
@@ -192,6 +203,17 @@ <h3>Method Details</h3>
An object of the form:

{ # A resizable group of nodes in a particular cloud location, capable of serving all Tables in the parent Instance.
&quot;clusterConfig&quot;: { # Configuration for a cluster. # Configuration for this cluster.
&quot;clusterAutoscalingConfig&quot;: { # Autoscaling config for a cluster. # Autoscaling configuration for this cluster. Note that when creating or updating a cluster, exactly one of serve_nodes or cluster_autoscaling_config must be set. If serve_nodes is set, then serve_nodes is fixed and autoscaling is turned off. If cluster_autoscaling_config is set, then serve_nodes will be autoscaled.
&quot;autoscalingLimits&quot;: { # Limits for the number of nodes a Cluster can autoscale up/down to. # Required. Autoscaling limits for this cluster.
&quot;maxServeNodes&quot;: 42, # Required. Maximum number of nodes to scale up to.
&quot;minServeNodes&quot;: 42, # Required. Minimum number of nodes to scale down to.
},
&quot;autoscalingTargets&quot;: { # The Autoscaling targets for a Cluster. These determine the recommended nodes. # Required. Autoscaling targets for this cluster.
&quot;cpuUtilizationPercent&quot;: 42, # 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).
},
},
},
&quot;defaultStorageType&quot;: &quot;A String&quot;, # Immutable. The type of storage used by this cluster to serve its parent instance&#x27;s tables, unless explicitly overridden.
&quot;encryptionConfig&quot;: { # Cloud Key Management Service (Cloud KMS) settings for a CMEK-protected cluster. # Immutable. The encryption configuration for CMEK-protected clusters.
&quot;kmsKeyName&quot;: &quot;A String&quot;, # Describes the Cloud KMS encryption key that will be used to protect the destination Bigtable cluster. The requirements for this key are: 1) The Cloud Bigtable service account associated with the project that contains this cluster must be granted the `cloudkms.cryptoKeyEncrypterDecrypter` role on the CMEK 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. Values are of the form `projects/{project}/locations/{location}/keyRings/{keyring}/cryptoKeys/{key}`
@@ -221,6 +243,17 @@ <h3>Method Details</h3>
{ # Response message for BigtableInstanceAdmin.ListClusters.
&quot;clusters&quot;: [ # The list of requested clusters.
{ # A resizable group of nodes in a particular cloud location, capable of serving all Tables in the parent Instance.
&quot;clusterConfig&quot;: { # Configuration for a cluster. # Configuration for this cluster.
&quot;clusterAutoscalingConfig&quot;: { # Autoscaling config for a cluster. # Autoscaling configuration for this cluster. Note that when creating or updating a cluster, exactly one of serve_nodes or cluster_autoscaling_config must be set. If serve_nodes is set, then serve_nodes is fixed and autoscaling is turned off. If cluster_autoscaling_config is set, then serve_nodes will be autoscaled.
&quot;autoscalingLimits&quot;: { # Limits for the number of nodes a Cluster can autoscale up/down to. # Required. Autoscaling limits for this cluster.
&quot;maxServeNodes&quot;: 42, # Required. Maximum number of nodes to scale up to.
&quot;minServeNodes&quot;: 42, # Required. Minimum number of nodes to scale down to.
},
&quot;autoscalingTargets&quot;: { # The Autoscaling targets for a Cluster. These determine the recommended nodes. # Required. Autoscaling targets for this cluster.
&quot;cpuUtilizationPercent&quot;: 42, # 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).
},
},
},
&quot;defaultStorageType&quot;: &quot;A String&quot;, # Immutable. The type of storage used by this cluster to serve its parent instance&#x27;s tables, unless explicitly overridden.
&quot;encryptionConfig&quot;: { # Cloud Key Management Service (Cloud KMS) settings for a CMEK-protected cluster. # Immutable. The encryption configuration for CMEK-protected clusters.
&quot;kmsKeyName&quot;: &quot;A String&quot;, # Describes the Cloud KMS encryption key that will be used to protect the destination Bigtable cluster. The requirements for this key are: 1) The Cloud Bigtable service account associated with the project that contains this cluster must be granted the `cloudkms.cryptoKeyEncrypterDecrypter` role on the CMEK 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. Values are of the form `projects/{project}/locations/{location}/keyRings/{keyring}/cryptoKeys/{key}`
@@ -262,6 +295,17 @@ <h3>Method Details</h3>
The object takes the form of:

{ # A resizable group of nodes in a particular cloud location, capable of serving all Tables in the parent Instance.
&quot;clusterConfig&quot;: { # Configuration for a cluster. # Configuration for this cluster.
&quot;clusterAutoscalingConfig&quot;: { # Autoscaling config for a cluster. # Autoscaling configuration for this cluster. Note that when creating or updating a cluster, exactly one of serve_nodes or cluster_autoscaling_config must be set. If serve_nodes is set, then serve_nodes is fixed and autoscaling is turned off. If cluster_autoscaling_config is set, then serve_nodes will be autoscaled.
&quot;autoscalingLimits&quot;: { # Limits for the number of nodes a Cluster can autoscale up/down to. # Required. Autoscaling limits for this cluster.
&quot;maxServeNodes&quot;: 42, # Required. Maximum number of nodes to scale up to.
&quot;minServeNodes&quot;: 42, # Required. Minimum number of nodes to scale down to.
},
&quot;autoscalingTargets&quot;: { # The Autoscaling targets for a Cluster. These determine the recommended nodes. # Required. Autoscaling targets for this cluster.
&quot;cpuUtilizationPercent&quot;: 42, # 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).
},
},
},
&quot;defaultStorageType&quot;: &quot;A String&quot;, # Immutable. The type of storage used by this cluster to serve its parent instance&#x27;s tables, unless explicitly overridden.
&quot;encryptionConfig&quot;: { # Cloud Key Management Service (Cloud KMS) settings for a CMEK-protected cluster. # Immutable. The encryption configuration for CMEK-protected clusters.
&quot;kmsKeyName&quot;: &quot;A String&quot;, # Describes the Cloud KMS encryption key that will be used to protect the destination Bigtable cluster. The requirements for this key are: 1) The Cloud Bigtable service account associated with the project that contains this cluster must be granted the `cloudkms.cryptoKeyEncrypterDecrypter` role on the CMEK 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. Values are of the form `projects/{project}/locations/{location}/keyRings/{keyring}/cryptoKeys/{key}`
@@ -312,6 +356,17 @@ <h3>Method Details</h3>
The object takes the form of:

{ # A resizable group of nodes in a particular cloud location, capable of serving all Tables in the parent Instance.
&quot;clusterConfig&quot;: { # Configuration for a cluster. # Configuration for this cluster.
&quot;clusterAutoscalingConfig&quot;: { # Autoscaling config for a cluster. # Autoscaling configuration for this cluster. Note that when creating or updating a cluster, exactly one of serve_nodes or cluster_autoscaling_config must be set. If serve_nodes is set, then serve_nodes is fixed and autoscaling is turned off. If cluster_autoscaling_config is set, then serve_nodes will be autoscaled.
&quot;autoscalingLimits&quot;: { # Limits for the number of nodes a Cluster can autoscale up/down to. # Required. Autoscaling limits for this cluster.
&quot;maxServeNodes&quot;: 42, # Required. Maximum number of nodes to scale up to.
&quot;minServeNodes&quot;: 42, # Required. Minimum number of nodes to scale down to.
},
&quot;autoscalingTargets&quot;: { # The Autoscaling targets for a Cluster. These determine the recommended nodes. # Required. Autoscaling targets for this cluster.
&quot;cpuUtilizationPercent&quot;: 42, # 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).
},
},
},
&quot;defaultStorageType&quot;: &quot;A String&quot;, # Immutable. The type of storage used by this cluster to serve its parent instance&#x27;s tables, unless explicitly overridden.
&quot;encryptionConfig&quot;: { # Cloud Key Management Service (Cloud KMS) settings for a CMEK-protected cluster. # Immutable. The encryption configuration for CMEK-protected clusters.
&quot;kmsKeyName&quot;: &quot;A String&quot;, # Describes the Cloud KMS encryption key that will be used to protect the destination Bigtable cluster. The requirements for this key are: 1) The Cloud Bigtable service account associated with the project that contains this cluster must be granted the `cloudkms.cryptoKeyEncrypterDecrypter` role on the CMEK 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. Values are of the form `projects/{project}/locations/{location}/keyRings/{keyring}/cryptoKeys/{key}`

0 comments on commit 815c1ac

Please sign in to comment.