Class DataProfileJobConfig (3.9.2)

Stay organized with collections Save and categorize content based on your preferences.
DataProfileJobConfig(mapping=None, *, ignore_unknown_fields=False, **kwargs)

Configuration for setting up a job to scan resources for profile generation. Only one data profile configuration may exist per organization, folder, or project.

The generated data profiles are retained according to the data retention policy.

Attributes

NameDescription
location google.cloud.dlp_v2.types.DataProfileLocation
The data to scan.
project_id str
The project that will run the scan. The DLP service account that exists within this project must have access to all resources that are profiled, and the Cloud DLP API must be enabled.
inspect_templates Sequence[str]
Detection logic for profile generation. Not all template features are used by profiles. FindingLimits, include_quote and exclude_info_types have no impact on data profiling. Multiple templates may be provided if there is data in multiple regions. At most one template must be specified per-region (including "global"). Each region is scanned using the applicable template. If no region-specific template is specified, but a "global" template is specified, it will be copied to that region and used instead. If no global or region-specific template is provided for a region with data, that region's data will not be scanned. For more information, see https://cloud.google.com/dlp/docs/data-profiles#data_residency.
data_profile_actions Sequence[google.cloud.dlp_v2.types.DataProfileAction]
Actions to execute at the completion of the job.

Inheritance

builtins.object > proto.message.Message > DataProfileJobConfig