Skip to content

Commit

Permalink
feat(all): auto-regenerate discovery clients (#2700)
Browse files Browse the repository at this point in the history
  • Loading branch information
@yoshi-automation
yoshi-automation authored Jul 27, 2024
1 parent 1e4c024 commit a8b0821
Show file tree
Hide file tree
Showing 22 changed files with 6,991 additions and 3,796 deletions.
14 changes: 12 additions & 2 deletions bigtableadmin/v2/bigtableadmin-api.json
View file
Original file line number Diff line number Diff line change
Expand Up @@ -2194,7 +2194,7 @@
}
}
},
"revision": "20240703",
"revision": "20240720",
"rootUrl": "https://bigtableadmin.googleapis.com/",
"schemas": {
"AppProfile": {
Expand Down Expand Up @@ -3325,6 +3325,10 @@
"utf8Bytes": {
"$ref": "GoogleBigtableAdminV2TypeStringEncodingUtf8Bytes",
"description": "Use `Utf8Bytes` encoding."
},
"utf8Raw": {
"$ref": "GoogleBigtableAdminV2TypeStringEncodingUtf8Raw",
"description": "Deprecated: if set, converts to an empty `utf8_bytes`."
}
},
"type": "object"
Expand All @@ -3335,6 +3339,12 @@
"properties": {},
"type": "object"
},
"GoogleBigtableAdminV2TypeStringEncodingUtf8Raw": {
"description": "Deprecated: prefer the equivalent `Utf8Bytes`.",
"id": "GoogleBigtableAdminV2TypeStringEncodingUtf8Raw",
"properties": {},
"type": "object"
},
"GoogleBigtableAdminV2TypeStruct": {
"description": "A structured data value, consisting of fields which map to dynamically typed values. Values of type `Struct` are stored in `Value.array_value` where entries are in the same order and number as `field_types`.",
"id": "GoogleBigtableAdminV2TypeStruct",
Expand Down Expand Up @@ -4246,7 +4256,7 @@
"type": "object"
},
"Type": {
"description": "`Type` represents the type of data that is written to, read from, or stored in Bigtable. It is heavily based on the GoogleSQL standard to help maintain familiarity and consistency across products and features. For compatibility with Bigtable's existing untyped APIs, each `Type` includes an `Encoding` which describes how to convert to/from the underlying data. Each encoding also defines the following properties: * Order-preserving: Does the encoded value sort consistently with the original typed value? Note that Bigtable will always sort data based on the raw encoded value, *not* the decoded type. - Example: BYTES values sort in the same order as their raw encodings. - Counterexample: Encoding INT64 as a fixed-width decimal string does *not* preserve sort order when dealing with negative numbers. INT64(1) \u003e INT64(-1), but STRING(\"-00001\") \u003e STRING(\"00001). * Self-delimiting: If we concatenate two encoded values, can we always tell where the first one ends and the second one begins? - Example: If we encode INT64s to fixed-width STRINGs, the first value will always contain exactly N digits, possibly preceded by a sign. - Counterexample: If we concatenate two UTF-8 encoded STRINGs, we have no way to tell where the first one ends. * Compatibility: Which other systems have matching encoding schemes? For example, does this encoding have a GoogleSQL equivalent? HBase? Java?",
"description": "`Type` represents the type of data that is written to, read from, or stored in Bigtable. It is heavily based on the GoogleSQL standard to help maintain familiarity and consistency across products and features. For compatibility with Bigtable's existing untyped APIs, each `Type` includes an `Encoding` which describes how to convert to/from the underlying data. Each encoding also defines the following properties: * Order-preserving: Does the encoded value sort consistently with the original typed value? Note that Bigtable will always sort data based on the raw encoded value, *not* the decoded type. - Example: BYTES values sort in the same order as their raw encodings. - Counterexample: Encoding INT64 as a fixed-width decimal string does *not* preserve sort order when dealing with negative numbers. `INT64(1) \u003e INT64(-1)`, but `STRING(\"-00001\") \u003e STRING(\"00001)`. * Self-delimiting: If we concatenate two encoded values, can we always tell where the first one ends and the second one begins? - Example: If we encode INT64s to fixed-width STRINGs, the first value will always contain exactly N digits, possibly preceded by a sign. - Counterexample: If we concatenate two UTF-8 encoded STRINGs, we have no way to tell where the first one ends. * Compatibility: Which other systems have matching encoding schemes? For example, does this encoding have a GoogleSQL equivalent? HBase? Java?",
"id": "Type",
"properties": {
"aggregateType": {
Expand Down
25 changes: 16 additions & 9 deletions bigtableadmin/v2/bigtableadmin-gen.go
View file

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

185 changes: 184 additions & 1 deletion contactcenterinsights/v1/contactcenterinsights-api.json
View file
Original file line number Diff line number Diff line change
Expand Up @@ -109,6 +109,31 @@
"resources": {
"locations": {
"methods": {
"getEncryptionSpec": {
"description": "Gets location-level encryption key specification.",
"flatPath": "v1/projects/{projectsId}/locations/{locationsId}/encryptionSpec",
"httpMethod": "GET",
"id": "contactcenterinsights.projects.locations.getEncryptionSpec",
"parameterOrder": [
"name"
],
"parameters": {
"name": {
"description": "Required. The name of the encryption spec resource to get.",
"location": "path",
"pattern": "^projects/[^/]+/locations/[^/]+/encryptionSpec$",
"required": true,
"type": "string"
}
},
"path": "v1/{+name}",
"response": {
"$ref": "GoogleCloudContactcenterinsightsV1EncryptionSpec"
},
"scopes": [
"https://www.googleapis.com/auth/cloud-platform"
]
},
"getSettings": {
"description": "Gets project-level settings.",
"flatPath": "v1/projects/{projectsId}/locations/{locationsId}/settings",
Expand Down Expand Up @@ -640,6 +665,38 @@
}
}
},
"encryptionSpec": {
"methods": {
"initialize": {
"description": "Initializes a location-level encryption key specification. An error will be thrown if the location has resources already created before the initialization. Once the encryption specification is initialized at a location, it is immutable and all newly created resources under the location will be encrypted with the existing specification.",
"flatPath": "v1/projects/{projectsId}/locations/{locationsId}/encryptionSpec:initialize",
"httpMethod": "POST",
"id": "contactcenterinsights.projects.locations.encryptionSpec.initialize",
"parameterOrder": [
"name"
],
"parameters": {
"name": {
"description": "Immutable. The resource name of the encryption key specification resource. Format: projects/{project}/locations/{location}/encryptionSpec",
"location": "path",
"pattern": "^projects/[^/]+/locations/[^/]+/encryptionSpec$",
"required": true,
"type": "string"
}
},
"path": "v1/{+name}:initialize",
"request": {
"$ref": "GoogleCloudContactcenterinsightsV1InitializeEncryptionSpecRequest"
},
"response": {
"$ref": "GoogleLongrunningOperation"
},
"scopes": [
"https://www.googleapis.com/auth/cloud-platform"
]
}
}
},
"insightsdata": {
"methods": {
"export": {
Expand Down Expand Up @@ -1474,7 +1531,7 @@
}
}
},
"revision": "20240701",
"revision": "20240723",
"rootUrl": "https://contactcenterinsights.googleapis.com/",
"schemas": {
"GoogleCloudContactcenterinsightsV1Analysis": {
Expand Down Expand Up @@ -2646,6 +2703,21 @@
},
"type": "object"
},
"GoogleCloudContactcenterinsightsV1EncryptionSpec": {
"description": "A customer-managed encryption key specification that can be applied to all created resources (e.g. Conversation).",
"id": "GoogleCloudContactcenterinsightsV1EncryptionSpec",
"properties": {
"kmsKey": {
"description": "Required. The name of customer-managed encryption key that is used to secure a resource and its sub-resources. If empty, the resource is secured by the default Google encryption key. Only the key in the same location as this resource is allowed to be used for encryption. Format: `projects/{project}/locations/{location}/keyRings/{keyRing}/cryptoKeys/{key}`",
"type": "string"
},
"name": {
"description": "Immutable. The resource name of the encryption key specification resource. Format: projects/{project}/locations/{location}/encryptionSpec",
"type": "string"
}
},
"type": "object"
},
"GoogleCloudContactcenterinsightsV1Entity": {
"description": "The data for an entity annotation. Represents a phrase in the conversation that is a known entity, such as a person, an organization, or location.",
"id": "GoogleCloudContactcenterinsightsV1Entity",
Expand Down Expand Up @@ -3193,6 +3265,54 @@
"properties": {},
"type": "object"
},
"GoogleCloudContactcenterinsightsV1InitializeEncryptionSpecMetadata": {
"description": "Metadata for initializing a location-level encryption specification.",
"id": "GoogleCloudContactcenterinsightsV1InitializeEncryptionSpecMetadata",
"properties": {
"createTime": {
"description": "Output only. The time the operation was created.",
"format": "google-datetime",
"readOnly": true,
"type": "string"
},
"endTime": {
"description": "Output only. The time the operation finished running.",
"format": "google-datetime",
"readOnly": true,
"type": "string"
},
"partialErrors": {
"description": "Partial errors during initialising operation that might cause the operation output to be incomplete.",
"items": {
"$ref": "GoogleRpcStatus"
},
"type": "array"
},
"request": {
"$ref": "GoogleCloudContactcenterinsightsV1InitializeEncryptionSpecRequest",
"description": "Output only. The original request for initialization.",
"readOnly": true
}
},
"type": "object"
},
"GoogleCloudContactcenterinsightsV1InitializeEncryptionSpecRequest": {
"description": "The request to initialize a location-level encryption specification.",
"id": "GoogleCloudContactcenterinsightsV1InitializeEncryptionSpecRequest",
"properties": {
"encryptionSpec": {
"$ref": "GoogleCloudContactcenterinsightsV1EncryptionSpec",
"description": "Required. The encryption spec used for CMEK encryption. It is required that the kms key is in the same region as the endpoint. The same key will be used for all provisioned resources, if encryption is available. If the kms_key_name is left empty, no encryption will be enforced."
}
},
"type": "object"
},
"GoogleCloudContactcenterinsightsV1InitializeEncryptionSpecResponse": {
"description": "The response to initialize a location-level encryption specification.",
"id": "GoogleCloudContactcenterinsightsV1InitializeEncryptionSpecResponse",
"properties": {},
"type": "object"
},
"GoogleCloudContactcenterinsightsV1Intent": {
"description": "The data for an intent. Represents a detected intent in the conversation, for example MAKES_PROMISE.",
"id": "GoogleCloudContactcenterinsightsV1Intent",
Expand Down Expand Up @@ -5180,6 +5300,21 @@
},
"type": "object"
},
"GoogleCloudContactcenterinsightsV1alpha1EncryptionSpec": {
"description": "A customer-managed encryption key specification that can be applied to all created resources (e.g. Conversation).",
"id": "GoogleCloudContactcenterinsightsV1alpha1EncryptionSpec",
"properties": {
"kmsKey": {
"description": "Required. The name of customer-managed encryption key that is used to secure a resource and its sub-resources. If empty, the resource is secured by the default Google encryption key. Only the key in the same location as this resource is allowed to be used for encryption. Format: `projects/{project}/locations/{location}/keyRings/{keyRing}/cryptoKeys/{key}`",
"type": "string"
},
"name": {
"description": "Immutable. The resource name of the encryption key specification resource. Format: projects/{project}/locations/{location}/encryptionSpec",
"type": "string"
}
},
"type": "object"
},
"GoogleCloudContactcenterinsightsV1alpha1Entity": {
"description": "The data for an entity annotation. Represents a phrase in the conversation that is a known entity, such as a person, an organization, or location.",
"id": "GoogleCloudContactcenterinsightsV1alpha1Entity",
Expand Down Expand Up @@ -5716,6 +5851,54 @@
"properties": {},
"type": "object"
},
"GoogleCloudContactcenterinsightsV1alpha1InitializeEncryptionSpecMetadata": {
"description": "Metadata for initializing a location-level encryption specification.",
"id": "GoogleCloudContactcenterinsightsV1alpha1InitializeEncryptionSpecMetadata",
"properties": {
"createTime": {
"description": "Output only. The time the operation was created.",
"format": "google-datetime",
"readOnly": true,
"type": "string"
},
"endTime": {
"description": "Output only. The time the operation finished running.",
"format": "google-datetime",
"readOnly": true,
"type": "string"
},
"partialErrors": {
"description": "Partial errors during initialising operation that might cause the operation output to be incomplete.",
"items": {
"$ref": "GoogleRpcStatus"
},
"type": "array"
},
"request": {
"$ref": "GoogleCloudContactcenterinsightsV1alpha1InitializeEncryptionSpecRequest",
"description": "Output only. The original request for initialization.",
"readOnly": true
}
},
"type": "object"
},
"GoogleCloudContactcenterinsightsV1alpha1InitializeEncryptionSpecRequest": {
"description": "The request to initialize a location-level encryption specification.",
"id": "GoogleCloudContactcenterinsightsV1alpha1InitializeEncryptionSpecRequest",
"properties": {
"encryptionSpec": {
"$ref": "GoogleCloudContactcenterinsightsV1alpha1EncryptionSpec",
"description": "Required. The encryption spec used for CMEK encryption. It is required that the kms key is in the same region as the endpoint. The same key will be used for all provisioned resources, if encryption is available. If the kms_key_name is left empty, no encryption will be enforced."
}
},
"type": "object"
},
"GoogleCloudContactcenterinsightsV1alpha1InitializeEncryptionSpecResponse": {
"description": "The response to initialize a location-level encryption specification.",
"id": "GoogleCloudContactcenterinsightsV1alpha1InitializeEncryptionSpecResponse",
"properties": {},
"type": "object"
},
"GoogleCloudContactcenterinsightsV1alpha1Intent": {
"description": "The data for an intent. Represents a detected intent in the conversation, for example MAKES_PROMISE.",
"id": "GoogleCloudContactcenterinsightsV1alpha1Intent",
Expand Down
Loading

0 comments on commit a8b0821

Please sign in to comment.