google-apis-servicemanagement_v1 0.55.0 → 0.57.0

Sign up to get free protection for your applications and to get access to all the features.
checksums.yaml CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  SHA256:
3
- metadata.gz: e5a5eb0cbca281a074fcd3a10692410ffa175fbfaa0bf347e35d235707cc52cd
4
- data.tar.gz: 8c46754743d6e1bbd6eff7640dd326ca2d706a324ff0618ea2c17b9b2c591ad8
3
+ metadata.gz: '015278d2313f68d1ed7fe9d67f508b37effbda5a99fa1ecd5b8bfc23f6433db4'
4
+ data.tar.gz: f2441645112127774cba293059b73313e0d596a3e641e2c91acfe4d7babfb660
5
5
  SHA512:
6
- metadata.gz: 622a191ca8a5ecf8bcd96bf901af4713f5250b95a2f9f86631bab040a468734cd4ec09dc8d2f2692d20111f3958131cab8e95fefbba2cd18eacbffa6def1d367
7
- data.tar.gz: e98d8fb1e935a2b7519c1803092a9d07e1238abc64f2773f33e77fdaef5ca87e579a7db9ceb86a39a652def591777fdd2f4b3f102a564d06845dcdbae22cc642
6
+ metadata.gz: 5b3a4642e967f9d2252f728efc2b3e96fa9f40d5943e9953673aa6b064a5745623a6cd621e3869438d91eaab95df7cbfdeefe919e091a666e4a53b0b0d378cd8
7
+ data.tar.gz: f571c5f88ee9dfa315200cf7410e4e472371293c07614dc28ab6785125310b979e7159ea3037e085270cc8553e0e7e64cbb5f46ecfc251418faa3b56c0362ea8
data/CHANGELOG.md CHANGED
@@ -1,5 +1,13 @@
1
1
  # Release history for google-apis-servicemanagement_v1
2
2
 
3
+ ### v0.57.0 (2024-06-09)
4
+
5
+ * Regenerated from discovery document revision 20240531
6
+
7
+ ### v0.56.0 (2024-05-19)
8
+
9
+ * Regenerated using generator version 0.15.0
10
+
3
11
  ### v0.55.0 (2024-05-05)
4
12
 
5
13
  * Regenerated from discovery document revision 20240426
@@ -1910,7 +1910,7 @@ module Google
1910
1910
  end
1911
1911
  end
1912
1912
 
1913
- # # gRPC Transcoding gRPC Transcoding is a feature for mapping between a gRPC
1913
+ # gRPC Transcoding gRPC Transcoding is a feature for mapping between a gRPC
1914
1914
  # method and one or more HTTP REST endpoints. It allows developers to build a
1915
1915
  # single API service that supports both gRPC APIs and REST APIs. Many systems,
1916
1916
  # including [Google APIs](https://github.com/googleapis/googleapis), [Cloud
@@ -1930,70 +1930,69 @@ module Google
1930
1930
  # Message) ` option (google.api.http) = ` get: "/v1/`name=messages/*`" `; ` `
1931
1931
  # message GetMessageRequest ` string name = 1; // Mapped to URL path. ` message
1932
1932
  # Message ` string text = 1; // The resource content. ` This enables an HTTP
1933
- # REST to gRPC mapping as below: HTTP | gRPC -----|----- `GET /v1/messages/
1934
- # 123456` | `GetMessage(name: "messages/123456")` Any fields in the request
1935
- # message which are not bound by the path template automatically become HTTP
1936
- # query parameters if there is no HTTP request body. For example: service
1937
- # Messaging ` rpc GetMessage(GetMessageRequest) returns (Message) ` option (
1938
- # google.api.http) = ` get:"/v1/messages/`message_id`" `; ` ` message
1939
- # GetMessageRequest ` message SubMessage ` string subfield = 1; ` string
1940
- # message_id = 1; // Mapped to URL path. int64 revision = 2; // Mapped to URL
1941
- # query parameter `revision`. SubMessage sub = 3; // Mapped to URL query
1942
- # parameter `sub.subfield`. ` This enables a HTTP JSON to RPC mapping as below:
1943
- # HTTP | gRPC -----|----- `GET /v1/messages/123456?revision=2&sub.subfield=foo` |
1944
- # `GetMessage(message_id: "123456" revision: 2 sub: SubMessage(subfield: "foo"))
1945
- # ` Note that fields which are mapped to URL query parameters must have a
1946
- # primitive type or a repeated primitive type or a non-repeated message type. In
1947
- # the case of a repeated type, the parameter can be repeated in the URL as `...?
1948
- # param=A&param=B`. In the case of a message type, each field of the message is
1949
- # mapped to a separate parameter, such as `...?foo.a=A&foo.b=B&foo.c=C`. For
1950
- # HTTP methods that allow a request body, the `body` field specifies the mapping.
1951
- # Consider a REST update method on the message resource collection: service
1952
- # Messaging ` rpc UpdateMessage(UpdateMessageRequest) returns (Message) ` option
1953
- # (google.api.http) = ` patch: "/v1/messages/`message_id`" body: "message" `; ` `
1954
- # message UpdateMessageRequest ` string message_id = 1; // mapped to the URL
1955
- # Message message = 2; // mapped to the body ` The following HTTP JSON to RPC
1956
- # mapping is enabled, where the representation of the JSON in the request body
1957
- # is determined by protos JSON encoding: HTTP | gRPC -----|----- `PATCH /v1/
1958
- # messages/123456 ` "text": "Hi!" `` | `UpdateMessage(message_id: "123456"
1959
- # message ` text: "Hi!" `)` The special name `*` can be used in the body mapping
1960
- # to define that every field not bound by the path template should be mapped to
1961
- # the request body. This enables the following alternative definition of the
1962
- # update method: service Messaging ` rpc UpdateMessage(Message) returns (Message)
1963
- # ` option (google.api.http) = ` patch: "/v1/messages/`message_id`" body: "*" `;
1964
- # ` ` message Message ` string message_id = 1; string text = 2; ` The following
1965
- # HTTP JSON to RPC mapping is enabled: HTTP | gRPC -----|----- `PATCH /v1/
1966
- # messages/123456 ` "text": "Hi!" `` | `UpdateMessage(message_id: "123456" text:
1967
- # "Hi!")` Note that when using `*` in the body mapping, it is not possible to
1968
- # have HTTP parameters, as all fields not bound by the path end in the body.
1969
- # This makes this option more rarely used in practice when defining REST APIs.
1970
- # The common usage of `*` is in custom methods which don't use the URL at all
1971
- # for transferring data. It is possible to define multiple HTTP methods for one
1972
- # RPC by using the `additional_bindings` option. Example: service Messaging `
1973
- # rpc GetMessage(GetMessageRequest) returns (Message) ` option (google.api.http)
1974
- # = ` get: "/v1/messages/`message_id`" additional_bindings ` get: "/v1/users/`
1975
- # user_id`/messages/`message_id`" ` `; ` ` message GetMessageRequest ` string
1976
- # message_id = 1; string user_id = 2; ` This enables the following two
1977
- # alternative HTTP JSON to RPC mappings: HTTP | gRPC -----|----- `GET /v1/
1978
- # messages/123456` | `GetMessage(message_id: "123456")` `GET /v1/users/me/
1979
- # messages/123456` | `GetMessage(user_id: "me" message_id: "123456")` ## Rules
1980
- # for HTTP mapping 1. Leaf request fields (recursive expansion nested messages
1981
- # in the request message) are classified into three categories: - Fields
1982
- # referred by the path template. They are passed via the URL path. - Fields
1983
- # referred by the HttpRule.body. They are passed via the HTTP request body. -
1984
- # All other fields are passed via the URL query parameters, and the parameter
1985
- # name is the field path in the request message. A repeated field can be
1986
- # represented as multiple query parameters under the same name. 2. If HttpRule.
1987
- # body is "*", there is no URL query parameter, all fields are passed via URL
1988
- # path and HTTP request body. 3. If HttpRule.body is omitted, there is no HTTP
1989
- # request body, all fields are passed via URL path and URL query parameters. ###
1990
- # Path template syntax Template = "/" Segments [ Verb ] ; Segments = Segment ` "/
1991
- # " Segment ` ; Segment = "*" | "**" | LITERAL | Variable ; Variable = "`"
1992
- # FieldPath [ "=" Segments ] "`" ; FieldPath = IDENT ` "." IDENT ` ; Verb = ":"
1993
- # LITERAL ; The syntax `*` matches a single URL path segment. The syntax `**`
1994
- # matches zero or more URL path segments, which must be the last part of the URL
1995
- # path except the `Verb`. The syntax `Variable` matches part of the URL path as
1996
- # specified by its template. A variable template must not contain other
1933
+ # REST to gRPC mapping as below: - HTTP: `GET /v1/messages/123456` - gRPC: `
1934
+ # GetMessage(name: "messages/123456")` Any fields in the request message which
1935
+ # are not bound by the path template automatically become HTTP query parameters
1936
+ # if there is no HTTP request body. For example: service Messaging ` rpc
1937
+ # GetMessage(GetMessageRequest) returns (Message) ` option (google.api.http) = `
1938
+ # get:"/v1/messages/`message_id`" `; ` ` message GetMessageRequest ` message
1939
+ # SubMessage ` string subfield = 1; ` string message_id = 1; // Mapped to URL
1940
+ # path. int64 revision = 2; // Mapped to URL query parameter `revision`.
1941
+ # SubMessage sub = 3; // Mapped to URL query parameter `sub.subfield`. ` This
1942
+ # enables a HTTP JSON to RPC mapping as below: - HTTP: `GET /v1/messages/123456?
1943
+ # revision=2&sub.subfield=foo` - gRPC: `GetMessage(message_id: "123456" revision:
1944
+ # 2 sub: SubMessage(subfield: "foo"))` Note that fields which are mapped to URL
1945
+ # query parameters must have a primitive type or a repeated primitive type or a
1946
+ # non-repeated message type. In the case of a repeated type, the parameter can
1947
+ # be repeated in the URL as `...?param=A&param=B`. In the case of a message type,
1948
+ # each field of the message is mapped to a separate parameter, such as `...?foo.
1949
+ # a=A&foo.b=B&foo.c=C`. For HTTP methods that allow a request body, the `body`
1950
+ # field specifies the mapping. Consider a REST update method on the message
1951
+ # resource collection: service Messaging ` rpc UpdateMessage(
1952
+ # UpdateMessageRequest) returns (Message) ` option (google.api.http) = ` patch: "
1953
+ # /v1/messages/`message_id`" body: "message" `; ` ` message UpdateMessageRequest
1954
+ # ` string message_id = 1; // mapped to the URL Message message = 2; // mapped
1955
+ # to the body ` The following HTTP JSON to RPC mapping is enabled, where the
1956
+ # representation of the JSON in the request body is determined by protos JSON
1957
+ # encoding: - HTTP: `PATCH /v1/messages/123456 ` "text": "Hi!" `` - gRPC: `
1958
+ # UpdateMessage(message_id: "123456" message ` text: "Hi!" `)` The special name `
1959
+ # *` can be used in the body mapping to define that every field not bound by the
1960
+ # path template should be mapped to the request body. This enables the following
1961
+ # alternative definition of the update method: service Messaging ` rpc
1962
+ # UpdateMessage(Message) returns (Message) ` option (google.api.http) = ` patch:
1963
+ # "/v1/messages/`message_id`" body: "*" `; ` ` message Message ` string
1964
+ # message_id = 1; string text = 2; ` The following HTTP JSON to RPC mapping is
1965
+ # enabled: - HTTP: `PATCH /v1/messages/123456 ` "text": "Hi!" `` - gRPC: `
1966
+ # UpdateMessage(message_id: "123456" text: "Hi!")` Note that when using `*` in
1967
+ # the body mapping, it is not possible to have HTTP parameters, as all fields
1968
+ # not bound by the path end in the body. This makes this option more rarely used
1969
+ # in practice when defining REST APIs. The common usage of `*` is in custom
1970
+ # methods which don't use the URL at all for transferring data. It is possible
1971
+ # to define multiple HTTP methods for one RPC by using the `additional_bindings`
1972
+ # option. Example: service Messaging ` rpc GetMessage(GetMessageRequest) returns
1973
+ # (Message) ` option (google.api.http) = ` get: "/v1/messages/`message_id`"
1974
+ # additional_bindings ` get: "/v1/users/`user_id`/messages/`message_id`" ` `; ` `
1975
+ # message GetMessageRequest ` string message_id = 1; string user_id = 2; ` This
1976
+ # enables the following two alternative HTTP JSON to RPC mappings: - HTTP: `GET /
1977
+ # v1/messages/123456` - gRPC: `GetMessage(message_id: "123456")` - HTTP: `GET /
1978
+ # v1/users/me/messages/123456` - gRPC: `GetMessage(user_id: "me" message_id: "
1979
+ # 123456")` Rules for HTTP mapping 1. Leaf request fields (recursive expansion
1980
+ # nested messages in the request message) are classified into three categories: -
1981
+ # Fields referred by the path template. They are passed via the URL path. -
1982
+ # Fields referred by the HttpRule.body. They are passed via the HTTP request
1983
+ # body. - All other fields are passed via the URL query parameters, and the
1984
+ # parameter name is the field path in the request message. A repeated field can
1985
+ # be represented as multiple query parameters under the same name. 2. If
1986
+ # HttpRule.body is "*", there is no URL query parameter, all fields are passed
1987
+ # via URL path and HTTP request body. 3. If HttpRule.body is omitted, there is
1988
+ # no HTTP request body, all fields are passed via URL path and URL query
1989
+ # parameters. Path template syntax Template = "/" Segments [ Verb ] ; Segments =
1990
+ # Segment ` "/" Segment ` ; Segment = "*" | "**" | LITERAL | Variable ; Variable
1991
+ # = "`" FieldPath [ "=" Segments ] "`" ; FieldPath = IDENT ` "." IDENT ` ; Verb =
1992
+ # ":" LITERAL ; The syntax `*` matches a single URL path segment. The syntax `**
1993
+ # ` matches zero or more URL path segments, which must be the last part of the
1994
+ # URL path except the `Verb`. The syntax `Variable` matches part of the URL path
1995
+ # as specified by its template. A variable template must not contain other
1997
1996
  # variables. If a variable matches a single path segment, its template may be
1998
1997
  # omitted, e.g. ``var`` is equivalent to ``var=*``. The syntax `LITERAL` matches
1999
1998
  # literal text in the URL path. If the `LITERAL` contains any reserved character,
@@ -2008,7 +2007,7 @@ module Google
2008
2007
  # except `[-_.~/0-9a-zA-Z]` are percent-encoded. The server side does the
2009
2008
  # reverse decoding, except "%2F" and "%2f" are left unchanged. Such variables
2010
2009
  # show up in the [Discovery Document](https://developers.google.com/discovery/v1/
2011
- # reference/apis) as ``+var``. ## Using gRPC API Service Configuration gRPC API
2010
+ # reference/apis) as ``+var``. Using gRPC API Service Configuration gRPC API
2012
2011
  # Service Configuration (service config) is a configuration language for
2013
2012
  # configuring a gRPC service to become a user-facing product. The service config
2014
2013
  # is simply the YAML representation of the `google.api.Service` proto message.
@@ -2018,11 +2017,11 @@ module Google
2018
2017
  # effect as the proto annotation. This can be particularly useful if you have a
2019
2018
  # proto that is reused in multiple services. Note that any transcoding specified
2020
2019
  # in the service config will override any matching transcoding configuration in
2021
- # the proto. Example: http: rules: # Selects a gRPC method and applies HttpRule
2022
- # to it. - selector: example.v1.Messaging.GetMessage get: /v1/messages/`
2023
- # message_id`/`sub.subfield` ## Special notes When gRPC Transcoding is used to
2024
- # map a gRPC to JSON REST endpoints, the proto to JSON conversion must follow
2025
- # the [proto3 specification](https://developers.google.com/protocol-buffers/docs/
2020
+ # the proto. Example below selects a gRPC method and applies HttpRule to it.
2021
+ # http: rules: - selector: example.v1.Messaging.GetMessage get: /v1/messages/`
2022
+ # message_id`/`sub.subfield` Special notes When gRPC Transcoding is used to map
2023
+ # a gRPC to JSON REST endpoints, the proto to JSON conversion must follow the [
2024
+ # proto3 specification](https://developers.google.com/protocol-buffers/docs/
2026
2025
  # proto3#json). While the single segment variable follows the semantics of [RFC
2027
2026
  # 6570](https://tools.ietf.org/html/rfc6570) Section 3.2.2 Simple String
2028
2027
  # Expansion, the multi segment variable **does not** follow RFC 6570 Section 3.2.
@@ -16,13 +16,13 @@ module Google
16
16
  module Apis
17
17
  module ServicemanagementV1
18
18
  # Version of the google-apis-servicemanagement_v1 gem
19
- GEM_VERSION = "0.55.0"
19
+ GEM_VERSION = "0.57.0"
20
20
 
21
21
  # Version of the code generator used to generate this client
22
- GENERATOR_VERSION = "0.14.0"
22
+ GENERATOR_VERSION = "0.15.0"
23
23
 
24
24
  # Revision of the discovery document this client was generated from
25
- REVISION = "20240426"
25
+ REVISION = "20240531"
26
26
  end
27
27
  end
28
28
  end
metadata CHANGED
@@ -1,14 +1,14 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: google-apis-servicemanagement_v1
3
3
  version: !ruby/object:Gem::Version
4
- version: 0.55.0
4
+ version: 0.57.0
5
5
  platform: ruby
6
6
  authors:
7
7
  - Google LLC
8
8
  autorequire:
9
9
  bindir: bin
10
10
  cert_chain: []
11
- date: 2024-05-05 00:00:00.000000000 Z
11
+ date: 2024-06-09 00:00:00.000000000 Z
12
12
  dependencies:
13
13
  - !ruby/object:Gem::Dependency
14
14
  name: google-apis-core
@@ -16,7 +16,7 @@ dependencies:
16
16
  requirements:
17
17
  - - ">="
18
18
  - !ruby/object:Gem::Version
19
- version: 0.14.0
19
+ version: 0.15.0
20
20
  - - "<"
21
21
  - !ruby/object:Gem::Version
22
22
  version: 2.a
@@ -26,7 +26,7 @@ dependencies:
26
26
  requirements:
27
27
  - - ">="
28
28
  - !ruby/object:Gem::Version
29
- version: 0.14.0
29
+ version: 0.15.0
30
30
  - - "<"
31
31
  - !ruby/object:Gem::Version
32
32
  version: 2.a
@@ -58,7 +58,7 @@ licenses:
58
58
  metadata:
59
59
  bug_tracker_uri: https://github.com/googleapis/google-api-ruby-client/issues
60
60
  changelog_uri: https://github.com/googleapis/google-api-ruby-client/tree/main/generated/google-apis-servicemanagement_v1/CHANGELOG.md
61
- documentation_uri: https://googleapis.dev/ruby/google-apis-servicemanagement_v1/v0.55.0
61
+ documentation_uri: https://googleapis.dev/ruby/google-apis-servicemanagement_v1/v0.57.0
62
62
  source_code_uri: https://github.com/googleapis/google-api-ruby-client/tree/main/generated/google-apis-servicemanagement_v1
63
63
  post_install_message:
64
64
  rdoc_options: []