@googleapis/servicenetworking 0.2.0 → 4.3.0

package/v1beta.ts

@@ -232,7 +232,7 @@ export namespace servicenetworking_v1beta {
     version?: string | null;
   }
   /**
-   * `Authentication` defines the authentication configuration for an API. Example for an API targeted for external use: name: calendar.googleapis.com authentication: providers: - id: google_calendar_auth jwks_uri: https://www.googleapis.com/oauth2/v1/certs issuer: https://securetoken.google.com rules: - selector: "*" requirements: provider_id: google_calendar_auth
+   * `Authentication` defines the authentication configuration for API methods provided by an API service. Example: name: calendar.googleapis.com authentication: providers: - id: google_calendar_auth jwks_uri: https://www.googleapis.com/oauth2/v1/certs issuer: https://securetoken.google.com rules: - selector: "*" requirements: provider_id: google_calendar_auth - selector: google.calendar.Delegate oauth: canonical_scopes: https://www.googleapis.com/auth/calendar.read
    */
   export interface Schema$Authentication {
     /**
@@ -336,10 +336,6 @@ export namespace servicenetworking_v1beta {
      * 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 | null;
-    /**
-     * Minimum deadline in seconds needed for this method. Calls having deadline value lower than this will be rejected.
-     */
-    minDeadline?: number | null;
     /**
      * The number of seconds to wait for the completion of a long running operation. The default is no deadline.
      */
@@ -485,11 +481,11 @@ export namespace servicenetworking_v1beta {
     selector?: string | null;
   }
   /**
-   * Selects and configures the service controller used by the service. The service controller handles features like abuse, quota, billing, logging, monitoring, etc.
+   * Selects and configures the service controller used by the service. The service controller handles two things: - **What is allowed:** for each API request, Chemist checks the project status, activation status, abuse status, billing status, service status, location restrictions, VPC Service Controls, SuperQuota, and other policies. - **What has happened:** for each API response, Chemist reports the telemetry data to analytics, auditing, billing, eventing, logging, monitoring, sawmill, and tracing. Chemist also accepts telemetry data not associated with API traffic, such as billing metrics. Example: control: environment: servicecontrol.googleapis.com
    */
   export interface Schema$Control {
     /**
-     * The service control environment to use. If empty, no control plane feature (like quota and billing) will be enabled.
+     * The service controller environment to use. If empty, no control plane feature (like quota and billing) will be enabled. The recommended value for most services is servicecontrol.googleapis.com
      */
     environment?: string | null;
   }
@@ -599,7 +595,7 @@ export namespace servicenetworking_v1beta {
      */
     serviceRootUrl?: string | null;
     /**
-     * A short summary of what the service does. Can only be provided by plain text.
+     * A short description of what the service does. The summary must be plain text. It becomes the overview of the service displayed in Google Cloud Console. NOTE: This field is equivalent to the standard field `description`.
      */
     summary?: string | null;
   }
@@ -612,22 +608,18 @@ export namespace servicenetworking_v1beta {
      */
     deprecationDescription?: string | null;
     /**
-     * Description of the selected API(s).
+     * Description of the selected proto element (e.g. a message, a method, a 'service' definition, or a field). Defaults to leading & trailing comments taken from the proto source definition of the proto element.
      */
     description?: string | null;
     /**
-     * The selector is a comma-separated list of patterns. Each pattern is a qualified name of the element which may end in "*", indicating a wildcard. Wildcards are only allowed at the end and for a whole component of the qualified name, i.e. "foo.*" is ok, but not "foo.b*" or "foo.*.bar". A wildcard will match one or more components. To specify a default for all applicable elements, the whole pattern "*" is used.
+     * The selector is a comma-separated list of patterns for any element such as a method, a field, an enum value. Each pattern is a qualified name of the element which may end in "*", indicating a wildcard. Wildcards are only allowed at the end and for a whole component of the qualified name, i.e. "foo.*" is ok, but not "foo.b*" or "foo.*.bar". A wildcard will match one or more components. To specify a default for all applicable elements, the whole pattern "*" is used.
      */
     selector?: string | null;
   }
   /**
-   * `Endpoint` describes a network endpoint of a service that serves a set of APIs. It is commonly known as a service endpoint. A service may expose any number of service endpoints, and all service endpoints share the same service definition, such as quota limits and monitoring metrics. Example service configuration: name: library-example.googleapis.com endpoints: # Below entry makes 'google.example.library.v1.Library' # API be served from endpoint address library-example.googleapis.com. # It also allows HTTP OPTIONS calls to be passed to the backend, for # it to decide whether the subsequent cross-origin request is # allowed to proceed. - name: library-example.googleapis.com allow_cors: true
+   * `Endpoint` describes a network address of a service that serves a set of APIs. It is commonly known as a service endpoint. A service may expose any number of service endpoints, and all service endpoints share the same service definition, such as quota limits and monitoring metrics. Example: type: google.api.Service name: library-example.googleapis.com endpoints: # Declares network address `https://library-example.googleapis.com` # for service `library-example.googleapis.com`. The `https` scheme # is implicit for all service endpoints. Other schemes may be # supported in the future. - name: library-example.googleapis.com allow_cors: false - name: content-staging-library-example.googleapis.com # Allows HTTP OPTIONS calls to be passed to the API frontend, for it # to decide whether the subsequent cross-origin request is allowed # to proceed. allow_cors: true
    */
   export interface Schema$Endpoint {
-    /**
-     * DEPRECATED: This field is no longer supported. Instead of using aliases, please specify multiple google.api.Endpoint for each of the intended aliases. Additional names that this endpoint will be hosted on.
-     */
-    aliases?: string[] | null;
     /**
      * Allowing [CORS](https://en.wikipedia.org/wiki/Cross-origin_resource_sharing), aka cross-domain traffic, would allow the backends served from this endpoint to receive and respond to HTTP OPTIONS requests. The response will be used by the browser to determine whether the subsequent cross-origin request is allowed to proceed.
      */
@@ -1085,7 +1077,7 @@ export namespace servicenetworking_v1beta {
      */
     name?: string | null;
     /**
-     * Required. The monitored resource type. For example, the type `"cloudsql_database"` represents databases in Google Cloud SQL.
+     * Required. The monitored resource type. For example, the type `"cloudsql_database"` represents databases in Google Cloud SQL. For a list of types, see [Monitoring resource types](https://cloud.google.com/monitoring/api/resources) and [Logging resource types](https://cloud.google.com/logging/docs/api/v2/resource-list).
      */
     type?: string | null;
   }
@@ -1167,7 +1159,7 @@ export namespace servicenetworking_v1beta {
    */
   export interface Schema$Page {
     /**
-     * The Markdown content of the page. You can use (== include {path\} ==) to include content from a Markdown file.
+     * 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 | null;
     /**
@@ -1179,12 +1171,16 @@ export namespace servicenetworking_v1beta {
      */
     subpages?: Schema$Page[];
   }
+  /**
+   * Metadata provided through GetOperation request for the LRO generated by Partial Delete Connection API
+   */
+  export interface Schema$PartialDeleteConnectionMetadata {}
   /**
    * DNS domain suffix for which requests originating in the producer VPC network are resolved in the associated consumer VPC network.
    */
   export interface Schema$PeeredDnsDomain {
     /**
-     * The DNS domain name suffix e.g. `example.com.`.
+     * The DNS domain name suffix e.g. `example.com.`. Cloud DNS requires that a DNS suffix ends with a trailing dot.
      */
     dnsSuffix?: string | null;
     /**
@@ -1341,7 +1337,7 @@ export namespace servicenetworking_v1beta {
     rangeName?: string | null;
   }
   /**
-   * `Service` is the root object of Google service configuration schema. It describes basic information about a service, such as the name and the title, and delegates other aspects to sub-sections. Each sub-section is either a proto message or a repeated proto message that configures a specific aspect, such as auth. See each proto message definition for details. Example: type: google.api.Service name: calendar.googleapis.com title: Google Calendar API apis: - name: google.calendar.v3.Calendar authentication: providers: - id: google_calendar_auth jwks_uri: https://www.googleapis.com/oauth2/v1/certs issuer: https://securetoken.google.com rules: - selector: "*" requirements: provider_id: google_calendar_auth
+   * `Service` is the root object of Google API service configuration (service config). It describes the basic information about a logical service, such as the service name and the user-facing title, and delegates other aspects to sub-sections. Each sub-section is either a proto message or a repeated proto message that configures a specific aspect, such as auth. For more information, see each proto message definition. Example: type: google.api.Service name: calendar.googleapis.com title: Google Calendar API apis: - name: google.calendar.v3.Calendar visibility: rules: - selector: "google.calendar.v3.*" restriction: PREVIEW backend: rules: - selector: "google.calendar.v3.*" address: calendar.example.com authentication: providers: - id: google_calendar_auth jwks_uri: https://www.googleapis.com/oauth2/v1/certs issuer: https://securetoken.google.com rules: - selector: "*" requirements: provider_id: google_calendar_auth
    */
   export interface Schema$Service {
     /**
@@ -1361,7 +1357,7 @@ export namespace servicenetworking_v1beta {
      */
     billing?: Schema$Billing;
     /**
-     * Deprecated. The service config compiler always sets this field to `3`.
+     * Obsolete. Do not use. This field has no semantic meaning. The service config compiler always sets this field to `3`.
      */
     configVersion?: number | null;
     /**
@@ -1385,7 +1381,7 @@ export namespace servicenetworking_v1beta {
      */
     endpoints?: Schema$Endpoint[];
     /**
-     * A list of all enum types included in this API service. Enums referenced directly or indirectly by the `apis` are automatically included. Enums which are not referenced but shall be included should be listed here by name. Example: enums: - name: google.someapi.v1.SomeEnum
+     * A list of all enum types included in this API service. Enums referenced directly or indirectly by the `apis` are automatically included. Enums which are not referenced but shall be included should be listed here by name by the configuration author. Example: enums: - name: google.someapi.v1.SomeEnum
      */
     enums?: Schema$Enum[];
     /**
@@ -1441,11 +1437,11 @@ export namespace servicenetworking_v1beta {
      */
     systemTypes?: Schema$Type[];
     /**
-     * The product title for this service.
+     * The product title for this service, it is the name displayed in Google Cloud Console.
      */
     title?: string | null;
     /**
-     * A list of all proto message types included in this API service. Types referenced directly or indirectly by the `apis` are automatically included. Messages which are not referenced but shall be included, such as types used by the `google.protobuf.Any` type, should be listed here by name. Example: types: - name: google.protobuf.Int32
+     * A list of all proto message types included in this API service. Types referenced directly or indirectly by the `apis` are automatically included. Messages which are not referenced but shall be included, such as types used by the `google.protobuf.Any` type, should be listed here by name by the configuration author. Example: types: - name: google.protobuf.Int32
      */
     types?: Schema$Type[];
     /**