google-apis-serviceusage_v1 0.53.0 → 0.54.0
Sign up to get free protection for your applications and to get access to all the features.
- checksums.yaml +4 -4
- data/CHANGELOG.md +4 -0
- data/lib/google/apis/serviceusage_v1/classes.rb +25 -23
- data/lib/google/apis/serviceusage_v1/gem_version.rb +2 -2
- metadata +3 -3
checksums.yaml
CHANGED
@@ -1,7 +1,7 @@
|
|
1
1
|
---
|
2
2
|
SHA256:
|
3
|
-
metadata.gz:
|
4
|
-
data.tar.gz:
|
3
|
+
metadata.gz: 35dfc01a3dab09288fbd7db9979fdf5ec0966e6eb0d1dba129cb5b987f53d11e
|
4
|
+
data.tar.gz: 674b030fd883eccee57f0b99e691b7a78aa5fc516ae9b4d482e0bf186fee4824
|
5
5
|
SHA512:
|
6
|
-
metadata.gz:
|
7
|
-
data.tar.gz:
|
6
|
+
metadata.gz: 9712b4b3dbbeaa9fc1fb0160bfa81962bbff7c7fdb0fb542ae450cf8f1a20fb474d768dc720328710167499ab3227b523e648e026fd4b6bd9c8b78a5e98f8dea
|
7
|
+
data.tar.gz: 71899103ef5e874327bfa14001720c7fbf4968d07eca832e0c4d8af3eb9754a555b733aae2252313448809693dd54955e56c2cadf647c2bca00ec3afe02607df
|
data/CHANGELOG.md
CHANGED
@@ -912,12 +912,14 @@ module Google
|
|
912
912
|
# @return [Array<String>]
|
913
913
|
attr_accessor :allowed_response_extensions
|
914
914
|
|
915
|
-
# A list of full type names of provided contexts.
|
915
|
+
# A list of full type names of provided contexts. It is used to support
|
916
|
+
# propagating HTTP headers and ETags from the response extension.
|
916
917
|
# Corresponds to the JSON property `provided`
|
917
918
|
# @return [Array<String>]
|
918
919
|
attr_accessor :provided
|
919
920
|
|
920
|
-
# A list of full type names of requested contexts
|
921
|
+
# A list of full type names of requested contexts, only the requested context
|
922
|
+
# will be made available to the backend.
|
921
923
|
# Corresponds to the JSON property `requested`
|
922
924
|
# @return [Array<String>]
|
923
925
|
attr_accessor :requested
|
@@ -2606,27 +2608,27 @@ module Google
|
|
2606
2608
|
# effect as the proto annotation. This can be particularly useful if you have a
|
2607
2609
|
# proto that is reused in multiple services. Note that any transcoding specified
|
2608
2610
|
# in the service config will override any matching transcoding configuration in
|
2609
|
-
# the proto.
|
2610
|
-
# http: rules: - selector: example.v1.Messaging.GetMessage get:
|
2611
|
-
# message_id`/`sub.subfield` Special notes When gRPC Transcoding
|
2612
|
-
# a gRPC to JSON REST endpoints, the proto to JSON conversion
|
2613
|
-
# proto3 specification](https://developers.google.com/protocol-
|
2614
|
-
# proto3#json). While the single segment variable follows the
|
2615
|
-
# 6570](https://tools.ietf.org/html/rfc6570) Section 3.2.2
|
2616
|
-
# Expansion, the multi segment variable **does not** follow RFC
|
2617
|
-
# 3 Reserved Expansion. The reason is that the Reserved
|
2618
|
-
# expand special characters like `?` and `#`, which would
|
2619
|
-
# As the result, gRPC Transcoding uses a custom encoding
|
2620
|
-
# variables. The path variables **must not** refer to any
|
2621
|
-
# field, because client libraries are not capable of handling
|
2622
|
-
# expansion. The path variables **must not** capture the leading "/
|
2623
|
-
# The reason is that the most common use case "`var`" does not
|
2624
|
-
# leading "/" character. For consistency, all path variables must
|
2625
|
-
# behavior. Repeated message fields must not be mapped to URL
|
2626
|
-
# because no client library can support such complicated
|
2627
|
-
# needs to use a JSON array for request or response body, it
|
2628
|
-
# or response body to a repeated field. However, some gRPC
|
2629
|
-
# implementations may not support this feature.
|
2611
|
+
# the proto. The following example selects a gRPC method and applies an `
|
2612
|
+
# HttpRule` to it: http: rules: - selector: example.v1.Messaging.GetMessage get:
|
2613
|
+
# /v1/messages/`message_id`/`sub.subfield` Special notes When gRPC Transcoding
|
2614
|
+
# is used to map a gRPC to JSON REST endpoints, the proto to JSON conversion
|
2615
|
+
# must follow the [proto3 specification](https://developers.google.com/protocol-
|
2616
|
+
# buffers/docs/proto3#json). While the single segment variable follows the
|
2617
|
+
# semantics of [RFC 6570](https://tools.ietf.org/html/rfc6570) Section 3.2.2
|
2618
|
+
# Simple String Expansion, the multi segment variable **does not** follow RFC
|
2619
|
+
# 6570 Section 3.2.3 Reserved Expansion. The reason is that the Reserved
|
2620
|
+
# Expansion does not expand special characters like `?` and `#`, which would
|
2621
|
+
# lead to invalid URLs. As the result, gRPC Transcoding uses a custom encoding
|
2622
|
+
# for multi segment variables. The path variables **must not** refer to any
|
2623
|
+
# repeated or mapped field, because client libraries are not capable of handling
|
2624
|
+
# such variable expansion. The path variables **must not** capture the leading "/
|
2625
|
+
# " character. The reason is that the most common use case "`var`" does not
|
2626
|
+
# capture the leading "/" character. For consistency, all path variables must
|
2627
|
+
# share the same behavior. Repeated message fields must not be mapped to URL
|
2628
|
+
# query parameters, because no client library can support such complicated
|
2629
|
+
# mapping. If an API needs to use a JSON array for request or response body, it
|
2630
|
+
# can map the request or response body to a repeated field. However, some gRPC
|
2631
|
+
# Transcoding implementations may not support this feature.
|
2630
2632
|
class HttpRule
|
2631
2633
|
include Google::Apis::Core::Hashable
|
2632
2634
|
|
@@ -16,13 +16,13 @@ module Google
|
|
16
16
|
module Apis
|
17
17
|
module ServiceusageV1
|
18
18
|
# Version of the google-apis-serviceusage_v1 gem
|
19
|
-
GEM_VERSION = "0.
|
19
|
+
GEM_VERSION = "0.54.0"
|
20
20
|
|
21
21
|
# Version of the code generator used to generate this client
|
22
22
|
GENERATOR_VERSION = "0.15.0"
|
23
23
|
|
24
24
|
# Revision of the discovery document this client was generated from
|
25
|
-
REVISION = "
|
25
|
+
REVISION = "20240712"
|
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-serviceusage_v1
|
3
3
|
version: !ruby/object:Gem::Version
|
4
|
-
version: 0.
|
4
|
+
version: 0.54.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-
|
11
|
+
date: 2024-07-25 00:00:00.000000000 Z
|
12
12
|
dependencies:
|
13
13
|
- !ruby/object:Gem::Dependency
|
14
14
|
name: google-apis-core
|
@@ -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-serviceusage_v1/CHANGELOG.md
|
61
|
-
documentation_uri: https://googleapis.dev/ruby/google-apis-serviceusage_v1/v0.
|
61
|
+
documentation_uri: https://googleapis.dev/ruby/google-apis-serviceusage_v1/v0.54.0
|
62
62
|
source_code_uri: https://github.com/googleapis/google-api-ruby-client/tree/main/generated/google-apis-serviceusage_v1
|
63
63
|
post_install_message:
|
64
64
|
rdoc_options: []
|