GooglePrivacyDlpV2DiscoveryCloudSqlGenerationCadence

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

How often existing tables should have their profiles refreshed. New tables are scanned as quickly as possible depending on system capacity.

interface GooglePrivacyDlpV2DiscoveryCloudSqlGenerationCadence {

inspectTemplateModifiedCadence?: GooglePrivacyDlpV2DiscoveryInspectTemplateModifiedCadence;

refreshFrequency?:

| "UPDATE_FREQUENCY_UNSPECIFIED"

| "UPDATE_FREQUENCY_NEVER"

| "UPDATE_FREQUENCY_DAILY"

| "UPDATE_FREQUENCY_MONTHLY";

schemaModifiedCadence?: GooglePrivacyDlpV2SchemaModifiedCadence;

}

§Properties

inspectTemplateModifiedCadence?: GooglePrivacyDlpV2DiscoveryInspectTemplateModifiedCadence

[src]

Governs when to update data profiles when the inspection rules defined by the InspectTemplate change. If not set, changing the template will not cause a data profile to update.

refreshFrequency?: "UPDATE_FREQUENCY_UNSPECIFIED" | "UPDATE_FREQUENCY_NEVER" | "UPDATE_FREQUENCY_DAILY" | "UPDATE_FREQUENCY_MONTHLY"

[src]

Data changes (non-schema changes) in Cloud SQL tables can't trigger reprofiling. If you set this field, profiles are refreshed at this frequency regardless of whether the underlying tables have changed. Defaults to never.

schemaModifiedCadence?: GooglePrivacyDlpV2SchemaModifiedCadence

[src]

When to reprofile if the schema has changed.