@maxim_mazurok/gapi.client.dlp-v2 0.0.20241215 → 0.0.20250105

package/index.d.ts

@@ -9,7 +9,7 @@
 // This file was generated by https://github.com/Maxim-Mazurok/google-api-typings-generator. Please do not edit it manually.
 // In case of any problems please post issue to https://github.com/Maxim-Mazurok/google-api-typings-generator
 // Generated from: https://dlp.googleapis.com/$discovery/rest?version=v2
-// Revision: 20241215
+// Revision: 20250105
 
 /// <reference types="gapi.client" />
 
@@ -994,7 +994,7 @@ declare namespace gapi.client {
       regex?: GooglePrivacyDlpV2Regex;
     }
     interface GooglePrivacyDlpV2Export {
-      /** 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 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 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. */
+      /** 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 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. * 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. */
       profileTable?: GooglePrivacyDlpV2BigQueryTable;
     }
     interface GooglePrivacyDlpV2Expressions {
@@ -1715,7 +1715,7 @@ declare namespace gapi.client {
       cryptoDeterministicConfig?: GooglePrivacyDlpV2CryptoDeterministicConfig;
       /** Crypto */
       cryptoHashConfig?: GooglePrivacyDlpV2CryptoHashConfig;
-      /** Ffx-Fpe */
+      /** Ffx-Fpe. Strongly discouraged, consider using CryptoDeterministicConfig instead. Fpe is computationally expensive incurring latency costs. */
       cryptoReplaceFfxFpeConfig?: GooglePrivacyDlpV2CryptoReplaceFfxFpeConfig;
       /** Date Shift */
       dateShiftConfig?: GooglePrivacyDlpV2DateShiftConfig;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@maxim_mazurok/gapi.client.dlp-v2",
-  "version": "0.0.20241215",
+  "version": "0.0.20250105",
   "description": "TypeScript typings for Sensitive Data Protection (DLP) v2",
   "repository": {
     "type": "git",