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

GoogleCloudIntegrationsV1alphaCloudKmsConfig

import type { GoogleCloudIntegrationsV1alphaCloudKmsConfig } from "https://googleapis.deno.dev/v1/integrations:v1.ts";

Configuration information for Client's Cloud KMS information

interface GoogleCloudIntegrationsV1alphaCloudKmsConfig {
key?: string;
keyVersion?: string;
kmsLocation?: string;
kmsProjectId?: string;
kmsRing?: string;
}

§Properties

§
key?: string
[src]

Required. 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.

§
keyVersion?: 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.

§
kmsLocation?: string
[src]

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

§
kmsProjectId?: string
[src]

Optional. The gcp project id of the project where the kms key stored. If empty, the kms key is stored at the same project as customer's project and ecrypted with CMEK, otherwise, the kms key is stored in the tenant project and encrypted with GMEK

§
kmsRing?: string
[src]

Required. 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.