google-apis-serviceconsumermanagement_v1beta1 0.51.0 → 0.52.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: bcb2a3e5f2d0803b3cc97ba1b985e5f282e9a1a289d1c6a90348cc680f67b691
4
- data.tar.gz: bec82414991d90b05570be19cfa1907a3488ac3694d36e610817e3ac1f2cd788
3
+ metadata.gz: a7154ea70e7c2bd40583bdcfaba84286be726a0cfe92c6abfd49ed314c3a93dd
4
+ data.tar.gz: e859241036d23469c8b6b95fdad2466b0c2a8d1cfcd8c44c87a8f903b33011d3
5
5
  SHA512:
6
- metadata.gz: 6c322440ba0f7a38f54bb503f5f7f66c0fb250cfa413aed3260f8fc8a42a7c49c264aec98923cfa99619b482b57388db1b9190710e08a29e641e50fb138d7590
7
- data.tar.gz: 2bcfbbc532ee866a9332b788f8b4333b62675d70af66a10f2d248e90df0bafce43c84816cf6cdb95996e9f3ede6ef7fc8d6fa5b5d84c5d0fa753e3e245e2de0d
6
+ metadata.gz: 14ad7d3b031cfb4351149dc764219fb9661b4e92f590ecaee61ded0d3aaf324e96fd9d812cc902ff3a91bb013ecc3862d6ef3e6df2846aa089a23069ffe9cac3
7
+ data.tar.gz: 14ea4edbde1b7fffb08357563e827238a15dccc6444b5d9712f0b0afde47a95ed3b5b09dee5f9d0e640b38ac7bbc26894c2cf1e125150c09eac81e97b6ba532c
data/CHANGELOG.md CHANGED
@@ -1,5 +1,9 @@
1
1
  # Release history for google-apis-serviceconsumermanagement_v1beta1
2
2
 
3
+ ### v0.52.0 (2024-07-25)
4
+
5
+ * Regenerated from discovery document revision 20240712
6
+
3
7
  ### v0.51.0 (2024-06-16)
4
8
 
5
9
  * Regenerated from discovery document revision 20240609
@@ -635,12 +635,14 @@ module Google
635
635
  # @return [Array<String>]
636
636
  attr_accessor :allowed_response_extensions
637
637
 
638
- # A list of full type names of provided contexts.
638
+ # A list of full type names of provided contexts. It is used to support
639
+ # propagating HTTP headers and ETags from the response extension.
639
640
  # Corresponds to the JSON property `provided`
640
641
  # @return [Array<String>]
641
642
  attr_accessor :provided
642
643
 
643
- # A list of full type names of requested contexts.
644
+ # A list of full type names of requested contexts, only the requested context
645
+ # will be made available to the backend.
644
646
  # Corresponds to the JSON property `requested`
645
647
  # @return [Array<String>]
646
648
  attr_accessor :requested
@@ -1425,27 +1427,27 @@ module Google
1425
1427
  # effect as the proto annotation. This can be particularly useful if you have a
1426
1428
  # proto that is reused in multiple services. Note that any transcoding specified
1427
1429
  # in the service config will override any matching transcoding configuration in
1428
- # the proto. Example below selects a gRPC method and applies HttpRule to it.
1429
- # http: rules: - selector: example.v1.Messaging.GetMessage get: /v1/messages/`
1430
- # message_id`/`sub.subfield` Special notes When gRPC Transcoding is used to map
1431
- # a gRPC to JSON REST endpoints, the proto to JSON conversion must follow the [
1432
- # proto3 specification](https://developers.google.com/protocol-buffers/docs/
1433
- # proto3#json). While the single segment variable follows the semantics of [RFC
1434
- # 6570](https://tools.ietf.org/html/rfc6570) Section 3.2.2 Simple String
1435
- # Expansion, the multi segment variable **does not** follow RFC 6570 Section 3.2.
1436
- # 3 Reserved Expansion. The reason is that the Reserved Expansion does not
1437
- # expand special characters like `?` and `#`, which would lead to invalid URLs.
1438
- # As the result, gRPC Transcoding uses a custom encoding for multi segment
1439
- # variables. The path variables **must not** refer to any repeated or mapped
1440
- # field, because client libraries are not capable of handling such variable
1441
- # expansion. The path variables **must not** capture the leading "/" character.
1442
- # The reason is that the most common use case "`var`" does not capture the
1443
- # leading "/" character. For consistency, all path variables must share the same
1444
- # behavior. Repeated message fields must not be mapped to URL query parameters,
1445
- # because no client library can support such complicated mapping. If an API
1446
- # needs to use a JSON array for request or response body, it can map the request
1447
- # or response body to a repeated field. However, some gRPC Transcoding
1448
- # implementations may not support this feature.
1430
+ # the proto. The following example selects a gRPC method and applies an `
1431
+ # HttpRule` to it: http: rules: - selector: example.v1.Messaging.GetMessage get:
1432
+ # /v1/messages/`message_id`/`sub.subfield` Special notes When gRPC Transcoding
1433
+ # is used to map a gRPC to JSON REST endpoints, the proto to JSON conversion
1434
+ # must follow the [proto3 specification](https://developers.google.com/protocol-
1435
+ # buffers/docs/proto3#json). While the single segment variable follows the
1436
+ # semantics of [RFC 6570](https://tools.ietf.org/html/rfc6570) Section 3.2.2
1437
+ # Simple String Expansion, the multi segment variable **does not** follow RFC
1438
+ # 6570 Section 3.2.3 Reserved Expansion. The reason is that the Reserved
1439
+ # Expansion does not expand special characters like `?` and `#`, which would
1440
+ # lead to invalid URLs. As the result, gRPC Transcoding uses a custom encoding
1441
+ # for multi segment variables. The path variables **must not** refer to any
1442
+ # repeated or mapped field, because client libraries are not capable of handling
1443
+ # such variable expansion. The path variables **must not** capture the leading "/
1444
+ # " character. The reason is that the most common use case "`var`" does not
1445
+ # capture the leading "/" character. For consistency, all path variables must
1446
+ # share the same behavior. Repeated message fields must not be mapped to URL
1447
+ # query parameters, because no client library can support such complicated
1448
+ # mapping. If an API needs to use a JSON array for request or response body, it
1449
+ # can map the request or response body to a repeated field. However, some gRPC
1450
+ # Transcoding implementations may not support this feature.
1449
1451
  class HttpRule
1450
1452
  include Google::Apis::Core::Hashable
1451
1453
 
@@ -16,13 +16,13 @@ module Google
16
16
  module Apis
17
17
  module ServiceconsumermanagementV1beta1
18
18
  # Version of the google-apis-serviceconsumermanagement_v1beta1 gem
19
- GEM_VERSION = "0.51.0"
19
+ GEM_VERSION = "0.52.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 = "20240609"
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-serviceconsumermanagement_v1beta1
3
3
  version: !ruby/object:Gem::Version
4
- version: 0.51.0
4
+ version: 0.52.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-06-16 00:00:00.000000000 Z
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-serviceconsumermanagement_v1beta1/CHANGELOG.md
61
- documentation_uri: https://googleapis.dev/ruby/google-apis-serviceconsumermanagement_v1beta1/v0.51.0
61
+ documentation_uri: https://googleapis.dev/ruby/google-apis-serviceconsumermanagement_v1beta1/v0.52.0
62
62
  source_code_uri: https://github.com/googleapis/google-api-ruby-client/tree/main/generated/google-apis-serviceconsumermanagement_v1beta1
63
63
  post_install_message:
64
64
  rdoc_options: []