Skip to content

Commit

Permalink
feat(dlp): update the api
Browse files Browse the repository at this point in the history
#### dlp:v2

The following keys were added:
- schemas.GooglePrivacyDlpV2ExcludeByHotword (Total Keys: 4)
- schemas.GooglePrivacyDlpV2ExclusionRule.properties.excludeByHotword.$ref (Total Keys: 1)
  • Loading branch information
yoshi-automation committed Nov 8, 2022
1 parent 8ad1152 commit 31b8027
Show file tree
Hide file tree
Showing 15 changed files with 860 additions and 1 deletion.
72 changes: 72 additions & 0 deletions docs/dyn/dlp_v2.organizations.inspectTemplates.html

Large diffs are not rendered by default.

24 changes: 24 additions & 0 deletions docs/dyn/dlp_v2.organizations.locations.dlpJobs.html
Expand Up @@ -279,6 +279,18 @@ <h3>Method Details</h3>
],
},
},
&quot;excludeByHotword&quot;: { # The rule to exclude findings based on a hotword. For record inspection of tables, column names are considered hotwords. An example of this is to exclude a finding if a BigQuery column matches a specific pattern. # Drop if the hotword rule is contained in the proximate context. For tabular data, the context includes the column name.
&quot;hotwordRegex&quot;: { # Message defining a custom regular expression. # Regular expression pattern defining what qualifies as a hotword.
&quot;groupIndexes&quot;: [ # The index of the submatch to extract as findings. When not specified, the entire match is returned. No more than 3 may be included.
42,
],
&quot;pattern&quot;: &quot;A String&quot;, # Pattern defining the regular expression. Its syntax (https://github.com/google/re2/wiki/Syntax) can be found under the google/re2 repository on GitHub.
},
&quot;proximity&quot;: { # Message for specifying a window around a finding to apply a detection rule. # Range of characters within which the entire hotword must reside. The total length of the window cannot exceed 1000 characters. The windowBefore property in proximity should be set to 1 if the hotword needs to be included in a column header.
&quot;windowAfter&quot;: 42, # Number of characters after the finding to consider.
&quot;windowBefore&quot;: 42, # Number of characters before the finding to consider. For tabular data, if you want to modify the likelihood of an entire column of findngs, set this to 1. For more information, see [Hotword example: Set the match likelihood of a table column] (https://cloud.google.com/dlp/docs/creating-custom-infotypes-likelihood#match-column-values).
},
},
&quot;excludeInfoTypes&quot;: { # List of excluded infoTypes. # Set of infoTypes for which findings would affect this rule.
&quot;infoTypes&quot;: [ # InfoType list in ExclusionRule rule drops a finding when it overlaps or contained within with a finding of an infoType from this list. For example, for `InspectionRuleSet.info_types` containing &quot;PHONE_NUMBER&quot;` and `exclusion_rule` containing `exclude_info_types.info_types` with &quot;EMAIL_ADDRESS&quot; the phone number findings are dropped if they overlap with EMAIL_ADDRESS finding. That leads to &quot;555-222-2222@example.org&quot; to generate only a single finding, namely email address.
{ # Type of information detected by the API.
Expand Down Expand Up @@ -502,6 +514,18 @@ <h3>Method Details</h3>
],
},
},
&quot;excludeByHotword&quot;: { # The rule to exclude findings based on a hotword. For record inspection of tables, column names are considered hotwords. An example of this is to exclude a finding if a BigQuery column matches a specific pattern. # Drop if the hotword rule is contained in the proximate context. For tabular data, the context includes the column name.
&quot;hotwordRegex&quot;: { # Message defining a custom regular expression. # Regular expression pattern defining what qualifies as a hotword.
&quot;groupIndexes&quot;: [ # The index of the submatch to extract as findings. When not specified, the entire match is returned. No more than 3 may be included.
42,
],
&quot;pattern&quot;: &quot;A String&quot;, # Pattern defining the regular expression. Its syntax (https://github.com/google/re2/wiki/Syntax) can be found under the google/re2 repository on GitHub.
},
&quot;proximity&quot;: { # Message for specifying a window around a finding to apply a detection rule. # Range of characters within which the entire hotword must reside. The total length of the window cannot exceed 1000 characters. The windowBefore property in proximity should be set to 1 if the hotword needs to be included in a column header.
&quot;windowAfter&quot;: 42, # Number of characters after the finding to consider.
&quot;windowBefore&quot;: 42, # Number of characters before the finding to consider. For tabular data, if you want to modify the likelihood of an entire column of findngs, set this to 1. For more information, see [Hotword example: Set the match likelihood of a table column] (https://cloud.google.com/dlp/docs/creating-custom-infotypes-likelihood#match-column-values).
},
},
&quot;excludeInfoTypes&quot;: { # List of excluded infoTypes. # Set of infoTypes for which findings would affect this rule.
&quot;infoTypes&quot;: [ # InfoType list in ExclusionRule rule drops a finding when it overlaps or contained within with a finding of an infoType from this list. For example, for `InspectionRuleSet.info_types` containing &quot;PHONE_NUMBER&quot;` and `exclusion_rule` containing `exclude_info_types.info_types` with &quot;EMAIL_ADDRESS&quot; the phone number findings are dropped if they overlap with EMAIL_ADDRESS finding. That leads to &quot;555-222-2222@example.org&quot; to generate only a single finding, namely email address.
{ # Type of information detected by the API.
Expand Down

0 comments on commit 31b8027

Please sign in to comment.