google-apis-serviceusage_v1 0.52.0 → 0.54.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 942c1a12eb558adf93132c9d37a53831d62fd4b99a68eb59641ddac89fbd7a3a
-  data.tar.gz: 841df4f8e6f374a097d9e795d24f261ef25678c6430f1e52499a7a853ffaaeac
+  metadata.gz: 35dfc01a3dab09288fbd7db9979fdf5ec0966e6eb0d1dba129cb5b987f53d11e
+  data.tar.gz: 674b030fd883eccee57f0b99e691b7a78aa5fc516ae9b4d482e0bf186fee4824
 SHA512:
-  metadata.gz: df7ca334886a4c02eef80ca5d95bcde59676636b6ce31e691108caa65a2ef7481a6503f72c16f5395d9a3260422f8ecf6c46a6eab2ec74bfa32e07d52bf175a0
-  data.tar.gz: '0025093f2a2189741dd9c20e1d1d34ab5dd7eef879fa24da34419df2caef1e28cc1fa9798a4a92e92cb5238ea9ab458f5e28a0849fe00f331c5c8a5f5894a52d'
+  metadata.gz: 9712b4b3dbbeaa9fc1fb0160bfa81962bbff7c7fdb0fb542ae450cf8f1a20fb474d768dc720328710167499ab3227b523e648e026fd4b6bd9c8b78a5e98f8dea
+  data.tar.gz: 71899103ef5e874327bfa14001720c7fbf4968d07eca832e0c4d8af3eb9754a555b733aae2252313448809693dd54955e56c2cadf647c2bca00ec3afe02607df

data/CHANGELOG.md

@@ -1,5 +1,13 @@
 # Release history for google-apis-serviceusage_v1
 
+### v0.54.0 (2024-07-25)
+
+* Regenerated from discovery document revision 20240712
+
+### v0.53.0 (2024-06-09)
+
+* Regenerated from discovery document revision 20240602
+
 ### v0.52.0 (2024-05-19)
 
 * Regenerated using generator version 0.15.0

data/lib/google/apis/serviceusage_v1/classes.rb

@@ -912,12 +912,14 @@ module Google
         # @return [Array<String>]
         attr_accessor :allowed_response_extensions
       
-        # A list of full type names of provided contexts.
+        # A list of full type names of provided contexts. It is used to support
+        # propagating HTTP headers and ETags from the response extension.
         # Corresponds to the JSON property `provided`
         # @return [Array<String>]
         attr_accessor :provided
       
-        # A list of full type names of requested contexts.
+        # A list of full type names of requested contexts, only the requested context
+        # will be made available to the backend.
         # Corresponds to the JSON property `requested`
         # @return [Array<String>]
         attr_accessor :requested
@@ -2499,7 +2501,7 @@ module Google
         end
       end
       
-      # # gRPC Transcoding gRPC Transcoding is a feature for mapping between a gRPC
+      # gRPC Transcoding gRPC Transcoding is a feature for mapping between a gRPC
       # method and one or more HTTP REST endpoints. It allows developers to build a
       # single API service that supports both gRPC APIs and REST APIs. Many systems,
       # including [Google APIs](https://github.com/googleapis/googleapis), [Cloud
@@ -2519,70 +2521,69 @@ module Google
       # Message) ` option (google.api.http) = ` get: "/v1/`name=messages/*`" `; ` `
       # message GetMessageRequest ` string name = 1; // Mapped to URL path. ` message
       # Message ` string text = 1; // The resource content. ` This enables an HTTP
-      # REST to gRPC mapping as below: HTTP | gRPC -----|----- `GET /v1/messages/
-      # 123456` | `GetMessage(name: "messages/123456")` Any fields in the request
-      # message which are not bound by the path template automatically become HTTP
-      # query parameters if there is no HTTP request body. For example: service
-      # Messaging ` rpc GetMessage(GetMessageRequest) returns (Message) ` option (
-      # google.api.http) = ` get:"/v1/messages/`message_id`" `; ` ` message
-      # GetMessageRequest ` message SubMessage ` string subfield = 1; ` string
-      # message_id = 1; // Mapped to URL path. int64 revision = 2; // Mapped to URL
-      # query parameter `revision`. SubMessage sub = 3; // Mapped to URL query
-      # parameter `sub.subfield`. ` This enables a HTTP JSON to RPC mapping as below:
-      # HTTP | gRPC -----|----- `GET /v1/messages/123456?revision=2&sub.subfield=foo` |
-      # `GetMessage(message_id: "123456" revision: 2 sub: SubMessage(subfield: "foo"))
-      # ` Note that fields which are mapped to URL query parameters must have a
-      # primitive type or a repeated primitive type or a non-repeated message type. In
-      # the case of a repeated type, the parameter can be repeated in the URL as `...?
-      # param=A&param=B`. In the case of a message type, each field of the message is
-      # mapped to a separate parameter, such as `...?foo.a=A&foo.b=B&foo.c=C`. For
-      # HTTP methods that allow a request body, the `body` field specifies the mapping.
-      # Consider a REST update method on the message resource collection: service
-      # Messaging ` rpc UpdateMessage(UpdateMessageRequest) returns (Message) ` option
-      # (google.api.http) = ` patch: "/v1/messages/`message_id`" body: "message" `; ` `
-      # message UpdateMessageRequest ` string message_id = 1; // mapped to the URL
-      # Message message = 2; // mapped to the body ` The following HTTP JSON to RPC
-      # mapping is enabled, where the representation of the JSON in the request body
-      # is determined by protos JSON encoding: HTTP | gRPC -----|----- `PATCH /v1/
-      # messages/123456 ` "text": "Hi!" `` | `UpdateMessage(message_id: "123456"
-      # message ` text: "Hi!" `)` The special name `*` can be used in the body mapping
-      # to define that every field not bound by the path template should be mapped to
-      # the request body. This enables the following alternative definition of the
-      # update method: service Messaging ` rpc UpdateMessage(Message) returns (Message)
-      # ` option (google.api.http) = ` patch: "/v1/messages/`message_id`" body: "*" `;
-      # ` ` message Message ` string message_id = 1; string text = 2; ` The following
-      # HTTP JSON to RPC mapping is enabled: HTTP | gRPC -----|----- `PATCH /v1/
-      # messages/123456 ` "text": "Hi!" `` | `UpdateMessage(message_id: "123456" text:
-      # "Hi!")` Note that when using `*` in the body mapping, it is not possible to
-      # have HTTP parameters, as all fields not bound by the path end in the body.
-      # This makes this option more rarely used in practice when defining REST APIs.
-      # The common usage of `*` is in custom methods which don't use the URL at all
-      # for transferring data. It is possible to define multiple HTTP methods for one
-      # RPC by using the `additional_bindings` option. Example: service Messaging `
-      # rpc GetMessage(GetMessageRequest) returns (Message) ` option (google.api.http)
-      # = ` get: "/v1/messages/`message_id`" additional_bindings ` get: "/v1/users/`
-      # user_id`/messages/`message_id`" ` `; ` ` message GetMessageRequest ` string
-      # message_id = 1; string user_id = 2; ` This enables the following two
-      # alternative HTTP JSON to RPC mappings: HTTP | gRPC -----|----- `GET /v1/
-      # messages/123456` | `GetMessage(message_id: "123456")` `GET /v1/users/me/
-      # messages/123456` | `GetMessage(user_id: "me" message_id: "123456")` ## Rules
-      # for HTTP mapping 1. Leaf request fields (recursive expansion nested messages
-      # in the request message) are classified into three categories: - Fields
-      # referred by the path template. They are passed via the URL path. - Fields
-      # referred by the HttpRule.body. They are passed via the HTTP request body. -
-      # All other fields are passed via the URL query parameters, and the parameter
-      # name is the field path in the request message. A repeated field can be
-      # represented as multiple query parameters under the same name. 2. If HttpRule.
-      # body is "*", there is no URL query parameter, all fields are passed via URL
-      # path and HTTP request body. 3. If HttpRule.body is omitted, there is no HTTP
-      # request body, all fields are passed via URL path and URL query parameters. ###
-      # Path template syntax Template = "/" Segments [ Verb ] ; Segments = Segment ` "/
-      # " Segment ` ; Segment = "*" | "**" | LITERAL | Variable ; Variable = "`"
-      # FieldPath [ "=" Segments ] "`" ; FieldPath = IDENT ` "." IDENT ` ; Verb = ":"
-      # LITERAL ; The syntax `*` matches a single URL path segment. The syntax `**`
-      # matches zero or more URL path segments, which must be the last part of the URL
-      # path except the `Verb`. The syntax `Variable` matches part of the URL path as
-      # specified by its template. A variable template must not contain other
+      # REST to gRPC mapping as below: - HTTP: `GET /v1/messages/123456` - gRPC: `
+      # GetMessage(name: "messages/123456")` Any fields in the request message which
+      # are not bound by the path template automatically become HTTP query parameters
+      # if there is no HTTP request body. For example: service Messaging ` rpc
+      # GetMessage(GetMessageRequest) returns (Message) ` option (google.api.http) = `
+      # get:"/v1/messages/`message_id`" `; ` ` message GetMessageRequest ` message
+      # SubMessage ` string subfield = 1; ` string message_id = 1; // Mapped to URL
+      # path. int64 revision = 2; // Mapped to URL query parameter `revision`.
+      # SubMessage sub = 3; // Mapped to URL query parameter `sub.subfield`. ` This
+      # enables a HTTP JSON to RPC mapping as below: - HTTP: `GET /v1/messages/123456?
+      # revision=2&sub.subfield=foo` - gRPC: `GetMessage(message_id: "123456" revision:
+      # 2 sub: SubMessage(subfield: "foo"))` Note that fields which are mapped to URL
+      # query parameters must have a primitive type or a repeated primitive type or a
+      # non-repeated message type. In the case of a repeated type, the parameter can
+      # be repeated in the URL as `...?param=A&param=B`. In the case of a message type,
+      # each field of the message is mapped to a separate parameter, such as `...?foo.
+      # a=A&foo.b=B&foo.c=C`. For HTTP methods that allow a request body, the `body`
+      # field specifies the mapping. Consider a REST update method on the message
+      # resource collection: service Messaging ` rpc UpdateMessage(
+      # UpdateMessageRequest) returns (Message) ` option (google.api.http) = ` patch: "
+      # /v1/messages/`message_id`" body: "message" `; ` ` message UpdateMessageRequest
+      # ` string message_id = 1; // mapped to the URL Message message = 2; // mapped
+      # to the body ` The following HTTP JSON to RPC mapping is enabled, where the
+      # representation of the JSON in the request body is determined by protos JSON
+      # encoding: - HTTP: `PATCH /v1/messages/123456 ` "text": "Hi!" `` - gRPC: `
+      # UpdateMessage(message_id: "123456" message ` text: "Hi!" `)` The special name `
+      # *` can be used in the body mapping to define that every field not bound by the
+      # path template should be mapped to the request body. This enables the following
+      # alternative definition of the update method: service Messaging ` rpc
+      # UpdateMessage(Message) returns (Message) ` option (google.api.http) = ` patch:
+      # "/v1/messages/`message_id`" body: "*" `; ` ` message Message ` string
+      # message_id = 1; string text = 2; ` The following HTTP JSON to RPC mapping is
+      # enabled: - HTTP: `PATCH /v1/messages/123456 ` "text": "Hi!" `` - gRPC: `
+      # UpdateMessage(message_id: "123456" text: "Hi!")` Note that when using `*` in
+      # the body mapping, it is not possible to have HTTP parameters, as all fields
+      # not bound by the path end in the body. This makes this option more rarely used
+      # in practice when defining REST APIs. The common usage of `*` is in custom
+      # methods which don't use the URL at all for transferring data. It is possible
+      # to define multiple HTTP methods for one RPC by using the `additional_bindings`
+      # option. Example: service Messaging ` rpc GetMessage(GetMessageRequest) returns
+      # (Message) ` option (google.api.http) = ` get: "/v1/messages/`message_id`"
+      # additional_bindings ` get: "/v1/users/`user_id`/messages/`message_id`" ` `; ` `
+      # message GetMessageRequest ` string message_id = 1; string user_id = 2; ` This
+      # enables the following two alternative HTTP JSON to RPC mappings: - HTTP: `GET /
+      # v1/messages/123456` - gRPC: `GetMessage(message_id: "123456")` - HTTP: `GET /
+      # v1/users/me/messages/123456` - gRPC: `GetMessage(user_id: "me" message_id: "
+      # 123456")` Rules for HTTP mapping 1. Leaf request fields (recursive expansion
+      # nested messages in the request message) are classified into three categories: -
+      # Fields referred by the path template. They are passed via the URL path. -
+      # Fields referred by the HttpRule.body. They are passed via the HTTP request
+      # body. - All other fields are passed via the URL query parameters, and the
+      # parameter name is the field path in the request message. A repeated field can
+      # be represented as multiple query parameters under the same name. 2. If
+      # HttpRule.body is "*", there is no URL query parameter, all fields are passed
+      # via URL path and HTTP request body. 3. If HttpRule.body is omitted, there is
+      # no HTTP request body, all fields are passed via URL path and URL query
+      # parameters. Path template syntax Template = "/" Segments [ Verb ] ; Segments =
+      # Segment ` "/" Segment ` ; Segment = "*" | "**" | LITERAL | Variable ; Variable
+      # = "`" FieldPath [ "=" Segments ] "`" ; FieldPath = IDENT ` "." IDENT ` ; Verb =
+      # ":" LITERAL ; The syntax `*` matches a single URL path segment. The syntax `**
+      # ` matches zero or more URL path segments, which must be the last part of the
+      # URL path except the `Verb`. The syntax `Variable` matches part of the URL path
+      # as specified by its template. A variable template must not contain other
       # variables. If a variable matches a single path segment, its template may be
       # omitted, e.g. ``var`` is equivalent to ``var=*``. The syntax `LITERAL` matches
       # literal text in the URL path. If the `LITERAL` contains any reserved character,
@@ -2597,7 +2598,7 @@ module Google
       # except `[-_.~/0-9a-zA-Z]` are percent-encoded. The server side does the
       # reverse decoding, except "%2F" and "%2f" are left unchanged. Such variables
       # show up in the [Discovery Document](https://developers.google.com/discovery/v1/
-      # reference/apis) as ``+var``. ## Using gRPC API Service Configuration gRPC API
+      # reference/apis) as ``+var``. Using gRPC API Service Configuration gRPC API
       # Service Configuration (service config) is a configuration language for
       # configuring a gRPC service to become a user-facing product. The service config
       # is simply the YAML representation of the `google.api.Service` proto message.
@@ -2607,27 +2608,27 @@ module Google
       # effect as the proto annotation. This can be particularly useful if you have a
       # proto that is reused in multiple services. Note that any transcoding specified
       # in the service config will override any matching transcoding configuration in
-      # the proto. Example: http: rules: # Selects a gRPC method and applies HttpRule
-      # to it. - selector: example.v1.Messaging.GetMessage get: /v1/messages/`
-      # message_id`/`sub.subfield` ## Special notes When gRPC Transcoding is used to
-      # map a gRPC to JSON REST endpoints, the proto to JSON conversion must follow
-      # the [proto3 specification](https://developers.google.com/protocol-buffers/docs/
-      # proto3#json). While the single segment variable follows the semantics of [RFC
-      # 6570](https://tools.ietf.org/html/rfc6570) Section 3.2.2 Simple String
-      # Expansion, the multi segment variable **does not** follow RFC 6570 Section 3.2.
-      # 3 Reserved Expansion. The reason is that the Reserved Expansion does not
-      # expand special characters like `?` and `#`, which would lead to invalid URLs.
-      # As the result, gRPC Transcoding uses a custom encoding for multi segment
-      # variables. The path variables **must not** refer to any repeated or mapped
-      # field, because client libraries are not capable of handling such variable
-      # expansion. The path variables **must not** capture the leading "/" character.
-      # The reason is that the most common use case "`var`" does not capture the
-      # leading "/" character. For consistency, all path variables must share the same
-      # behavior. Repeated message fields must not be mapped to URL query parameters,
-      # because no client library can support such complicated mapping. If an API
-      # needs to use a JSON array for request or response body, it can map the request
-      # or response body to a repeated field. However, some gRPC Transcoding
-      # implementations may not support this feature.
+      # the proto. The following example selects a gRPC method and applies an `
+      # HttpRule` to it: http: rules: - selector: example.v1.Messaging.GetMessage get:
+      # /v1/messages/`message_id`/`sub.subfield` Special notes When gRPC Transcoding
+      # is used to map a gRPC to JSON REST endpoints, the proto to JSON conversion
+      # must follow the [proto3 specification](https://developers.google.com/protocol-
+      # buffers/docs/proto3#json). While the single segment variable follows the
+      # semantics of [RFC 6570](https://tools.ietf.org/html/rfc6570) Section 3.2.2
+      # Simple String Expansion, the multi segment variable **does not** follow RFC
+      # 6570 Section 3.2.3 Reserved Expansion. The reason is that the Reserved
+      # Expansion does not expand special characters like `?` and `#`, which would
+      # lead to invalid URLs. As the result, gRPC Transcoding uses a custom encoding
+      # for multi segment variables. The path variables **must not** refer to any
+      # repeated or mapped field, because client libraries are not capable of handling
+      # such variable expansion. The path variables **must not** capture the leading "/
+      # " character. The reason is that the most common use case "`var`" does not
+      # capture the leading "/" character. For consistency, all path variables must
+      # share the same behavior. Repeated message fields must not be mapped to URL
+      # query parameters, because no client library can support such complicated
+      # mapping. If an API needs to use a JSON array for request or response body, it
+      # can map the request or response body to a repeated field. However, some gRPC
+      # Transcoding implementations may not support this feature.
       class HttpRule
         include Google::Apis::Core::Hashable
       

data/lib/google/apis/serviceusage_v1/gem_version.rb

@@ -16,13 +16,13 @@ module Google
   module Apis
     module ServiceusageV1
       # Version of the google-apis-serviceusage_v1 gem
-      GEM_VERSION = "0.52.0"
+      GEM_VERSION = "0.54.0"
 
       # Version of the code generator used to generate this client
       GENERATOR_VERSION = "0.15.0"
 
       # Revision of the discovery document this client was generated from
-      REVISION = "20240429"
+      REVISION = "20240712"
     end
   end
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: google-apis-serviceusage_v1
 version: !ruby/object:Gem::Version
-  version: 0.52.0
+  version: 0.54.0
 platform: ruby
 authors:
 - Google LLC
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2024-05-19 00:00:00.000000000 Z
+date: 2024-07-25 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: google-apis-core
@@ -58,7 +58,7 @@ licenses:
 metadata:
   bug_tracker_uri: https://github.com/googleapis/google-api-ruby-client/issues
   changelog_uri: https://github.com/googleapis/google-api-ruby-client/tree/main/generated/google-apis-serviceusage_v1/CHANGELOG.md
-  documentation_uri: https://googleapis.dev/ruby/google-apis-serviceusage_v1/v0.52.0
+  documentation_uri: https://googleapis.dev/ruby/google-apis-serviceusage_v1/v0.54.0
   source_code_uri: https://github.com/googleapis/google-api-ruby-client/tree/main/generated/google-apis-serviceusage_v1
 post_install_message: 
 rdoc_options: []