@maxim_mazurok/gapi.client.servicemanagement-v1 0.0.20250127 → 0.0.20250210

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://servicemanagement.googleapis.com/$discovery/rest?version=v1
-// Revision: 20250127
+// Revision: 20250210
 
 /// <reference types="gapi.client" />
 
@@ -48,6 +48,12 @@ declare namespace gapi.client {
       /** A version string for this interface. If specified, must have the form `major-version.minor-version`, as in `1.10`. If the minor version is omitted, it defaults to zero. If the entire version field is empty, the major version is derived from the package name, as outlined below. If the field is not empty, the version in the package name will be verified to be consistent with what is provided here. The versioning schema uses [semantic versioning](http://semver.org) where the major version number indicates a breaking change and the minor version an additive, non-breaking change. Both version numbers are signals to users what to expect from different versions, and should be carefully chosen based on the product plan. The major version is also reflected in the package name of the interface, which must end in `v`, as in `google.feature.v1`. For major versions 0 and 1, the suffix can be omitted. Zero major versions must only be used for experimental, non-GA interfaces. */
       version?: string;
     }
+    interface Aspect {
+      /** The type of this aspect configuration. */
+      kind?: string;
+      /** Content of the configuration. The underlying schema should be defined by Aspect owners as protobuf message under `apiserving/configaspects/proto`. */
+      spec?: {[P in string]: any};
+    }
     interface AuditConfig {
       /** The configuration for logging of each type of permission. */
       auditLogConfigs?: AuditLogConfig[];
@@ -109,6 +115,8 @@ declare namespace gapi.client {
       disableAuth?: boolean;
       /** The JWT audience is used when generating a JWT ID token for the backend. This ID token will be added in the HTTP "authorization" header, and sent to the backend. */
       jwtAudience?: string;
+      /** The load balancing policy used for connection to the application backend. Defined as an arbitrary string to accomondate custom load balancing policies supported by the underlying channel, but suggest most users use one of the standard policies, such as the default, "RoundRobin". */
+      loadBalancingPolicy?: string;
       /** Deprecated, do not use. */
       minDeadline?: number;
       /** The number of seconds to wait for the completion of a long running operation. The default is no deadline. */
@@ -338,6 +346,8 @@ declare namespace gapi.client {
       protobufPythonicTypesEnabled?: boolean;
       /** Enables generation of asynchronous REST clients if `rest` transport is enabled. By default, asynchronous REST clients will not be generated. This feature will be enabled by default 1 month after launching the feature in preview packages. */
       restAsyncIoEnabled?: boolean;
+      /** Disables generation of an unversioned Python package for this client library. This means that the module names will need to be versioned in import statements. For example `import google.cloud.library_v2` instead of `import google.cloud.library`. */
+      unversionedPackageDisabled?: boolean;
     }
     interface Expr {
       /** Optional. Description of the expression. This is a longer text which describes the expression, e.g. when hovered over it in a UI. */
@@ -676,7 +686,7 @@ declare namespace gapi.client {
       value?: {[P in string]: any};
     }
     interface Page {
-      /** The Markdown content of the page. You can use (== include {path} ==) to include content from a Markdown file. The content can be used to produce the documentation page such as HTML format page. */
+      /** The Markdown content of the page. You can use ```(== include {path} ==)``` to include content from a Markdown file. The content can be used to produce the documentation page such as HTML format page. */
       content?: string;
       /** The name of the page. It will be used as an identity of the page to generate URI of the page, text of the link to this page in navigation, etc. The full page name (start from the root page name to this page concatenated with `.`) can be used as reference to the page in your documentation. For example: pages: - name: Tutorial content: (== include tutorial.md ==) subpages: - name: Java content: (== include tutorial_java.md ==) You can reference `Java` page using Markdown reference link syntax: `Java`. */
       name?: string;
@@ -782,12 +792,16 @@ declare namespace gapi.client {
       common?: CommonLanguageSettings;
     }
     interface SelectiveGapicGeneration {
+      /** Setting this to true indicates to the client generators that methods that would be excluded from the generation should instead be generated in a way that indicates these methods should not be consumed by end users. How this is expressed is up to individual language implementations to decide. Some examples may be: added annotations, obfuscated identifiers, or other language idiomatic patterns. */
+      generateOmittedAsInternal?: boolean;
       /** An allowlist of the fully qualified names of RPCs that should be included on public client surfaces. */
       methods?: string[];
     }
     interface Service {
       /** A list of API interfaces exported by this service. Only the `name` field of the google.protobuf.Api needs to be provided by the configuration author, as the remaining fields will be derived from the IDL during the normalization process. It is an error to specify an API interface here which cannot be resolved against the associated IDL files. */
       apis?: Api[];
+      /** Configuration aspects. This is a repeated field to allow multiple aspects to be configured. The kind field in each ConfigAspect specifies the type of aspect. The spec field contains the configuration for that aspect. The schema for the spec field is defined by the backend service owners. */
+      aspects?: Aspect[];
       /** Auth configuration. */
       authentication?: Authentication;
       /** API backend configuration. */

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@maxim_mazurok/gapi.client.servicemanagement-v1",
-  "version": "0.0.20250127",
+  "version": "0.0.20250210",
   "description": "TypeScript typings for Service Management API v1",
   "repository": {
     "type": "git",