chore(dlp): update the api

Author: yoshi-automation

docs/dyn/dlp_v2.organizations.inspectTemplates.html

@@ -163,7 +163,7 @@ <h3>Method Details</h3>
               },
             ],
             &quot;inspectConfig&quot;: { # Configuration description of the scanning process. When used with redactContent only info_types and min_likelihood are currently used. # How and what to scan for.
-              &quot;contentOptions&quot;: [ # List of options defining data content to scan. If empty, text, images, and other content will be included.
+              &quot;contentOptions&quot;: [ # Deprecated and unused.
                 &quot;A String&quot;,
               ],
               &quot;customInfoTypes&quot;: [ # CustomInfoTypes provided by the user. See https://cloud.google.com/dlp/docs/creating-custom-infotypes to learn more.
@@ -218,15 +218,15 @@ <h3>Method Details</h3>
                   },
                 },
               ],
-              &quot;excludeInfoTypes&quot;: True or False, # When true, excludes type information of the findings.
-              &quot;includeQuote&quot;: True or False, # When true, a contextual quote from the data that triggered a finding is included in the response; see Finding.quote.
+              &quot;excludeInfoTypes&quot;: True or False, # When true, excludes type information of the findings. This is not used for data profiling.
+              &quot;includeQuote&quot;: True or False, # When true, a contextual quote from the data that triggered a finding is included in the response; see Finding.quote. This is not used for data profiling.
               &quot;infoTypes&quot;: [ # 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.
                 { # Type of information detected by the API.
                   &quot;name&quot;: &quot;A String&quot;, # Name of the information type. Either a name of your choosing when creating a CustomInfoType, or one of the names listed at https://cloud.google.com/dlp/docs/infotypes-reference when specifying a built-in type. When sending Cloud DLP results to Data Catalog, infoType names should conform to the pattern `[A-Za-z0-9$-_]{1,64}`.
                   &quot;version&quot;: &quot;A String&quot;, # Optional version name for this InfoType.
                 },
               ],
-              &quot;limits&quot;: { # Configuration to control the number of findings returned. Cannot be set if de-identification is requested. # Configuration to control the number of findings returned.
+              &quot;limits&quot;: { # Configuration to control the number of findings returned for inspection. This is not used for de-identification or data profiling. # Configuration to control the number of findings returned. This is not used for data profiling.
                 &quot;maxFindingsPerInfoType&quot;: [ # Configuration of findings limit given for specified infoTypes.
                   { # Max findings configuration per infoType, per content item or long running DlpJob.
                     &quot;infoType&quot;: { # Type of information detected by the API. # Type of information the findings limit applies to. Only one limit per info_type should be provided. If InfoTypeLimit does not have an info_type, the DLP API applies the limit against all info_types that are found but not specified in another InfoTypeLimit.
@@ -386,7 +386,7 @@ <h3>Method Details</h3>
             &quot;description&quot;: &quot;A String&quot;, # Short description (max 256 chars).
             &quot;displayName&quot;: &quot;A String&quot;, # Display name (max 256 chars).
             &quot;inspectConfig&quot;: { # Configuration description of the scanning process. When used with redactContent only info_types and min_likelihood are currently used. # The core content of the template. Configuration of the scanning process.
-              &quot;contentOptions&quot;: [ # List of options defining data content to scan. If empty, text, images, and other content will be included.
+              &quot;contentOptions&quot;: [ # Deprecated and unused.
                 &quot;A String&quot;,
               ],
               &quot;customInfoTypes&quot;: [ # CustomInfoTypes provided by the user. See https://cloud.google.com/dlp/docs/creating-custom-infotypes to learn more.
@@ -441,15 +441,15 @@ <h3>Method Details</h3>
                   },
                 },
               ],
-              &quot;excludeInfoTypes&quot;: True or False, # When true, excludes type information of the findings.
-              &quot;includeQuote&quot;: True or False, # When true, a contextual quote from the data that triggered a finding is included in the response; see Finding.quote.
+              &quot;excludeInfoTypes&quot;: True or False, # When true, excludes type information of the findings. This is not used for data profiling.
+              &quot;includeQuote&quot;: True or False, # When true, a contextual quote from the data that triggered a finding is included in the response; see Finding.quote. This is not used for data profiling.
               &quot;infoTypes&quot;: [ # 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.
                 { # Type of information detected by the API.
                   &quot;name&quot;: &quot;A String&quot;, # Name of the information type. Either a name of your choosing when creating a CustomInfoType, or one of the names listed at https://cloud.google.com/dlp/docs/infotypes-reference when specifying a built-in type. When sending Cloud DLP results to Data Catalog, infoType names should conform to the pattern `[A-Za-z0-9$-_]{1,64}`.
                   &quot;version&quot;: &quot;A String&quot;, # Optional version name for this InfoType.
                 },
               ],
-              &quot;limits&quot;: { # Configuration to control the number of findings returned. Cannot be set if de-identification is requested. # Configuration to control the number of findings returned.
+              &quot;limits&quot;: { # Configuration to control the number of findings returned for inspection. This is not used for de-identification or data profiling. # Configuration to control the number of findings returned. This is not used for data profiling.
                 &quot;maxFindingsPerInfoType&quot;: [ # Configuration of findings limit given for specified infoTypes.
                   { # Max findings configuration per infoType, per content item or long running DlpJob.
                     &quot;infoType&quot;: { # Type of information detected by the API. # Type of information the findings limit applies to. Only one limit per info_type should be provided. If InfoTypeLimit does not have an info_type, the DLP API applies the limit against all info_types that are found but not specified in another InfoTypeLimit.