chore: regenerate dlp client (googleapis#24658)

Generated in GitHub action: https://togithub.com/googleapis/googleapis/google-api-java-client-services/actions/workflows/codegen.yaml

Author: yoshi-code-bot

clients/google-api-services-dlp/v2/2.0.0/README.md

@@ -22,7 +22,7 @@ Add the following lines to your `pom.xml` file:
     <dependency>
       <groupId>com.google.apis</groupId>
       <artifactId>google-api-services-dlp</artifactId>
-      <version>v2-rev20241215-2.0.0</version>
+      <version>v2-rev20250105-2.0.0</version>
     </dependency>
   </dependencies>
 </project>
@@ -35,7 +35,7 @@ repositories {
   mavenCentral()
 }
 dependencies {
-  implementation 'com.google.apis:google-api-services-dlp:v2-rev20241215-2.0.0'
+  implementation 'com.google.apis:google-api-services-dlp:v2-rev20250105-2.0.0'
 }
 ```
 

clients/google-api-services-dlp/v2/2.0.0/com/google/api/services/dlp/v2/model/GooglePrivacyDlpV2CryptoReplaceFfxFpeConfig.java

@@ -25,7 +25,8 @@
  * that the identifier is the empty string, it will be skipped. See
  * https://cloud.google.com/sensitive-data-protection/docs/pseudonymization to learn more. Note: We
  * recommend using CryptoDeterministicConfig for all use cases which do not require preserving the
- * input alphabet space and size, plus warrant referential integrity.
+ * input alphabet space and size, plus warrant referential integrity. FPE incurs significant latency
+ * costs.
  *
  * <p> This is the Java data model class that specifies how to parse/serialize into the JSON that is
  * transmitted over HTTP when working with the Sensitive Data Protection (DLP). For a detailed

clients/google-api-services-dlp/v2/2.0.0/com/google/api/services/dlp/v2/model/GooglePrivacyDlpV2Export.java

@@ -32,40 +32,67 @@
 public final class GooglePrivacyDlpV2Export extends com.google.api.client.json.GenericJson {
 
   /**
-   * Store all table and column profiles in an existing table or a new table in an existing dataset.
-   * Each re-generation will result in new rows in BigQuery. Data is inserted using [streaming
+   * Store all profiles to BigQuery. * The system will create a new dataset and table for you if
+   * none are are provided. The dataset will be named `sensitive_data_protection_discovery` and
+   * table will be named `discovery_profiles`. This table will be placed in the same project as the
+   * container project running the scan. The configuration will be updated with the fields set after
+   * the first profile is generated and the dataset and table are created. * See [Analyze data
+   * profiles stored in BigQuery](https://cloud.google.com/sensitive-data-protection/docs/analyze-
+   * data-profiles) * See [Sample queries for your BigQuery
+   * table](https://cloud.google.com/sensitive-data-protection/docs/analyze-data-
+   * profiles#sample_sql_queries). * Data is inserted using [streaming
    * insert](https://cloud.google.com/blog/products/bigquery/life-of-a-bigquery-streaming-insert)
-   * and so data may be in the buffer for a period of time after the profile has finished. The
+   * and so data may be in the buffer for a period of time after the profile has finished. * The
    * Pub/Sub notification is sent before the streaming buffer is guaranteed to be written, so data
    * may not be instantly visible to queries by the time your topic receives the Pub/Sub
-   * notification.
+   * notification. * The best practice is to use the same table for an entire organization so that
+   * you can take advantage of the provided Looker reports. If you use VPC Service Controls to
+   * define security perimeters, then you must use a separate table for each boundary.
    * The value may be {@code null}.
    */
   @com.google.api.client.util.Key
   private GooglePrivacyDlpV2BigQueryTable profileTable;
 
   /**
-   * Store all table and column profiles in an existing table or a new table in an existing dataset.
-   * Each re-generation will result in new rows in BigQuery. Data is inserted using [streaming
+   * Store all profiles to BigQuery. * The system will create a new dataset and table for you if
+   * none are are provided. The dataset will be named `sensitive_data_protection_discovery` and
+   * table will be named `discovery_profiles`. This table will be placed in the same project as the
+   * container project running the scan. The configuration will be updated with the fields set after
+   * the first profile is generated and the dataset and table are created. * See [Analyze data
+   * profiles stored in BigQuery](https://cloud.google.com/sensitive-data-protection/docs/analyze-
+   * data-profiles) * See [Sample queries for your BigQuery
+   * table](https://cloud.google.com/sensitive-data-protection/docs/analyze-data-
+   * profiles#sample_sql_queries). * Data is inserted using [streaming
    * insert](https://cloud.google.com/blog/products/bigquery/life-of-a-bigquery-streaming-insert)
-   * and so data may be in the buffer for a period of time after the profile has finished. The
+   * and so data may be in the buffer for a period of time after the profile has finished. * The
    * Pub/Sub notification is sent before the streaming buffer is guaranteed to be written, so data
    * may not be instantly visible to queries by the time your topic receives the Pub/Sub
-   * notification.
+   * notification. * The best practice is to use the same table for an entire organization so that
+   * you can take advantage of the provided Looker reports. If you use VPC Service Controls to
+   * define security perimeters, then you must use a separate table for each boundary.
    * @return value or {@code null} for none
    */
   public GooglePrivacyDlpV2BigQueryTable getProfileTable() {
     return profileTable;
   }
 
   /**
-   * Store all table and column profiles in an existing table or a new table in an existing dataset.
-   * Each re-generation will result in new rows in BigQuery. Data is inserted using [streaming
+   * Store all profiles to BigQuery. * The system will create a new dataset and table for you if
+   * none are are provided. The dataset will be named `sensitive_data_protection_discovery` and
+   * table will be named `discovery_profiles`. This table will be placed in the same project as the
+   * container project running the scan. The configuration will be updated with the fields set after
+   * the first profile is generated and the dataset and table are created. * See [Analyze data
+   * profiles stored in BigQuery](https://cloud.google.com/sensitive-data-protection/docs/analyze-
+   * data-profiles) * See [Sample queries for your BigQuery
+   * table](https://cloud.google.com/sensitive-data-protection/docs/analyze-data-
+   * profiles#sample_sql_queries). * Data is inserted using [streaming
    * insert](https://cloud.google.com/blog/products/bigquery/life-of-a-bigquery-streaming-insert)
-   * and so data may be in the buffer for a period of time after the profile has finished. The
+   * and so data may be in the buffer for a period of time after the profile has finished. * The
    * Pub/Sub notification is sent before the streaming buffer is guaranteed to be written, so data
    * may not be instantly visible to queries by the time your topic receives the Pub/Sub
-   * notification.
+   * notification. * The best practice is to use the same table for an entire organization so that
+   * you can take advantage of the provided Looker reports. If you use VPC Service Controls to
+   * define security perimeters, then you must use a separate table for each boundary.
    * @param profileTable profileTable or {@code null} for none
    */
   public GooglePrivacyDlpV2Export setProfileTable(GooglePrivacyDlpV2BigQueryTable profileTable) {

clients/google-api-services-dlp/v2/2.0.0/com/google/api/services/dlp/v2/model/GooglePrivacyDlpV2PrimitiveTransformation.java

@@ -59,7 +59,8 @@ public final class GooglePrivacyDlpV2PrimitiveTransformation extends com.google.
   private GooglePrivacyDlpV2CryptoHashConfig cryptoHashConfig;
 
   /**
-   * Ffx-Fpe
+   * Ffx-Fpe. Strongly discouraged, consider using CryptoDeterministicConfig instead. Fpe is
+   * computationally expensive incurring latency costs.
    * The value may be {@code null}.
    */
   @com.google.api.client.util.Key
@@ -183,15 +184,17 @@ public GooglePrivacyDlpV2PrimitiveTransformation setCryptoHashConfig(GooglePriva
   }
 
   /**
-   * Ffx-Fpe
+   * Ffx-Fpe. Strongly discouraged, consider using CryptoDeterministicConfig instead. Fpe is
+   * computationally expensive incurring latency costs.
    * @return value or {@code null} for none
    */
   public GooglePrivacyDlpV2CryptoReplaceFfxFpeConfig getCryptoReplaceFfxFpeConfig() {
     return cryptoReplaceFfxFpeConfig;
   }
 
   /**
-   * Ffx-Fpe
+   * Ffx-Fpe. Strongly discouraged, consider using CryptoDeterministicConfig instead. Fpe is
+   * computationally expensive incurring latency costs.
    * @param cryptoReplaceFfxFpeConfig cryptoReplaceFfxFpeConfig or {@code null} for none
    */
   public GooglePrivacyDlpV2PrimitiveTransformation setCryptoReplaceFfxFpeConfig(GooglePrivacyDlpV2CryptoReplaceFfxFpeConfig cryptoReplaceFfxFpeConfig) {

clients/google-api-services-dlp/v2/2.0.0/pom.xml

@@ -8,8 +8,8 @@
 
   <groupId>com.google.apis</groupId>
   <artifactId>google-api-services-dlp</artifactId>
-  <version>v2-rev20241215-2.0.0</version>
-  <name>Sensitive Data Protection (DLP) v2-rev20241215-2.0.0</name>
+  <version>v2-rev20250105-2.0.0</version>
+  <name>Sensitive Data Protection (DLP) v2-rev20250105-2.0.0</name>
   <packaging>jar</packaging>
 
   <inceptionYear>2011</inceptionYear>

clients/google-api-services-dlp/v2/README.md

@@ -22,7 +22,7 @@ Add the following lines to your `pom.xml` file:
     <dependency>
       <groupId>com.google.apis</groupId>
       <artifactId>google-api-services-dlp</artifactId>
-      <version>v2-rev20241215-2.0.0</version>
+      <version>v2-rev20250105-2.0.0</version>
     </dependency>
   </dependencies>
 </project>
@@ -35,7 +35,7 @@ repositories {
   mavenCentral()
 }
 dependencies {
-  implementation 'com.google.apis:google-api-services-dlp:v2-rev20241215-2.0.0'
+  implementation 'com.google.apis:google-api-services-dlp:v2-rev20250105-2.0.0'
 }
 ```