Cloud Data Loss Prevention (DLP) V2 API - Class Google::Cloud::Dlp::V2::DataProfileJobConfig (v1.2.0)

Reference documentation and code samples for the Cloud Data Loss Prevention (DLP) V2 API class Google::Cloud::Dlp::V2::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.

Inherits

  • Object

Extended By

  • Google::Protobuf::MessageExts::ClassMethods

Includes

  • Google::Protobuf::MessageExts

Methods

#data_profile_actions

def data_profile_actions() -> ::Array<::Google::Cloud::Dlp::V2::DataProfileAction>
Returns

#data_profile_actions=

def data_profile_actions=(value) -> ::Array<::Google::Cloud::Dlp::V2::DataProfileAction>
Parameter
Returns

#inspect_templates

def inspect_templates() -> ::Array<::String>
Returns
  • (::Array<::String>) — 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/sensitive-data-protection/docs/data-profiles#data-residency.

#inspect_templates=

def inspect_templates=(value) -> ::Array<::String>
Parameter
  • value (::Array<::String>) — 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/sensitive-data-protection/docs/data-profiles#data-residency.

Returns
  • (::Array<::String>) — 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/sensitive-data-protection/docs/data-profiles#data-residency.

#location

def location() -> ::Google::Cloud::Dlp::V2::DataProfileLocation
Returns

#location=

def location=(value) -> ::Google::Cloud::Dlp::V2::DataProfileLocation
Parameter
Returns

#project_id

def project_id() -> ::String
Returns
  • (::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.

#project_id=

def project_id=(value) -> ::String
Parameter
  • value (::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.
Returns
  • (::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.