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

GooglePrivacyDlpV2TagResources

import type { GooglePrivacyDlpV2TagResources } from "https://googleapis.deno.dev/v1/dlp:v2.ts";

If set, attaches the [tags] (https://cloud.google.com/resource-manager/docs/tags/tags-overview) provided to profiled resources. Tags support access control. You can conditionally grant or deny access to a resource based on whether the resource has a specific tag.

interface GooglePrivacyDlpV2TagResources {
lowerDataRiskToLow?: boolean;
profileGenerationsToTag?: "PROFILE_GENERATION_UNSPECIFIED" | "PROFILE_GENERATION_NEW" | "PROFILE_GENERATION_UPDATE"[];
tagConditions?: GooglePrivacyDlpV2TagCondition[];
}

§Properties

§
lowerDataRiskToLow?: boolean
[src]

Whether applying a tag to a resource should lower the risk of the profile for that resource. For example, in conjunction with an IAM deny policy, you can deny all principals a permission if a tag value is present, mitigating the risk of the resource. This also lowers the data risk of resources at the lower levels of the resource hierarchy. For example, reducing the data risk of a table data profile also reduces the data risk of the constituent column data profiles.

§
profileGenerationsToTag?: "PROFILE_GENERATION_UNSPECIFIED" | "PROFILE_GENERATION_NEW" | "PROFILE_GENERATION_UPDATE"[]
[src]

The profile generations for which the tag should be attached to resources. If you attach a tag to only new profiles, then if the sensitivity score of a profile subsequently changes, its tag doesn't change. By default, this field includes only new profiles. To include both new and updated profiles for tagging, this field should explicitly include both PROFILE_GENERATION_NEW and PROFILE_GENERATION_UPDATE.

§
tagConditions?: GooglePrivacyDlpV2TagCondition[]
[src]

The tags to associate with different conditions.