Skip to content

Commit d9c4396

Browse files
fix(serviceusage): update the api
#### serviceusage:v1 The following keys were changed: - resources.operations.methods.cancel (Total Keys: 1) - resources.operations.methods.delete (Total Keys: 1) - resources.operations.methods.get (Total Keys: 1) - resources.operations.methods.list (Total Keys: 1) - resources.services.methods.batchEnable (Total Keys: 1) - resources.services.methods.batchGet (Total Keys: 1) - resources.services.methods.disable (Total Keys: 1) - resources.services.methods.enable (Total Keys: 1) - resources.services.methods.get (Total Keys: 1) - resources.services.methods.list (Total Keys: 1) #### serviceusage:v1beta1 The following keys were changed: - resources.operations.methods.get (Total Keys: 1) - resources.operations.methods.list (Total Keys: 1) - resources.services.methods.batchEnable (Total Keys: 1) - resources.services.methods.disable (Total Keys: 1) - resources.services.methods.enable (Total Keys: 1) - resources.services.methods.generateServiceIdentity (Total Keys: 1) - resources.services.methods.get (Total Keys: 1) - resources.services.methods.list (Total Keys: 1) - resources.services.resources.consumerQuotaMetrics.methods.get (Total Keys: 1) - resources.services.resources.consumerQuotaMetrics.methods.importAdminOverrides (Total Keys: 1) - resources.services.resources.consumerQuotaMetrics.methods.importConsumerOverrides (Total Keys: 1) - resources.services.resources.consumerQuotaMetrics.methods.list (Total Keys: 1) - resources.services.resources.consumerQuotaMetrics.resources.limits.methods.get (Total Keys: 1) - resources.services.resources.consumerQuotaMetrics.resources.limits.resources.adminOverrides.methods.create (Total Keys: 1) - resources.services.resources.consumerQuotaMetrics.resources.limits.resources.adminOverrides.methods.delete (Total Keys: 1) - resources.services.resources.consumerQuotaMetrics.resources.limits.resources.adminOverrides.methods.list (Total Keys: 1) - resources.services.resources.consumerQuotaMetrics.resources.limits.resources.adminOverrides.methods.patch (Total Keys: 1) - resources.services.resources.consumerQuotaMetrics.resources.limits.resources.consumerOverrides.methods.create (Total Keys: 1) - resources.services.resources.consumerQuotaMetrics.resources.limits.resources.consumerOverrides.methods.delete (Total Keys: 1) - resources.services.resources.consumerQuotaMetrics.resources.limits.resources.consumerOverrides.methods.list (Total Keys: 1) - resources.services.resources.consumerQuotaMetrics.resources.limits.resources.consumerOverrides.methods.patch (Total Keys: 1)
1 parent 634ef34 commit d9c4396

8 files changed

+137
-180
lines changed

docs/dyn/serviceusage_v1.services.html

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -204,7 +204,7 @@ <h3>Method Details</h3>
204204
&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.
205205
},
206206
],
207-
&quot;authentication&quot;: { # `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: &quot;*&quot; requirements: provider_id: google_calendar_auth # Auth configuration. Contains only the OAuth rules.
207+
&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. Contains only the OAuth rules.
208208
&quot;providers&quot;: [ # Defines a set of authentication providers that a service supports.
209209
{ # Configuration for an authentication provider, including support for [JSON Web Token (JWT)](https://tools.ietf.org/html/draft-ietf-oauth-json-web-token-32).
210210
&quot;audiences&quot;: &quot;A String&quot;, # The list of JWT [audiences](https://tools.ietf.org/html/draft-ietf-oauth-json-web-token-32#section-4.1.3). that are allowed to access. A JWT containing any of these audiences will be accepted. When this setting is absent, JWTs with audiences: - &quot;https://[service.name]/[google.protobuf.Api.name]&quot; - &quot;https://[service.name]/&quot; will be accepted. For example, if no audiences are in the setting, LibraryService API will accept JWTs with the following audiences: - https://library-example.googleapis.com/google.example.library.v1.LibraryService - https://library-example.googleapis.com/ Example: audiences: bookstore_android.apps.googleusercontent.com, bookstore_web.apps.googleusercontent.com
@@ -497,7 +497,7 @@ <h3>Method Details</h3>
497497
&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.
498498
},
499499
],
500-
&quot;authentication&quot;: { # `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: &quot;*&quot; requirements: provider_id: google_calendar_auth # Auth configuration. Contains only the OAuth rules.
500+
&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. Contains only the OAuth rules.
501501
&quot;providers&quot;: [ # Defines a set of authentication providers that a service supports.
502502
{ # Configuration for an authentication provider, including support for [JSON Web Token (JWT)](https://tools.ietf.org/html/draft-ietf-oauth-json-web-token-32).
503503
&quot;audiences&quot;: &quot;A String&quot;, # The list of JWT [audiences](https://tools.ietf.org/html/draft-ietf-oauth-json-web-token-32#section-4.1.3). that are allowed to access. A JWT containing any of these audiences will be accepted. When this setting is absent, JWTs with audiences: - &quot;https://[service.name]/[google.protobuf.Api.name]&quot; - &quot;https://[service.name]/&quot; will be accepted. For example, if no audiences are in the setting, LibraryService API will accept JWTs with the following audiences: - https://library-example.googleapis.com/google.example.library.v1.LibraryService - https://library-example.googleapis.com/ Example: audiences: bookstore_android.apps.googleusercontent.com, bookstore_web.apps.googleusercontent.com
@@ -705,7 +705,7 @@ <h3>Method Details</h3>
705705
&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.
706706
},
707707
],
708-
&quot;authentication&quot;: { # `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: &quot;*&quot; requirements: provider_id: google_calendar_auth # Auth configuration. Contains only the OAuth rules.
708+
&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. Contains only the OAuth rules.
709709
&quot;providers&quot;: [ # Defines a set of authentication providers that a service supports.
710710
{ # Configuration for an authentication provider, including support for [JSON Web Token (JWT)](https://tools.ietf.org/html/draft-ietf-oauth-json-web-token-32).
711711
&quot;audiences&quot;: &quot;A String&quot;, # The list of JWT [audiences](https://tools.ietf.org/html/draft-ietf-oauth-json-web-token-32#section-4.1.3). that are allowed to access. A JWT containing any of these audiences will be accepted. When this setting is absent, JWTs with audiences: - &quot;https://[service.name]/[google.protobuf.Api.name]&quot; - &quot;https://[service.name]/&quot; will be accepted. For example, if no audiences are in the setting, LibraryService API will accept JWTs with the following audiences: - https://library-example.googleapis.com/google.example.library.v1.LibraryService - https://library-example.googleapis.com/ Example: audiences: bookstore_android.apps.googleusercontent.com, bookstore_web.apps.googleusercontent.com

0 commit comments

Comments
 (0)