feat: regenerate index files

discovery/accessapproval-v1.json

@@ -3,7 +3,7 @@
     "oauth2": {
       "scopes": {
         "https://www.googleapis.com/auth/cloud-platform": {
-          "description": "View and manage your data across Google Cloud Platform services"
+          "description": "See, edit, configure, and delete your Google Cloud Platform data"
         }
       }
     }
@@ -754,7 +754,7 @@
       }
     }
   },
-  "revision": "20210318",
+  "revision": "20210416",
   "rootUrl": "https://accessapproval.googleapis.com/",
   "schemas": {
     "AccessApprovalSettings": {

discovery/admin-directory_v1.json

@@ -4417,7 +4417,7 @@
       }
     }
   },
-  "revision": "20210413",
+  "revision": "20210420",
   "rootUrl": "https://admin.googleapis.com/",
   "schemas": {
     "Alias": {
@@ -5730,7 +5730,7 @@
             "The caller does not have permission to execute the specified operation. `PERMISSION_DENIED` must not be used for rejections caused by exhausting some resource (use `RESOURCE_EXHAUSTED` instead for those errors). `PERMISSION_DENIED` must not be used if the caller can not be identified (use `UNAUTHENTICATED` instead for those errors). This error code does not imply the request is valid or the requested entity exists or satisfies other pre-conditions. HTTP Mapping: 403 Forbidden",
             "The request does not have valid authentication credentials for the operation. HTTP Mapping: 401 Unauthorized",
             "Some resource has been exhausted, perhaps a per-user quota, or perhaps the entire file system is out of space. HTTP Mapping: 429 Too Many Requests",
-            "The operation was rejected because the system is not in a state required for the operation's execution. For example, the directory to be deleted is non-empty, an rmdir operation is applied to a non-directory, etc. Service implementors can use the following guidelines to decide between `FAILED_PRECONDITION`, `ABORTED`, and `UNAVAILABLE`: (a) Use `UNAVAILABLE` if the client can retry just the failing call. (b) Use `ABORTED` if the client should retry at a higher level (e.g., when a client-specified test-and-set fails, indicating the client should restart a read-modify-write sequence). (c) Use `FAILED_PRECONDITION` if the client should not retry until the system state has been explicitly fixed. E.g., if an \"rmdir\" fails because the directory is non-empty, `FAILED_PRECONDITION` should be returned since the client should not retry unless the files are deleted from the directory. HTTP Mapping: 400 Bad Request",
+            "The operation was rejected because the system is not in a state required for the operation's execution. For example, the directory to be deleted is non-empty, an rmdir operation is applied to a non-directory, etc. Service implementors can use the following guidelines to decide between `FAILED_PRECONDITION`, `ABORTED`, and `UNAVAILABLE`: (a) Use `UNAVAILABLE` if the client can retry just the failing call. (b) Use `ABORTED` if the client should retry at a higher level. For example, when a client-specified test-and-set fails, indicating the client should restart a read-modify-write sequence. (c) Use `FAILED_PRECONDITION` if the client should not retry until the system state has been explicitly fixed. For example, if an \"rmdir\" fails because the directory is non-empty, `FAILED_PRECONDITION` should be returned since the client should not retry unless the files are deleted from the directory. HTTP Mapping: 400 Bad Request",
             "The operation was aborted, typically due to a concurrency issue such as a sequencer check failure or transaction abort. See the guidelines above for deciding between `FAILED_PRECONDITION`, `ABORTED`, and `UNAVAILABLE`. HTTP Mapping: 409 Conflict",
             "The operation was attempted past the valid range. E.g., seeking or reading past end-of-file. Unlike `INVALID_ARGUMENT`, this error indicates a problem that may be fixed if the system state changes. For example, a 32-bit file system will generate `INVALID_ARGUMENT` if asked to read at an offset that is not in the range [0,2^32-1], but it will generate `OUT_OF_RANGE` if asked to read from an offset past the current file size. There is a fair bit of overlap between `FAILED_PRECONDITION` and `OUT_OF_RANGE`. We recommend using `OUT_OF_RANGE` (the more specific error) when it applies so that callers who are iterating through a space can easily look for an `OUT_OF_RANGE` error to detect when they are done. HTTP Mapping: 400 Bad Request",
             "The operation is not implemented or is not supported/enabled in this service. HTTP Mapping: 501 Not Implemented",

discovery/index.json

@@ -454,6 +454,21 @@
       "documentationLink": "https://cloud.google.com/apigee-api-management/",
       "preferred": true
     },
+    {
+      "kind": "discovery#directoryItem",
+      "id": "apikeys:v2",
+      "name": "apikeys",
+      "version": "v2",
+      "title": "API Keys API",
+      "description": "Manages the API keys associated with developer projects.",
+      "discoveryRestUrl": "https://apikeys.googleapis.com/$discovery/rest?version=v2",
+      "icons": {
+        "x16": "https://www.gstatic.com/images/branding/product/1x/googleg_16dp.png",
+        "x32": "https://www.gstatic.com/images/branding/product/1x/googleg_32dp.png"
+      },
+      "documentationLink": "https://cloud.google.com/api-keys/docs",
+      "preferred": true
+    },
     {
       "kind": "discovery#directoryItem",
       "id": "appengine:v1alpha",

src/apis/index.ts

@@ -75,6 +75,7 @@ import {
   androidpublisher,
 } from './androidpublisher';
 import {VERSIONS as apigatewayVersions, apigateway} from './apigateway';
+import {VERSIONS as apikeysVersions, apikeys} from './apikeys';
 import {VERSIONS as appengineVersions, appengine} from './appengine';
 import {VERSIONS as appsactivityVersions, appsactivity} from './appsactivity';
 import {
@@ -518,6 +519,7 @@ export const APIS: APIList = {
   androidmanagement: androidmanagementVersions,
   androidpublisher: androidpublisherVersions,
   apigateway: apigatewayVersions,
+  apikeys: apikeysVersions,
   appengine: appengineVersions,
   appsactivity: appsactivityVersions,
   area120tables: area120tablesVersions,
@@ -732,6 +734,7 @@ export class GeneratedAPIs {
   androidmanagement = androidmanagement;
   androidpublisher = androidpublisher;
   apigateway = apigateway;
+  apikeys = apikeys;
   appengine = appengine;
   appsactivity = appsactivity;
   area120tables = area120tables;

src/index.ts

@@ -52,6 +52,7 @@ export {androidpublisher_v2} from './apis/androidpublisher/v2';
 export {androidpublisher_v3} from './apis/androidpublisher/v3';
 export {apigateway_v1} from './apis/apigateway/v1';
 export {apigateway_v1beta} from './apis/apigateway/v1beta';
+export {apikeys_v2} from './apis/apikeys/v2';
 export {appengine_v1} from './apis/appengine/v1';
 export {appengine_v1alpha} from './apis/appengine/v1alpha';
 export {appengine_v1beta} from './apis/appengine/v1beta';