DataProfileConfigSnapshot

Stay organized with collections Save and categorize content based on your preferences.

Snapshot of the configurations used to generate the profile.

JSON representation 
{
  "inspectConfig": {
    object (InspectConfig)
  },
  "dataProfileJob": {
    object (DataProfileJobConfig)
  }
}
Fields
inspectConfig

object (InspectConfig)

A copy of the inspection config used to generate this profile. This is a copy of the inspectTemplate specified in DataProfileJobConfig.
dataProfileJob

object (DataProfileJobConfig)

A copy of the configuration used to generate this profile.

DataProfileJobConfig

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.

JSON representation 
{
  "location": {
    object (DataProfileLocation)
  },
  "projectId": string,
  "inspectTemplates": [
    string
  ],
  "dataProfileActions": [
    {
      object (DataProfileAction)
    }
  ]
}
Fields
location

object (DataProfileLocation)

The data to scan.
projectId

string

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.
inspectTemplates[]

string

Detection logic for profile generation.

Not all template features are used by profiles. FindingLimits, includeQuote and excludeInfoTypes 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.
dataProfileActions[]

object (DataProfileAction)

Actions to execute at the completion of the job.

DataProfileLocation

The data that will be profiled.

JSON representation 
{

  // Union field location can be only one of the following:
  "organizationId": string,
  "folderId": string
  // End of list of possible types for union field location.
}
Fields
Union field location. The location to be scanned. location can be only one of the following:
organizationId

string (int64 format)

The ID of an organization to scan.
folderId

string (int64 format)

The ID of the Folder within an organization to scan.