Skip to content

Commit c0d2bb2

Browse files
feat(servicemanagement): update the api
#### servicemanagement:v1 The following keys were added: - schemas.Aspect (Total Keys: 5) - schemas.BackendRule.properties.loadBalancingPolicy.type (Total Keys: 1) - schemas.Service.properties.aspects (Total Keys: 2)
1 parent 132cc3f commit c0d2bb2

File tree

3 files changed

+76
-1
lines changed

3 files changed

+76
-1
lines changed

docs/dyn/servicemanagement_v1.services.configs.html

Lines changed: 36 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -150,6 +150,14 @@ <h3>Method Details</h3>
150150
&quot;version&quot;: &quot;A String&quot;, # 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.
151151
},
152152
],
153+
&quot;aspects&quot;: [ # 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.
154+
{ # Aspect represents Generic aspect. It is used to configure an aspect without making direct changes to service.proto
155+
&quot;kind&quot;: &quot;A String&quot;, # The type of this aspect configuration.
156+
&quot;spec&quot;: { # Content of the configuration. The underlying schema should be defined by Aspect owners as protobuf message under `apiserving/configaspects/proto`.
157+
&quot;a_key&quot;: &quot;&quot;, # Properties of the object.
158+
},
159+
},
160+
],
153161
&quot;authentication&quot;: { # `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: &quot;*&quot; requirements: provider_id: google_calendar_auth - selector: google.calendar.Delegate oauth: canonical_scopes: https://www.googleapis.com/auth/calendar.read # Auth configuration.
154162
&quot;providers&quot;: [ # Defines a set of authentication providers that a service supports.
155163
{ # Configuration for an authentication provider, including support for [JSON Web Token (JWT)](https://tools.ietf.org/html/draft-ietf-oauth-json-web-token-32).
@@ -191,6 +199,7 @@ <h3>Method Details</h3>
191199
&quot;deadline&quot;: 3.14, # The number of seconds to wait for a response from a request. The default varies based on the request protocol and deployment environment.
192200
&quot;disableAuth&quot;: True or False, # When disable_auth is true, a JWT ID token won&#x27;t be generated and the original &quot;Authorization&quot; HTTP header will be preserved. If the header is used to carry the original token and is expected by the backend, this field must be set to true to preserve the header.
193201
&quot;jwtAudience&quot;: &quot;A String&quot;, # The JWT audience is used when generating a JWT ID token for the backend. This ID token will be added in the HTTP &quot;authorization&quot; header, and sent to the backend.
202+
&quot;loadBalancingPolicy&quot;: &quot;A String&quot;, # 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, &quot;RoundRobin&quot;.
194203
&quot;minDeadline&quot;: 3.14, # Deprecated, do not use.
195204
&quot;operationDeadline&quot;: 3.14, # The number of seconds to wait for the completion of a long running operation. The default is no deadline.
196205
&quot;overridesByRequestProtocol&quot;: { # The map between request protocol and the backend address.
@@ -825,6 +834,14 @@ <h3>Method Details</h3>
825834
&quot;version&quot;: &quot;A String&quot;, # 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.
826835
},
827836
],
837+
&quot;aspects&quot;: [ # 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.
838+
{ # Aspect represents Generic aspect. It is used to configure an aspect without making direct changes to service.proto
839+
&quot;kind&quot;: &quot;A String&quot;, # The type of this aspect configuration.
840+
&quot;spec&quot;: { # Content of the configuration. The underlying schema should be defined by Aspect owners as protobuf message under `apiserving/configaspects/proto`.
841+
&quot;a_key&quot;: &quot;&quot;, # Properties of the object.
842+
},
843+
},
844+
],
828845
&quot;authentication&quot;: { # `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: &quot;*&quot; requirements: provider_id: google_calendar_auth - selector: google.calendar.Delegate oauth: canonical_scopes: https://www.googleapis.com/auth/calendar.read # Auth configuration.
829846
&quot;providers&quot;: [ # Defines a set of authentication providers that a service supports.
830847
{ # Configuration for an authentication provider, including support for [JSON Web Token (JWT)](https://tools.ietf.org/html/draft-ietf-oauth-json-web-token-32).
@@ -866,6 +883,7 @@ <h3>Method Details</h3>
866883
&quot;deadline&quot;: 3.14, # The number of seconds to wait for a response from a request. The default varies based on the request protocol and deployment environment.
867884
&quot;disableAuth&quot;: True or False, # When disable_auth is true, a JWT ID token won&#x27;t be generated and the original &quot;Authorization&quot; HTTP header will be preserved. If the header is used to carry the original token and is expected by the backend, this field must be set to true to preserve the header.
868885
&quot;jwtAudience&quot;: &quot;A String&quot;, # The JWT audience is used when generating a JWT ID token for the backend. This ID token will be added in the HTTP &quot;authorization&quot; header, and sent to the backend.
886+
&quot;loadBalancingPolicy&quot;: &quot;A String&quot;, # 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, &quot;RoundRobin&quot;.
869887
&quot;minDeadline&quot;: 3.14, # Deprecated, do not use.
870888
&quot;operationDeadline&quot;: 3.14, # The number of seconds to wait for the completion of a long running operation. The default is no deadline.
871889
&quot;overridesByRequestProtocol&quot;: { # The map between request protocol and the backend address.
@@ -1512,6 +1530,14 @@ <h3>Method Details</h3>
15121530
&quot;version&quot;: &quot;A String&quot;, # 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.
15131531
},
15141532
],
1533+
&quot;aspects&quot;: [ # 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.
1534+
{ # Aspect represents Generic aspect. It is used to configure an aspect without making direct changes to service.proto
1535+
&quot;kind&quot;: &quot;A String&quot;, # The type of this aspect configuration.
1536+
&quot;spec&quot;: { # Content of the configuration. The underlying schema should be defined by Aspect owners as protobuf message under `apiserving/configaspects/proto`.
1537+
&quot;a_key&quot;: &quot;&quot;, # Properties of the object.
1538+
},
1539+
},
1540+
],
15151541
&quot;authentication&quot;: { # `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: &quot;*&quot; requirements: provider_id: google_calendar_auth - selector: google.calendar.Delegate oauth: canonical_scopes: https://www.googleapis.com/auth/calendar.read # Auth configuration.
15161542
&quot;providers&quot;: [ # Defines a set of authentication providers that a service supports.
15171543
{ # Configuration for an authentication provider, including support for [JSON Web Token (JWT)](https://tools.ietf.org/html/draft-ietf-oauth-json-web-token-32).
@@ -1553,6 +1579,7 @@ <h3>Method Details</h3>
15531579
&quot;deadline&quot;: 3.14, # The number of seconds to wait for a response from a request. The default varies based on the request protocol and deployment environment.
15541580
&quot;disableAuth&quot;: True or False, # When disable_auth is true, a JWT ID token won&#x27;t be generated and the original &quot;Authorization&quot; HTTP header will be preserved. If the header is used to carry the original token and is expected by the backend, this field must be set to true to preserve the header.
15551581
&quot;jwtAudience&quot;: &quot;A String&quot;, # The JWT audience is used when generating a JWT ID token for the backend. This ID token will be added in the HTTP &quot;authorization&quot; header, and sent to the backend.
1582+
&quot;loadBalancingPolicy&quot;: &quot;A String&quot;, # 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, &quot;RoundRobin&quot;.
15561583
&quot;minDeadline&quot;: 3.14, # Deprecated, do not use.
15571584
&quot;operationDeadline&quot;: 3.14, # The number of seconds to wait for the completion of a long running operation. The default is no deadline.
15581585
&quot;overridesByRequestProtocol&quot;: { # The map between request protocol and the backend address.
@@ -2199,6 +2226,14 @@ <h3>Method Details</h3>
21992226
&quot;version&quot;: &quot;A String&quot;, # 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.
22002227
},
22012228
],
2229+
&quot;aspects&quot;: [ # 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.
2230+
{ # Aspect represents Generic aspect. It is used to configure an aspect without making direct changes to service.proto
2231+
&quot;kind&quot;: &quot;A String&quot;, # The type of this aspect configuration.
2232+
&quot;spec&quot;: { # Content of the configuration. The underlying schema should be defined by Aspect owners as protobuf message under `apiserving/configaspects/proto`.
2233+
&quot;a_key&quot;: &quot;&quot;, # Properties of the object.
2234+
},
2235+
},
2236+
],
22022237
&quot;authentication&quot;: { # `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: &quot;*&quot; requirements: provider_id: google_calendar_auth - selector: google.calendar.Delegate oauth: canonical_scopes: https://www.googleapis.com/auth/calendar.read # Auth configuration.
22032238
&quot;providers&quot;: [ # Defines a set of authentication providers that a service supports.
22042239
{ # Configuration for an authentication provider, including support for [JSON Web Token (JWT)](https://tools.ietf.org/html/draft-ietf-oauth-json-web-token-32).
@@ -2240,6 +2275,7 @@ <h3>Method Details</h3>
22402275
&quot;deadline&quot;: 3.14, # The number of seconds to wait for a response from a request. The default varies based on the request protocol and deployment environment.
22412276
&quot;disableAuth&quot;: True or False, # When disable_auth is true, a JWT ID token won&#x27;t be generated and the original &quot;Authorization&quot; HTTP header will be preserved. If the header is used to carry the original token and is expected by the backend, this field must be set to true to preserve the header.
22422277
&quot;jwtAudience&quot;: &quot;A String&quot;, # The JWT audience is used when generating a JWT ID token for the backend. This ID token will be added in the HTTP &quot;authorization&quot; header, and sent to the backend.
2278+
&quot;loadBalancingPolicy&quot;: &quot;A String&quot;, # 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, &quot;RoundRobin&quot;.
22432279
&quot;minDeadline&quot;: 3.14, # Deprecated, do not use.
22442280
&quot;operationDeadline&quot;: 3.14, # The number of seconds to wait for the completion of a long running operation. The default is no deadline.
22452281
&quot;overridesByRequestProtocol&quot;: { # The map between request protocol and the backend address.

0 commit comments

Comments
 (0)