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.
Protobuf type google.privacy.dlp.v2.DataProfileJobConfig
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.
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.
The bytes of the inspectTemplates at the given index.
getInspectTemplatesCount()
publicintgetInspectTemplatesCount()
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.
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.
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.
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.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-01-27 UTC."],[],[]]