google-apis-serviceusage_v1 0.52.0 → 0.53.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 +70 -71
- 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: 5a7064b8d6fc9a010e6b2528207e0c71669c1072600e8de72ae06fc0083d450c
|
4
|
+
data.tar.gz: 28ac8621a506a018b0cfdc122abcf436791e3cb8d1b648c445c79b5318265e9c
|
5
5
|
SHA512:
|
6
|
-
metadata.gz:
|
7
|
-
data.tar.gz:
|
6
|
+
metadata.gz: d1e54871562faf2a297c03089631569761ae93b655a29e41e28d8987e6223584ef9e5b1e4e47b630ee285330ba6f51f974bf075f8dca1786879f41638108e3f6
|
7
|
+
data.tar.gz: fa094c708428622cbc0193110a17e5164297ae40ad31f17cf44dde5c78de0dc75aab8bcc7710570c1042cb66a2e668510709d2d3868c171b8d71ec701a0a1242
|
data/CHANGELOG.md
CHANGED
@@ -2499,7 +2499,7 @@ module Google
|
|
2499
2499
|
end
|
2500
2500
|
end
|
2501
2501
|
|
2502
|
-
#
|
2502
|
+
# gRPC Transcoding gRPC Transcoding is a feature for mapping between a gRPC
|
2503
2503
|
# method and one or more HTTP REST endpoints. It allows developers to build a
|
2504
2504
|
# single API service that supports both gRPC APIs and REST APIs. Many systems,
|
2505
2505
|
# including [Google APIs](https://github.com/googleapis/googleapis), [Cloud
|
@@ -2519,70 +2519,69 @@ module Google
|
|
2519
2519
|
# Message) ` option (google.api.http) = ` get: "/v1/`name=messages/*`" `; ` `
|
2520
2520
|
# message GetMessageRequest ` string name = 1; // Mapped to URL path. ` message
|
2521
2521
|
# Message ` string text = 1; // The resource content. ` This enables an HTTP
|
2522
|
-
# REST to gRPC mapping as below: HTTP
|
2523
|
-
#
|
2524
|
-
#
|
2525
|
-
#
|
2526
|
-
#
|
2527
|
-
#
|
2528
|
-
#
|
2529
|
-
#
|
2530
|
-
#
|
2531
|
-
#
|
2532
|
-
#
|
2533
|
-
#
|
2534
|
-
#
|
2535
|
-
#
|
2536
|
-
#
|
2537
|
-
#
|
2538
|
-
#
|
2539
|
-
#
|
2540
|
-
#
|
2541
|
-
#
|
2542
|
-
#
|
2543
|
-
#
|
2544
|
-
#
|
2545
|
-
#
|
2546
|
-
#
|
2547
|
-
#
|
2548
|
-
#
|
2549
|
-
#
|
2550
|
-
#
|
2551
|
-
#
|
2552
|
-
#
|
2553
|
-
#
|
2554
|
-
#
|
2555
|
-
#
|
2556
|
-
#
|
2557
|
-
#
|
2558
|
-
#
|
2559
|
-
#
|
2560
|
-
#
|
2561
|
-
#
|
2562
|
-
#
|
2563
|
-
#
|
2564
|
-
#
|
2565
|
-
#
|
2566
|
-
#
|
2567
|
-
# messages/123456`
|
2568
|
-
#
|
2569
|
-
#
|
2570
|
-
#
|
2571
|
-
# referred by the
|
2572
|
-
#
|
2573
|
-
#
|
2574
|
-
#
|
2575
|
-
#
|
2576
|
-
#
|
2577
|
-
#
|
2578
|
-
#
|
2579
|
-
#
|
2580
|
-
# "
|
2581
|
-
#
|
2582
|
-
#
|
2583
|
-
#
|
2584
|
-
#
|
2585
|
-
# specified by its template. A variable template must not contain other
|
2522
|
+
# REST to gRPC mapping as below: - HTTP: `GET /v1/messages/123456` - gRPC: `
|
2523
|
+
# GetMessage(name: "messages/123456")` Any fields in the request message which
|
2524
|
+
# are not bound by the path template automatically become HTTP query parameters
|
2525
|
+
# if there is no HTTP request body. For example: service Messaging ` rpc
|
2526
|
+
# GetMessage(GetMessageRequest) returns (Message) ` option (google.api.http) = `
|
2527
|
+
# get:"/v1/messages/`message_id`" `; ` ` message GetMessageRequest ` message
|
2528
|
+
# SubMessage ` string subfield = 1; ` string message_id = 1; // Mapped to URL
|
2529
|
+
# path. int64 revision = 2; // Mapped to URL query parameter `revision`.
|
2530
|
+
# SubMessage sub = 3; // Mapped to URL query parameter `sub.subfield`. ` This
|
2531
|
+
# enables a HTTP JSON to RPC mapping as below: - HTTP: `GET /v1/messages/123456?
|
2532
|
+
# revision=2&sub.subfield=foo` - gRPC: `GetMessage(message_id: "123456" revision:
|
2533
|
+
# 2 sub: SubMessage(subfield: "foo"))` Note that fields which are mapped to URL
|
2534
|
+
# query parameters must have a primitive type or a repeated primitive type or a
|
2535
|
+
# non-repeated message type. In the case of a repeated type, the parameter can
|
2536
|
+
# be repeated in the URL as `...?param=A¶m=B`. In the case of a message type,
|
2537
|
+
# each field of the message is mapped to a separate parameter, such as `...?foo.
|
2538
|
+
# a=A&foo.b=B&foo.c=C`. For HTTP methods that allow a request body, the `body`
|
2539
|
+
# field specifies the mapping. Consider a REST update method on the message
|
2540
|
+
# resource collection: service Messaging ` rpc UpdateMessage(
|
2541
|
+
# UpdateMessageRequest) returns (Message) ` option (google.api.http) = ` patch: "
|
2542
|
+
# /v1/messages/`message_id`" body: "message" `; ` ` message UpdateMessageRequest
|
2543
|
+
# ` string message_id = 1; // mapped to the URL Message message = 2; // mapped
|
2544
|
+
# to the body ` The following HTTP JSON to RPC mapping is enabled, where the
|
2545
|
+
# representation of the JSON in the request body is determined by protos JSON
|
2546
|
+
# encoding: - HTTP: `PATCH /v1/messages/123456 ` "text": "Hi!" `` - gRPC: `
|
2547
|
+
# UpdateMessage(message_id: "123456" message ` text: "Hi!" `)` The special name `
|
2548
|
+
# *` can be used in the body mapping to define that every field not bound by the
|
2549
|
+
# path template should be mapped to the request body. This enables the following
|
2550
|
+
# alternative definition of the update method: service Messaging ` rpc
|
2551
|
+
# UpdateMessage(Message) returns (Message) ` option (google.api.http) = ` patch:
|
2552
|
+
# "/v1/messages/`message_id`" body: "*" `; ` ` message Message ` string
|
2553
|
+
# message_id = 1; string text = 2; ` The following HTTP JSON to RPC mapping is
|
2554
|
+
# enabled: - HTTP: `PATCH /v1/messages/123456 ` "text": "Hi!" `` - gRPC: `
|
2555
|
+
# UpdateMessage(message_id: "123456" text: "Hi!")` Note that when using `*` in
|
2556
|
+
# the body mapping, it is not possible to have HTTP parameters, as all fields
|
2557
|
+
# not bound by the path end in the body. This makes this option more rarely used
|
2558
|
+
# in practice when defining REST APIs. The common usage of `*` is in custom
|
2559
|
+
# methods which don't use the URL at all for transferring data. It is possible
|
2560
|
+
# to define multiple HTTP methods for one RPC by using the `additional_bindings`
|
2561
|
+
# option. Example: service Messaging ` rpc GetMessage(GetMessageRequest) returns
|
2562
|
+
# (Message) ` option (google.api.http) = ` get: "/v1/messages/`message_id`"
|
2563
|
+
# additional_bindings ` get: "/v1/users/`user_id`/messages/`message_id`" ` `; ` `
|
2564
|
+
# message GetMessageRequest ` string message_id = 1; string user_id = 2; ` This
|
2565
|
+
# enables the following two alternative HTTP JSON to RPC mappings: - HTTP: `GET /
|
2566
|
+
# v1/messages/123456` - gRPC: `GetMessage(message_id: "123456")` - HTTP: `GET /
|
2567
|
+
# v1/users/me/messages/123456` - gRPC: `GetMessage(user_id: "me" message_id: "
|
2568
|
+
# 123456")` Rules for HTTP mapping 1. Leaf request fields (recursive expansion
|
2569
|
+
# nested messages in the request message) are classified into three categories: -
|
2570
|
+
# Fields referred by the path template. They are passed via the URL path. -
|
2571
|
+
# Fields referred by the HttpRule.body. They are passed via the HTTP request
|
2572
|
+
# body. - All other fields are passed via the URL query parameters, and the
|
2573
|
+
# parameter name is the field path in the request message. A repeated field can
|
2574
|
+
# be represented as multiple query parameters under the same name. 2. If
|
2575
|
+
# HttpRule.body is "*", there is no URL query parameter, all fields are passed
|
2576
|
+
# via URL path and HTTP request body. 3. If HttpRule.body is omitted, there is
|
2577
|
+
# no HTTP request body, all fields are passed via URL path and URL query
|
2578
|
+
# parameters. Path template syntax Template = "/" Segments [ Verb ] ; Segments =
|
2579
|
+
# Segment ` "/" Segment ` ; Segment = "*" | "**" | LITERAL | Variable ; Variable
|
2580
|
+
# = "`" FieldPath [ "=" Segments ] "`" ; FieldPath = IDENT ` "." IDENT ` ; Verb =
|
2581
|
+
# ":" LITERAL ; The syntax `*` matches a single URL path segment. The syntax `**
|
2582
|
+
# ` matches zero or more URL path segments, which must be the last part of the
|
2583
|
+
# URL path except the `Verb`. The syntax `Variable` matches part of the URL path
|
2584
|
+
# as specified by its template. A variable template must not contain other
|
2586
2585
|
# variables. If a variable matches a single path segment, its template may be
|
2587
2586
|
# omitted, e.g. ``var`` is equivalent to ``var=*``. The syntax `LITERAL` matches
|
2588
2587
|
# literal text in the URL path. If the `LITERAL` contains any reserved character,
|
@@ -2597,7 +2596,7 @@ module Google
|
|
2597
2596
|
# except `[-_.~/0-9a-zA-Z]` are percent-encoded. The server side does the
|
2598
2597
|
# reverse decoding, except "%2F" and "%2f" are left unchanged. Such variables
|
2599
2598
|
# show up in the [Discovery Document](https://developers.google.com/discovery/v1/
|
2600
|
-
# reference/apis) as ``+var``.
|
2599
|
+
# reference/apis) as ``+var``. Using gRPC API Service Configuration gRPC API
|
2601
2600
|
# Service Configuration (service config) is a configuration language for
|
2602
2601
|
# configuring a gRPC service to become a user-facing product. The service config
|
2603
2602
|
# is simply the YAML representation of the `google.api.Service` proto message.
|
@@ -2607,11 +2606,11 @@ module Google
|
|
2607
2606
|
# effect as the proto annotation. This can be particularly useful if you have a
|
2608
2607
|
# proto that is reused in multiple services. Note that any transcoding specified
|
2609
2608
|
# in the service config will override any matching transcoding configuration in
|
2610
|
-
# the proto. Example
|
2611
|
-
#
|
2612
|
-
# message_id`/`sub.subfield`
|
2613
|
-
#
|
2614
|
-
#
|
2609
|
+
# the proto. Example below selects a gRPC method and applies HttpRule to it.
|
2610
|
+
# http: rules: - selector: example.v1.Messaging.GetMessage get: /v1/messages/`
|
2611
|
+
# message_id`/`sub.subfield` Special notes When gRPC Transcoding is used to map
|
2612
|
+
# a gRPC to JSON REST endpoints, the proto to JSON conversion must follow the [
|
2613
|
+
# proto3 specification](https://developers.google.com/protocol-buffers/docs/
|
2615
2614
|
# proto3#json). While the single segment variable follows the semantics of [RFC
|
2616
2615
|
# 6570](https://tools.ietf.org/html/rfc6570) Section 3.2.2 Simple String
|
2617
2616
|
# 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 ServiceusageV1
|
18
18
|
# Version of the google-apis-serviceusage_v1 gem
|
19
|
-
GEM_VERSION = "0.
|
19
|
+
GEM_VERSION = "0.53.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 = "20240602"
|
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.53.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-06-09 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.53.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: []
|