Hi there! Are you looking for the official Deno documentation? Try docs.deno.com for all your Deno learning needs.

EnterpriseCrmEventbusProtoCloudKmsConfig

import type { EnterpriseCrmEventbusProtoCloudKmsConfig } from "https://googleapis.deno.dev/v1/integrations:v1.ts";
interface EnterpriseCrmEventbusProtoCloudKmsConfig {
gcpProjectId?: string;
keyName?: string;
keyRingName?: string;
keyVersionName?: string;
locationName?: string;
serviceAccount?: string;
}

§Properties

§
gcpProjectId?: string
[src]

Optional. The id of GCP project where the KMS key is stored. If not provided, assume the key is stored in the same GCP project defined in Client (tag 14).

§
keyName?: string
[src]

A Cloud KMS key is a named object containing one or more key versions, along with metadata for the key. A key exists on exactly one key ring tied to a specific location.

§
keyRingName?: string
[src]

A key ring organizes keys in a specific Google Cloud location and allows you to manage access control on groups of keys. A key ring's name does not need to be unique across a Google Cloud project, but must be unique within a given location.

§
keyVersionName?: string
[src]

Optional. Each version of a key contains key material used for encryption or signing. A key's version is represented by an integer, starting at 1. To decrypt data or verify a signature, you must use the same key version that was used to encrypt or sign the data.

§
locationName?: string
[src]

Location name of the key ring, e.g. "us-west1".

§
serviceAccount?: string
[src]

Optional. The service account used for authentication of this KMS key. If this is not provided, the service account in Client.clientSource will be used.