@maxim_mazurok/gapi.client.dlp-v2 0.0.20250109 → 0.0.20250119
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/index.d.ts +3 -3
- package/package.json +1 -1
package/index.d.ts
CHANGED
|
@@ -9,7 +9,7 @@
|
|
|
9
9
|
// This file was generated by https://github.com/Maxim-Mazurok/google-api-typings-generator. Please do not edit it manually.
|
|
10
10
|
// In case of any problems please post issue to https://github.com/Maxim-Mazurok/google-api-typings-generator
|
|
11
11
|
// Generated from: https://dlp.googleapis.com/$discovery/rest?version=v2
|
|
12
|
-
// Revision:
|
|
12
|
+
// Revision: 20250119
|
|
13
13
|
|
|
14
14
|
/// <reference types="gapi.client" />
|
|
15
15
|
|
|
@@ -994,7 +994,7 @@ declare namespace gapi.client {
|
|
|
994
994
|
regex?: GooglePrivacyDlpV2Regex;
|
|
995
995
|
}
|
|
996
996
|
interface GooglePrivacyDlpV2Export {
|
|
997
|
-
/** 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.
|
|
997
|
+
/** 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. After the first profile is generated and the dataset and table are created, the discovery scan configuration will be updated with the dataset and table names. * 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](https://cloud.google.com/sensitive-data-protection/docs/analyze-data-profiles#use_a_premade_report). If you use VPC Service Controls to define security perimeters, then you must use a separate table for each boundary. */
|
|
998
998
|
profileTable?: GooglePrivacyDlpV2BigQueryTable;
|
|
999
999
|
}
|
|
1000
1000
|
interface GooglePrivacyDlpV2Expressions {
|
|
@@ -1260,7 +1260,7 @@ declare namespace gapi.client {
|
|
|
1260
1260
|
description?: string;
|
|
1261
1261
|
/** Human readable form of the infoType name. */
|
|
1262
1262
|
displayName?: string;
|
|
1263
|
-
/** A sample true positive for this infoType. */
|
|
1263
|
+
/** A sample that is a true positive for this infoType. */
|
|
1264
1264
|
example?: string;
|
|
1265
1265
|
/** Internal name of the infoType. */
|
|
1266
1266
|
name?: string;
|