@maxim_mazurok/gapi.client.batch-v1 0.0.20240315 → 0.0.20240411

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://batch.googleapis.com/$discovery/rest?version=v1
-// Revision: 20240315
+// Revision: 20240411
 
 /// <reference types="gapi.client" />
 
@@ -177,7 +177,7 @@ declare namespace gapi.client {
       network?: NetworkPolicy;
       /** The placement policy. */
       placement?: PlacementPolicy;
-      /** Service account that VMs will run as. */
+      /** Defines the service account for Batch-created VMs. If omitted, the [default Compute Engine service account](https://cloud.google.com/compute/docs/access/service-accounts#default_service_account) is used. Must match the service account specified in any used instance template configured in the Batch job. Includes the following fields: * email: The service account's email address. If not set, the default Compute Engine service account is used. * scopes: Additional OAuth scopes to grant the service account, beyond the default cloud-platform scope. (list of strings) */
       serviceAccount?: ServiceAccount;
       /** Optional. Tags applied to the VM instances. The tags identify valid sources or targets for network firewalls. Each tag must be 1-63 characters long, and comply with [RFC1035](https://www.ietf.org/rfc/rfc1035.txt). */
       tags?: string[];
@@ -378,7 +378,7 @@ declare namespace gapi.client {
       name?: string;
     }
     interface LocationPolicy {
-      /** A list of allowed location names represented by internal URLs. Each location can be a region or a zone. Only one region or multiple zones in one region is supported now. For example, ["regions/us-central1"] allow VMs in any zones in region us-central1. ["zones/us-central1-a", "zones/us-central1-c"] only allow VMs in zones us-central1-a and us-central1-c. All locations end up in different regions would cause errors. For example, ["regions/us-central1", "zones/us-central1-a", "zones/us-central1-b", "zones/us-west1-a"] contains 2 regions "us-central1" and "us-west1". An error is expected in this case. */
+      /** A list of allowed location names represented by internal URLs. Each location can be a region or a zone. Only one region or multiple zones in one region is supported now. For example, ["regions/us-central1"] allow VMs in any zones in region us-central1. ["zones/us-central1-a", "zones/us-central1-c"] only allow VMs in zones us-central1-a and us-central1-c. Mixing locations from different regions would cause errors. For example, ["regions/us-central1", "zones/us-central1-a", "zones/us-central1-b", "zones/us-west1-a"] contains locations from two distinct regions: us-central1 and us-west1. This combination will trigger an error. */
       allowedLocations?: string[];
     }
     interface LogsPolicy {
@@ -496,9 +496,9 @@ declare namespace gapi.client {
       text?: string;
     }
     interface ServiceAccount {
-      /** Email address of the service account. If not specified, the default Compute Engine service account for the project will be used. If instance template is being used, the service account has to be specified in the instance template and it has to match the email field here. */
+      /** Email address of the service account. */
       email?: string;
-      /** List of scopes to be enabled for this service account on the VM, in addition to the cloud-platform API scope that will be added by default. */
+      /** List of scopes to be enabled for this service account. */
       scopes?: string[];
     }
     interface Status {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@maxim_mazurok/gapi.client.batch-v1",
-  "version": "0.0.20240315",
+  "version": "0.0.20240411",
   "description": "TypeScript typings for Batch API v1",
   "repository": {
     "type": "git",