From e6e9a36e142bd8622606fc9db65d709aad80dd1d Mon Sep 17 00:00:00 2001
From: yoshi-automation <yoshi-automation@google.com>
Date: Thu, 16 Jul 2020 04:30:39 -0700
Subject: [PATCH] fix(dlp): update the API

#### dlp:v2
The following keys were changed:
- schemas.GooglePrivacyDlpV2CryptoReplaceFfxFpeConfig.properties.customAlphabet.description
- schemas.GooglePrivacyDlpV2InfoType.properties.name.description
---
 discovery/dlp-v2.json | 6 +++---
 src/apis/dlp/v2.ts    | 4 ++--
 2 files changed, 5 insertions(+), 5 deletions(-)

diff --git a/discovery/dlp-v2.json b/discovery/dlp-v2.json
index a8b8b4baa2..387e796161 100644
--- a/discovery/dlp-v2.json
+++ b/discovery/dlp-v2.json
@@ -3126,7 +3126,7 @@
       }
     }
   },
-  "revision": "20200706",
+  "revision": "20200713",
   "rootUrl": "https://dlp.googleapis.com/",
   "schemas": {
     "GooglePrivacyDlpV2Action": {
@@ -4012,7 +4012,7 @@
           "description": "Required. The key used by the encryption algorithm."
         },
         "customAlphabet": {
-          "description": "This is supported by mapping these to the alphanumeric characters\nthat the FFX mode natively supports. This happens before/after\nencryption/decryption.\nEach character listed must appear only once.\nNumber of characters must be in the range [2, 95].\nThis must be encoded as ASCII.\nThe order of characters does not matter.",
+          "description": "This is supported by mapping these to the alphanumeric characters\nthat the FFX mode natively supports. This happens before/after\nencryption/decryption.\nEach character listed must appear only once.\nNumber of characters must be in the range [2, 95].\nThis must be encoded as ASCII.\nThe order of characters does not matter.\nThe full list of allowed characters is:\n<code>0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz\n~`!@#$%^&*()_-+={[}]|\\:;\"'<,>.?/</code>",
           "type": "string"
         },
         "radix": {
@@ -4959,7 +4959,7 @@
       "id": "GooglePrivacyDlpV2InfoType",
       "properties": {
         "name": {
-          "description": "Name of the information type. Either a name of your choosing when\ncreating a CustomInfoType, or one of the names listed\nat https://cloud.google.com/dlp/docs/infotypes-reference when specifying\na built-in type. InfoType names should conform to the pattern\n`[a-zA-Z0-9_]{1,64}`.",
+          "description": "Name of the information type. Either a name of your choosing when\ncreating a CustomInfoType, or one of the names listed\nat https://cloud.google.com/dlp/docs/infotypes-reference when specifying\na built-in type.  When sending Cloud DLP results to Data Catalog, infoType\nnames should conform to the pattern `[A-Za-z0-9$-_]{1,64}`.",
           "type": "string"
         }
       },
diff --git a/src/apis/dlp/v2.ts b/src/apis/dlp/v2.ts
index 1f7a0a81d8..04ddb94406 100644
--- a/src/apis/dlp/v2.ts
+++ b/src/apis/dlp/v2.ts
@@ -766,7 +766,7 @@ export namespace dlp_v2 {
      */
     cryptoKey?: Schema$GooglePrivacyDlpV2CryptoKey;
     /**
-     * This is supported by mapping these to the alphanumeric characters that the FFX mode natively supports. This happens before/after encryption/decryption. Each character listed must appear only once. Number of characters must be in the range [2, 95]. This must be encoded as ASCII. The order of characters does not matter.
+     * This is supported by mapping these to the alphanumeric characters that the FFX mode natively supports. This happens before/after encryption/decryption. Each character listed must appear only once. Number of characters must be in the range [2, 95]. This must be encoded as ASCII. The order of characters does not matter. The full list of allowed characters is: &lt;code&gt;0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz ~`!@#$%^&amp;*()_-+={[}]|\:;&quot;&#39;&lt;,&gt;.?/&lt;/code&gt;
      */
     customAlphabet?: string | null;
     /**
@@ -1452,7 +1452,7 @@ export namespace dlp_v2 {
    */
   export interface Schema$GooglePrivacyDlpV2InfoType {
     /**
-     * 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. InfoType names should conform to the pattern `[a-zA-Z0-9_]{1,64}`.
+     * 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}`.
      */
     name?: string | null;
   }