google-apis-servicenetworking_v1 0.61.0 → 0.62.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: db79ef8e56cd0ae9c4ca4fcb3db2021c58b4cc49a5064d24fcde6581226af381
-  data.tar.gz: 54aa666c2c865b86ceab518f741ecd633f9622a60679b204be90e7c037049c4e
+  metadata.gz: 1d70c01b384e22264e5842da21bfb6702576dcea5c169a8520d0ad939be1949e
+  data.tar.gz: 6bc5facc3db40ca606a62714559e6d9236b85acdae9063d9adad17dc0a9531c0
 SHA512:
-  metadata.gz: 350a4182399b0515e9c1a4eb6f2f876ea3b163d93eaafc4198140c32ef91ae0cb9d00ffe7617e9c34abdec4e8e7745c9b6fd67493b78a5dc473b96d68aaa1341
-  data.tar.gz: 3e1c16b3c7c536c233a1c1655b77770353b5bb09546edec567aa7f3f7d841465fe878a1ddf564a7189cfc3606e91a6ce9c09e1fbd35ebdb642d744d6c2a4ceef
+  metadata.gz: 884099d7c41db42e0e81e802e52501c363ff31772cb96d4817f8ea45843b44d1394e2ffab42a8984d8893450f1ce6df2ab2f1aed550df5966c37deb440049af5
+  data.tar.gz: 4d3a9e939c7e39beac50eb5d7aa484bfabcaf2289f4df1c86e00dec37d40f8f35548574d4711450cb3b86dec95c86b8a041bff0052efdb28524f7b5ff91dbde5

data/CHANGELOG.md

@@ -1,5 +1,9 @@
 # Release history for google-apis-servicenetworking_v1
 
+### v0.62.0 (2024-07-25)
+
+* Regenerated from discovery document revision 20240716
+
 ### v0.61.0 (2024-06-30)
 
 * Regenerated from discovery document revision 20240626

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

@@ -1246,12 +1246,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
@@ -1575,17 +1577,14 @@ module Google
       # overview.md ==) - name: Tutorial content: (== include google/foo/tutorial.md ==
       # ) subpages: - name: Java content: (== include google/foo/tutorial_java.md ==)
       # rules: - selector: google.calendar.Calendar.Get description: > ... - selector:
-      # google.calendar.Calendar.Put description: > ... code_snippet_rules: - selector:
-      # google.calendar.Calendar.Delete code_snippets: - includes: - github_include:
-      # region_tag: calendar_delete code_language: JAVA account: GoogleCloudPlatform
-      # project: java-docs-samples file: calendar/delete.java Documentation is
-      # provided in markdown syntax. In addition to standard markdown features,
-      # definition lists, tables and fenced code blocks are supported. Section headers
-      # can be provided and are interpreted relative to the section nesting of the
-      # context where a documentation fragment is embedded. Documentation from the IDL
-      # is merged with documentation defined via the config at normalization time,
-      # where documentation provided by config rules overrides IDL provided. A number
-      # of constructs specific to the API platform are supported in documentation text.
+      # google.calendar.Calendar.Put description: > ... Documentation is provided in
+      # markdown syntax. In addition to standard markdown features, definition lists,
+      # tables and fenced code blocks are supported. Section headers can be provided
+      # and are interpreted relative to the section nesting of the context where a
+      # documentation fragment is embedded. Documentation from the IDL is merged with
+      # documentation defined via the config at normalization time, where
+      # documentation provided by config rules overrides IDL provided. A number of
+      # constructs specific to the API platform are supported in documentation text.
       # In order to reference a proto element, the following notation can be used: [
       # fully.qualified.proto.name][] To override the display text used for the link,
       # this can be used: [display text][fully.qualified.proto.name] Text can be
@@ -2372,27 +2371,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
       
@@ -4416,17 +4415,14 @@ module Google
         # overview.md ==) - name: Tutorial content: (== include google/foo/tutorial.md ==
         # ) subpages: - name: Java content: (== include google/foo/tutorial_java.md ==)
         # rules: - selector: google.calendar.Calendar.Get description: > ... - selector:
-        # google.calendar.Calendar.Put description: > ... code_snippet_rules: - selector:
-        # google.calendar.Calendar.Delete code_snippets: - includes: - github_include:
-        # region_tag: calendar_delete code_language: JAVA account: GoogleCloudPlatform
-        # project: java-docs-samples file: calendar/delete.java Documentation is
-        # provided in markdown syntax. In addition to standard markdown features,
-        # definition lists, tables and fenced code blocks are supported. Section headers
-        # can be provided and are interpreted relative to the section nesting of the
-        # context where a documentation fragment is embedded. Documentation from the IDL
-        # is merged with documentation defined via the config at normalization time,
-        # where documentation provided by config rules overrides IDL provided. A number
-        # of constructs specific to the API platform are supported in documentation text.
+        # google.calendar.Calendar.Put description: > ... Documentation is provided in
+        # markdown syntax. In addition to standard markdown features, definition lists,
+        # tables and fenced code blocks are supported. Section headers can be provided
+        # and are interpreted relative to the section nesting of the context where a
+        # documentation fragment is embedded. Documentation from the IDL is merged with
+        # documentation defined via the config at normalization time, where
+        # documentation provided by config rules overrides IDL provided. A number of
+        # constructs specific to the API platform are supported in documentation text.
         # In order to reference a proto element, the following notation can be used: [
         # fully.qualified.proto.name][] To override the display text used for the link,
         # this can be used: [display text][fully.qualified.proto.name] Text can be

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

@@ -16,13 +16,13 @@ module Google
   module Apis
     module ServicenetworkingV1
       # Version of the google-apis-servicenetworking_v1 gem
-      GEM_VERSION = "0.61.0"
+      GEM_VERSION = "0.62.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 = "20240626"
+      REVISION = "20240716"
     end
   end
 end

metadata

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