InspectConfig(mapping=None, *, ignore_unknown_fields=False, **kwargs)
Configuration description of the scanning process. When used with redactContent only info_types and min_likelihood are currently used.
Restricts what info_types to look for. The values must correspond to InfoType values returned by ListInfoTypes or listed at https://cloud.google.com/dlp/docs/infotypes-reference. When no InfoTypes or CustomInfoTypes are specified in a request, the system may automatically choose what detectors to run. By default this may be all types, but may change over time as detectors are updated. If you need precise control and predictability as to what detectors are run you should specify specific InfoTypes listed in the reference, otherwise a default list will be used, which may change over time.
Only returns findings equal or above this threshold. The default is POSSIBLE. See https://cloud.google.com/dlp/docs/likelihood to learn more.
Configuration to control the number of findings returned. This is not used for data profiling. When redacting sensitive data from images, finding limits don't apply. They can cause unexpected or inconsistent results, where only some data is redacted. Don't include finding limits in
When true, a contextual quote from the data that triggered a finding is included in the response; see
When true, excludes type information of the findings. This is not used for data profiling.
CustomInfoTypes provided by the user. See https://cloud.google.com/dlp/docs/creating-custom-infotypes to learn more.
Deprecated and unused.
Set of rules to apply to the findings for this InspectConfig. Exclusion rules, contained in the set are executed in the end, other rules are executed in the order they are specified for each info type.
Inheritancebuiltins.object > proto.message.Message > InspectConfig
FindingLimits(mapping=None, *, ignore_unknown_fields=False, **kwargs)
Configuration to control the number of findings returned for inspection. This is not used for de-identification or data profiling.
When redacting sensitive data from images, finding limits don't
apply. They can cause unexpected or inconsistent results, where only
some data is redacted. Don't include finding limits in
requests. Otherwise, Cloud DLP returns an error.