google-apis-servicemanagement_v1 0.57.0 → 0.58.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: '015278d2313f68d1ed7fe9d67f508b37effbda5a99fa1ecd5b8bfc23f6433db4'
-  data.tar.gz: f2441645112127774cba293059b73313e0d596a3e641e2c91acfe4d7babfb660
+  metadata.gz: 65abbc5d017fac8e4657fb5a06d6903f4530ac6f8221a8caf72708703b5cc617
+  data.tar.gz: a854a6d548eb690602313ecc2b7fb5104455b4554ff2472401b6913ee5183058
 SHA512:
-  metadata.gz: 5b3a4642e967f9d2252f728efc2b3e96fa9f40d5943e9953673aa6b064a5745623a6cd621e3869438d91eaab95df7cbfdeefe919e091a666e4a53b0b0d378cd8
-  data.tar.gz: f571c5f88ee9dfa315200cf7410e4e472371293c07614dc28ab6785125310b979e7159ea3037e085270cc8553e0e7e64cbb5f46ecfc251418faa3b56c0362ea8
+  metadata.gz: 2f0a3e35950b3aff60a860226b1995e7e5728747ffd0af35db5c2c915d99461439bb2e3a7f442ca4d05a6ac864afc8540597b9802985b1d5e014320bab9014cb
+  data.tar.gz: 596e06c207415778d72b399ad650df327e4fadaa45890e9f1d26ac34903f7efa8aa93dcde5ccb6314e68ce692f06f5fd2f4fa068ca154eb6395b5520a4c224c2

data/CHANGELOG.md

@@ -1,5 +1,9 @@
 # Release history for google-apis-servicemanagement_v1
 
+### v0.58.0 (2024-07-25)
+
+* Regenerated from discovery document revision 20240712
+
 ### v0.57.0 (2024-06-09)
 
 * Regenerated from discovery document revision 20240531

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

@@ -988,12 +988,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
@@ -2017,27 +2019,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 below selects a gRPC method and applies 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.
+      # 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/servicemanagement_v1/gem_version.rb

@@ -16,13 +16,13 @@ module Google
   module Apis
     module ServicemanagementV1
       # Version of the google-apis-servicemanagement_v1 gem
-      GEM_VERSION = "0.57.0"
+      GEM_VERSION = "0.58.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 = "20240531"
+      REVISION = "20240712"
     end
   end
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: google-apis-servicemanagement_v1
 version: !ruby/object:Gem::Version
-  version: 0.57.0
+  version: 0.58.0
 platform: ruby
 authors:
 - Google LLC
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2024-06-09 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-servicemanagement_v1/CHANGELOG.md
-  documentation_uri: https://googleapis.dev/ruby/google-apis-servicemanagement_v1/v0.57.0
+  documentation_uri: https://googleapis.dev/ruby/google-apis-servicemanagement_v1/v0.58.0
   source_code_uri: https://github.com/googleapis/google-api-ruby-client/tree/main/generated/google-apis-servicemanagement_v1
 post_install_message: 
 rdoc_options: []