@maxim_mazurok/gapi.client.servicenetworking-v1beta 0.0.20250203 → 0.0.20250205
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 +9 -1
- 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://servicenetworking.googleapis.com/$discovery/rest?version=v1beta
|
|
12
|
-
// Revision:
|
|
12
|
+
// Revision: 20250205
|
|
13
13
|
|
|
14
14
|
/// <reference types="gapi.client" />
|
|
15
15
|
|
|
@@ -75,6 +75,12 @@ declare namespace gapi.client {
|
|
|
75
75
|
/** 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. */
|
|
76
76
|
version?: string;
|
|
77
77
|
}
|
|
78
|
+
interface Aspect {
|
|
79
|
+
/** The type of this aspect configuration. */
|
|
80
|
+
kind?: string;
|
|
81
|
+
/** Content of the configuration. The underlying schema should be defined by Aspect owners as protobuf message under `apiserving/configaspects/proto`. */
|
|
82
|
+
spec?: {[P in string]: any};
|
|
83
|
+
}
|
|
78
84
|
interface Authentication {
|
|
79
85
|
/** Defines a set of authentication providers that a service supports. */
|
|
80
86
|
providers?: AuthProvider[];
|
|
@@ -780,6 +786,8 @@ declare namespace gapi.client {
|
|
|
780
786
|
interface Service {
|
|
781
787
|
/** 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. */
|
|
782
788
|
apis?: Api[];
|
|
789
|
+
/** 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. */
|
|
790
|
+
aspects?: Aspect[];
|
|
783
791
|
/** Auth configuration. */
|
|
784
792
|
authentication?: Authentication;
|
|
785
793
|
/** API backend configuration. */
|