google-cloud-optimization-v1 0.1.0
Sign up to get free protection for your applications and to get access to all the features.
- checksums.yaml +7 -0
- data/.yardopts +12 -0
- data/AUTHENTICATION.md +149 -0
- data/LICENSE.md +201 -0
- data/README.md +135 -0
- data/lib/google/cloud/optimization/v1/async_model_pb.rb +63 -0
- data/lib/google/cloud/optimization/v1/fleet_routing/client.rb +719 -0
- data/lib/google/cloud/optimization/v1/fleet_routing/credentials.rb +47 -0
- data/lib/google/cloud/optimization/v1/fleet_routing/operations.rb +767 -0
- data/lib/google/cloud/optimization/v1/fleet_routing.rb +65 -0
- data/lib/google/cloud/optimization/v1/fleet_routing_pb.rb +483 -0
- data/lib/google/cloud/optimization/v1/fleet_routing_services_pb.rb +85 -0
- data/lib/google/cloud/optimization/v1/version.rb +28 -0
- data/lib/google/cloud/optimization/v1.rb +40 -0
- data/lib/google-cloud-optimization-v1.rb +21 -0
- data/proto_docs/README.md +4 -0
- data/proto_docs/google/api/field_behavior.rb +71 -0
- data/proto_docs/google/api/resource.rb +222 -0
- data/proto_docs/google/cloud/optimization/v1/async_model.rb +118 -0
- data/proto_docs/google/cloud/optimization/v1/fleet_routing.rb +2755 -0
- data/proto_docs/google/longrunning/operations.rb +164 -0
- data/proto_docs/google/protobuf/any.rb +141 -0
- data/proto_docs/google/protobuf/duration.rb +98 -0
- data/proto_docs/google/protobuf/empty.rb +36 -0
- data/proto_docs/google/protobuf/timestamp.rb +129 -0
- data/proto_docs/google/rpc/status.rb +46 -0
- data/proto_docs/google/type/latlng.rb +38 -0
- metadata +217 -0
checksums.yaml
ADDED
@@ -0,0 +1,7 @@
|
|
1
|
+
---
|
2
|
+
SHA256:
|
3
|
+
metadata.gz: e080ce2748169d4c7edaa3dca7b3a822a05114303896d640ec31bcbbe8684500
|
4
|
+
data.tar.gz: 3fc95ad2d4b45731021d6ef44e4f15a3cf48d4b438e1083a74c075deb5706a2d
|
5
|
+
SHA512:
|
6
|
+
metadata.gz: dd6b29c497ff59ffc251ecf36026c7d4215a0afadf1178cab22b4a44ed7b22c7a23d199cee5751c816994d8cd4609960d48f42d6c868cdd7e22289fa7a569a73
|
7
|
+
data.tar.gz: 4477875d014d49314cdaae860db6efd25d5f8da74bec3b75ebb73fd58b7b6249163f5948d6d7d064cc28d6705843a4f5dc716e3d1c5563ef063f102e231a2443
|
data/.yardopts
ADDED
data/AUTHENTICATION.md
ADDED
@@ -0,0 +1,149 @@
|
|
1
|
+
# Authentication
|
2
|
+
|
3
|
+
In general, the google-cloud-optimization-v1 library uses
|
4
|
+
[Service Account](https://cloud.google.com/iam/docs/creating-managing-service-accounts)
|
5
|
+
credentials to connect to Google Cloud services. When running within
|
6
|
+
[Google Cloud Platform environments](#google-cloud-platform-environments) the
|
7
|
+
credentials will be discovered automatically. When running on other
|
8
|
+
environments, the Service Account credentials can be specified by providing the
|
9
|
+
path to the
|
10
|
+
[JSON keyfile](https://cloud.google.com/iam/docs/managing-service-account-keys)
|
11
|
+
for the account (or the JSON itself) in
|
12
|
+
[environment variables](#environment-variables). Additionally, Cloud SDK
|
13
|
+
credentials can also be discovered automatically, but this is only recommended
|
14
|
+
during development.
|
15
|
+
|
16
|
+
## Quickstart
|
17
|
+
|
18
|
+
1. [Create a service account and credentials](#creating-a-service-account).
|
19
|
+
2. Set the [environment variable](#environment-variables).
|
20
|
+
|
21
|
+
```sh
|
22
|
+
export GOOGLE_CLOUD_CREDENTIALS=path/to/keyfile.json
|
23
|
+
```
|
24
|
+
|
25
|
+
3. Initialize the client.
|
26
|
+
|
27
|
+
```ruby
|
28
|
+
require "google/cloud/optimization/v1"
|
29
|
+
|
30
|
+
client = ::Google::Cloud::Optimization::V1::FleetRouting::Client.new
|
31
|
+
```
|
32
|
+
|
33
|
+
## Credential Lookup
|
34
|
+
|
35
|
+
The google-cloud-optimization-v1 library aims to make authentication
|
36
|
+
as simple as possible, and provides several mechanisms to configure your system
|
37
|
+
without requiring **Service Account Credentials** directly in code.
|
38
|
+
|
39
|
+
**Credentials** are discovered in the following order:
|
40
|
+
|
41
|
+
1. Specify credentials in method arguments
|
42
|
+
2. Specify credentials in configuration
|
43
|
+
3. Discover credentials path in environment variables
|
44
|
+
4. Discover credentials JSON in environment variables
|
45
|
+
5. Discover credentials file in the Cloud SDK's path
|
46
|
+
6. Discover GCP credentials
|
47
|
+
|
48
|
+
### Google Cloud Platform environments
|
49
|
+
|
50
|
+
When running on Google Cloud Platform (GCP), including Google Compute Engine
|
51
|
+
(GCE), Google Kubernetes Engine (GKE), Google App Engine (GAE), Google Cloud
|
52
|
+
Functions (GCF) and Cloud Run, **Credentials** are discovered automatically.
|
53
|
+
Code should be written as if already authenticated.
|
54
|
+
|
55
|
+
### Environment Variables
|
56
|
+
|
57
|
+
The **Credentials JSON** can be placed in environment variables instead of
|
58
|
+
declaring them directly in code. Each service has its own environment variable,
|
59
|
+
allowing for different service accounts to be used for different services. (See
|
60
|
+
the READMEs for the individual service gems for details.) The path to the
|
61
|
+
**Credentials JSON** file can be stored in the environment variable, or the
|
62
|
+
**Credentials JSON** itself can be stored for environments such as Docker
|
63
|
+
containers where writing files is difficult or not encouraged.
|
64
|
+
|
65
|
+
The environment variables that google-cloud-optimization-v1
|
66
|
+
checks for credentials are configured on the service Credentials class (such as
|
67
|
+
{::Google::Cloud::Optimization::V1::FleetRouting::Credentials}):
|
68
|
+
|
69
|
+
* `GOOGLE_CLOUD_CREDENTIALS` - Path to JSON file, or JSON contents
|
70
|
+
* `GOOGLE_CLOUD_KEYFILE` - Path to JSON file, or JSON contents
|
71
|
+
* `GOOGLE_APPLICATION_CREDENTIALS` - Path to JSON file
|
72
|
+
|
73
|
+
```ruby
|
74
|
+
require "google/cloud/optimization/v1"
|
75
|
+
|
76
|
+
ENV["GOOGLE_CLOUD_CREDENTIALS"] = "path/to/keyfile.json"
|
77
|
+
|
78
|
+
client = ::Google::Cloud::Optimization::V1::FleetRouting::Client.new
|
79
|
+
```
|
80
|
+
|
81
|
+
### Configuration
|
82
|
+
|
83
|
+
The path to the **Credentials JSON** file can be configured instead of storing
|
84
|
+
it in an environment variable. Either on an individual client initialization:
|
85
|
+
|
86
|
+
```ruby
|
87
|
+
require "google/cloud/optimization/v1"
|
88
|
+
|
89
|
+
client = ::Google::Cloud::Optimization::V1::FleetRouting::Client.new do |config|
|
90
|
+
config.credentials = "path/to/keyfile.json"
|
91
|
+
end
|
92
|
+
```
|
93
|
+
|
94
|
+
Or globally for all clients:
|
95
|
+
|
96
|
+
```ruby
|
97
|
+
require "google/cloud/optimization/v1"
|
98
|
+
|
99
|
+
::Google::Cloud::Optimization::V1::FleetRouting::Client.configure do |config|
|
100
|
+
config.credentials = "path/to/keyfile.json"
|
101
|
+
end
|
102
|
+
|
103
|
+
client = ::Google::Cloud::Optimization::V1::FleetRouting::Client.new
|
104
|
+
```
|
105
|
+
|
106
|
+
### Cloud SDK
|
107
|
+
|
108
|
+
This option allows for an easy way to authenticate during development. If
|
109
|
+
credentials are not provided in code or in environment variables, then Cloud SDK
|
110
|
+
credentials are discovered.
|
111
|
+
|
112
|
+
To configure your system for this, simply:
|
113
|
+
|
114
|
+
1. [Download and install the Cloud SDK](https://cloud.google.com/sdk)
|
115
|
+
2. Authenticate using OAuth 2.0 `$ gcloud auth login`
|
116
|
+
3. Write code as if already authenticated.
|
117
|
+
|
118
|
+
**NOTE:** This is _not_ recommended for running in production. The Cloud SDK
|
119
|
+
*should* only be used during development.
|
120
|
+
|
121
|
+
## Creating a Service Account
|
122
|
+
|
123
|
+
Google Cloud requires **Service Account Credentials** to
|
124
|
+
connect to the APIs. You will use the **JSON key file** to
|
125
|
+
connect to most services with google-cloud-optimization-v1.
|
126
|
+
|
127
|
+
If you are not running this client within
|
128
|
+
[Google Cloud Platform environments](#google-cloud-platform-environments), you
|
129
|
+
need a Google Developers service account.
|
130
|
+
|
131
|
+
1. Visit the [Google Cloud Console](https://console.cloud.google.com/project).
|
132
|
+
2. Create a new project or click on an existing project.
|
133
|
+
3. Activate the menu in the upper left and select **APIs & Services**. From
|
134
|
+
here, you will enable the APIs that your application requires.
|
135
|
+
|
136
|
+
*Note: You may need to enable billing in order to use these services.*
|
137
|
+
|
138
|
+
4. Select **Credentials** from the side navigation.
|
139
|
+
|
140
|
+
Find the "Create credentials" drop down near the top of the page, and select
|
141
|
+
"Service account" to be guided through downloading a new JSON key file.
|
142
|
+
|
143
|
+
If you want to re-use an existing service account, you can easily generate a
|
144
|
+
new key file. Just select the account you wish to re-use, click the pencil
|
145
|
+
tool on the right side to edit the service account, select the **Keys** tab,
|
146
|
+
and then select **Add Key**.
|
147
|
+
|
148
|
+
The key file you download will be used by this library to authenticate API
|
149
|
+
requests and should be stored in a secure location.
|
data/LICENSE.md
ADDED
@@ -0,0 +1,201 @@
|
|
1
|
+
Apache License
|
2
|
+
Version 2.0, January 2004
|
3
|
+
http://www.apache.org/licenses/
|
4
|
+
|
5
|
+
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
|
6
|
+
|
7
|
+
1. Definitions.
|
8
|
+
|
9
|
+
"License" shall mean the terms and conditions for use, reproduction,
|
10
|
+
and distribution as defined by Sections 1 through 9 of this document.
|
11
|
+
|
12
|
+
"Licensor" shall mean the copyright owner or entity authorized by
|
13
|
+
the copyright owner that is granting the License.
|
14
|
+
|
15
|
+
"Legal Entity" shall mean the union of the acting entity and all
|
16
|
+
other entities that control, are controlled by, or are under common
|
17
|
+
control with that entity. For the purposes of this definition,
|
18
|
+
"control" means (i) the power, direct or indirect, to cause the
|
19
|
+
direction or management of such entity, whether by contract or
|
20
|
+
otherwise, or (ii) ownership of fifty percent (50%) or more of the
|
21
|
+
outstanding shares, or (iii) beneficial ownership of such entity.
|
22
|
+
|
23
|
+
"You" (or "Your") shall mean an individual or Legal Entity
|
24
|
+
exercising permissions granted by this License.
|
25
|
+
|
26
|
+
"Source" form shall mean the preferred form for making modifications,
|
27
|
+
including but not limited to software source code, documentation
|
28
|
+
source, and configuration files.
|
29
|
+
|
30
|
+
"Object" form shall mean any form resulting from mechanical
|
31
|
+
transformation or translation of a Source form, including but
|
32
|
+
not limited to compiled object code, generated documentation,
|
33
|
+
and conversions to other media types.
|
34
|
+
|
35
|
+
"Work" shall mean the work of authorship, whether in Source or
|
36
|
+
Object form, made available under the License, as indicated by a
|
37
|
+
copyright notice that is included in or attached to the work
|
38
|
+
(an example is provided in the Appendix below).
|
39
|
+
|
40
|
+
"Derivative Works" shall mean any work, whether in Source or Object
|
41
|
+
form, that is based on (or derived from) the Work and for which the
|
42
|
+
editorial revisions, annotations, elaborations, or other modifications
|
43
|
+
represent, as a whole, an original work of authorship. For the purposes
|
44
|
+
of this License, Derivative Works shall not include works that remain
|
45
|
+
separable from, or merely link (or bind by name) to the interfaces of,
|
46
|
+
the Work and Derivative Works thereof.
|
47
|
+
|
48
|
+
"Contribution" shall mean any work of authorship, including
|
49
|
+
the original version of the Work and any modifications or additions
|
50
|
+
to that Work or Derivative Works thereof, that is intentionally
|
51
|
+
submitted to Licensor for inclusion in the Work by the copyright owner
|
52
|
+
or by an individual or Legal Entity authorized to submit on behalf of
|
53
|
+
the copyright owner. For the purposes of this definition, "submitted"
|
54
|
+
means any form of electronic, verbal, or written communication sent
|
55
|
+
to the Licensor or its representatives, including but not limited to
|
56
|
+
communication on electronic mailing lists, source code control systems,
|
57
|
+
and issue tracking systems that are managed by, or on behalf of, the
|
58
|
+
Licensor for the purpose of discussing and improving the Work, but
|
59
|
+
excluding communication that is conspicuously marked or otherwise
|
60
|
+
designated in writing by the copyright owner as "Not a Contribution."
|
61
|
+
|
62
|
+
"Contributor" shall mean Licensor and any individual or Legal Entity
|
63
|
+
on behalf of whom a Contribution has been received by Licensor and
|
64
|
+
subsequently incorporated within the Work.
|
65
|
+
|
66
|
+
2. Grant of Copyright License. Subject to the terms and conditions of
|
67
|
+
this License, each Contributor hereby grants to You a perpetual,
|
68
|
+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
69
|
+
copyright license to reproduce, prepare Derivative Works of,
|
70
|
+
publicly display, publicly perform, sublicense, and distribute the
|
71
|
+
Work and such Derivative Works in Source or Object form.
|
72
|
+
|
73
|
+
3. Grant of Patent License. Subject to the terms and conditions of
|
74
|
+
this License, each Contributor hereby grants to You a perpetual,
|
75
|
+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
76
|
+
(except as stated in this section) patent license to make, have made,
|
77
|
+
use, offer to sell, sell, import, and otherwise transfer the Work,
|
78
|
+
where such license applies only to those patent claims licensable
|
79
|
+
by such Contributor that are necessarily infringed by their
|
80
|
+
Contribution(s) alone or by combination of their Contribution(s)
|
81
|
+
with the Work to which such Contribution(s) was submitted. If You
|
82
|
+
institute patent litigation against any entity (including a
|
83
|
+
cross-claim or counterclaim in a lawsuit) alleging that the Work
|
84
|
+
or a Contribution incorporated within the Work constitutes direct
|
85
|
+
or contributory patent infringement, then any patent licenses
|
86
|
+
granted to You under this License for that Work shall terminate
|
87
|
+
as of the date such litigation is filed.
|
88
|
+
|
89
|
+
4. Redistribution. You may reproduce and distribute copies of the
|
90
|
+
Work or Derivative Works thereof in any medium, with or without
|
91
|
+
modifications, and in Source or Object form, provided that You
|
92
|
+
meet the following conditions:
|
93
|
+
|
94
|
+
(a) You must give any other recipients of the Work or
|
95
|
+
Derivative Works a copy of this License; and
|
96
|
+
|
97
|
+
(b) You must cause any modified files to carry prominent notices
|
98
|
+
stating that You changed the files; and
|
99
|
+
|
100
|
+
(c) You must retain, in the Source form of any Derivative Works
|
101
|
+
that You distribute, all copyright, patent, trademark, and
|
102
|
+
attribution notices from the Source form of the Work,
|
103
|
+
excluding those notices that do not pertain to any part of
|
104
|
+
the Derivative Works; and
|
105
|
+
|
106
|
+
(d) If the Work includes a "NOTICE" text file as part of its
|
107
|
+
distribution, then any Derivative Works that You distribute must
|
108
|
+
include a readable copy of the attribution notices contained
|
109
|
+
within such NOTICE file, excluding those notices that do not
|
110
|
+
pertain to any part of the Derivative Works, in at least one
|
111
|
+
of the following places: within a NOTICE text file distributed
|
112
|
+
as part of the Derivative Works; within the Source form or
|
113
|
+
documentation, if provided along with the Derivative Works; or,
|
114
|
+
within a display generated by the Derivative Works, if and
|
115
|
+
wherever such third-party notices normally appear. The contents
|
116
|
+
of the NOTICE file are for informational purposes only and
|
117
|
+
do not modify the License. You may add Your own attribution
|
118
|
+
notices within Derivative Works that You distribute, alongside
|
119
|
+
or as an addendum to the NOTICE text from the Work, provided
|
120
|
+
that such additional attribution notices cannot be construed
|
121
|
+
as modifying the License.
|
122
|
+
|
123
|
+
You may add Your own copyright statement to Your modifications and
|
124
|
+
may provide additional or different license terms and conditions
|
125
|
+
for use, reproduction, or distribution of Your modifications, or
|
126
|
+
for any such Derivative Works as a whole, provided Your use,
|
127
|
+
reproduction, and distribution of the Work otherwise complies with
|
128
|
+
the conditions stated in this License.
|
129
|
+
|
130
|
+
5. Submission of Contributions. Unless You explicitly state otherwise,
|
131
|
+
any Contribution intentionally submitted for inclusion in the Work
|
132
|
+
by You to the Licensor shall be under the terms and conditions of
|
133
|
+
this License, without any additional terms or conditions.
|
134
|
+
Notwithstanding the above, nothing herein shall supersede or modify
|
135
|
+
the terms of any separate license agreement you may have executed
|
136
|
+
with Licensor regarding such Contributions.
|
137
|
+
|
138
|
+
6. Trademarks. This License does not grant permission to use the trade
|
139
|
+
names, trademarks, service marks, or product names of the Licensor,
|
140
|
+
except as required for reasonable and customary use in describing the
|
141
|
+
origin of the Work and reproducing the content of the NOTICE file.
|
142
|
+
|
143
|
+
7. Disclaimer of Warranty. Unless required by applicable law or
|
144
|
+
agreed to in writing, Licensor provides the Work (and each
|
145
|
+
Contributor provides its Contributions) on an "AS IS" BASIS,
|
146
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
|
147
|
+
implied, including, without limitation, any warranties or conditions
|
148
|
+
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
|
149
|
+
PARTICULAR PURPOSE. You are solely responsible for determining the
|
150
|
+
appropriateness of using or redistributing the Work and assume any
|
151
|
+
risks associated with Your exercise of permissions under this License.
|
152
|
+
|
153
|
+
8. Limitation of Liability. In no event and under no legal theory,
|
154
|
+
whether in tort (including negligence), contract, or otherwise,
|
155
|
+
unless required by applicable law (such as deliberate and grossly
|
156
|
+
negligent acts) or agreed to in writing, shall any Contributor be
|
157
|
+
liable to You for damages, including any direct, indirect, special,
|
158
|
+
incidental, or consequential damages of any character arising as a
|
159
|
+
result of this License or out of the use or inability to use the
|
160
|
+
Work (including but not limited to damages for loss of goodwill,
|
161
|
+
work stoppage, computer failure or malfunction, or any and all
|
162
|
+
other commercial damages or losses), even if such Contributor
|
163
|
+
has been advised of the possibility of such damages.
|
164
|
+
|
165
|
+
9. Accepting Warranty or Additional Liability. While redistributing
|
166
|
+
the Work or Derivative Works thereof, You may choose to offer,
|
167
|
+
and charge a fee for, acceptance of support, warranty, indemnity,
|
168
|
+
or other liability obligations and/or rights consistent with this
|
169
|
+
License. However, in accepting such obligations, You may act only
|
170
|
+
on Your own behalf and on Your sole responsibility, not on behalf
|
171
|
+
of any other Contributor, and only if You agree to indemnify,
|
172
|
+
defend, and hold each Contributor harmless for any liability
|
173
|
+
incurred by, or claims asserted against, such Contributor by reason
|
174
|
+
of your accepting any such warranty or additional liability.
|
175
|
+
|
176
|
+
END OF TERMS AND CONDITIONS
|
177
|
+
|
178
|
+
APPENDIX: How to apply the Apache License to your work.
|
179
|
+
|
180
|
+
To apply the Apache License to your work, attach the following
|
181
|
+
boilerplate notice, with the fields enclosed by brackets "[]"
|
182
|
+
replaced with your own identifying information. (Don't include
|
183
|
+
the brackets!) The text should be enclosed in the appropriate
|
184
|
+
comment syntax for the file format. We also recommend that a
|
185
|
+
file or class name and description of purpose be included on the
|
186
|
+
same "printed page" as the copyright notice for easier
|
187
|
+
identification within third-party archives.
|
188
|
+
|
189
|
+
Copyright [yyyy] [name of copyright owner]
|
190
|
+
|
191
|
+
Licensed under the Apache License, Version 2.0 (the "License");
|
192
|
+
you may not use this file except in compliance with the License.
|
193
|
+
You may obtain a copy of the License at
|
194
|
+
|
195
|
+
http://www.apache.org/licenses/LICENSE-2.0
|
196
|
+
|
197
|
+
Unless required by applicable law or agreed to in writing, software
|
198
|
+
distributed under the License is distributed on an "AS IS" BASIS,
|
199
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
200
|
+
See the License for the specific language governing permissions and
|
201
|
+
limitations under the License.
|
data/README.md
ADDED
@@ -0,0 +1,135 @@
|
|
1
|
+
# Ruby Client for the Google Cloud Optimization V1 API
|
2
|
+
|
3
|
+
API Client library for the Google Cloud Optimization V1 API
|
4
|
+
|
5
|
+
google-cloud-optimization-v1 is the official client library for the Google Cloud Optimization V1 API.
|
6
|
+
|
7
|
+
https://github.com/googleapis/google-cloud-ruby
|
8
|
+
|
9
|
+
This gem is a _versioned_ client. It provides basic client classes for a
|
10
|
+
specific version of the Google Cloud Optimization V1 API. Most users should consider using
|
11
|
+
the main client gem,
|
12
|
+
[google-cloud-optimization](https://rubygems.org/gems/google-cloud-optimization).
|
13
|
+
See the section below titled *Which client should I use?* for more information.
|
14
|
+
|
15
|
+
## Installation
|
16
|
+
|
17
|
+
```
|
18
|
+
$ gem install google-cloud-optimization-v1
|
19
|
+
```
|
20
|
+
|
21
|
+
## Before You Begin
|
22
|
+
|
23
|
+
In order to use this library, you first need to go through the following steps:
|
24
|
+
|
25
|
+
1. [Select or create a Cloud Platform project.](https://console.cloud.google.com/project)
|
26
|
+
1. [Enable billing for your project.](https://cloud.google.com/billing/docs/how-to/modify-project#enable_billing_for_a_project)
|
27
|
+
1. {file:AUTHENTICATION.md Set up authentication.}
|
28
|
+
|
29
|
+
## Quick Start
|
30
|
+
|
31
|
+
```ruby
|
32
|
+
require "google/cloud/optimization/v1"
|
33
|
+
|
34
|
+
client = ::Google::Cloud::Optimization::V1::FleetRouting::Client.new
|
35
|
+
request = ::Google::Cloud::Optimization::V1::OptimizeToursRequest.new # (request fields as keyword arguments...)
|
36
|
+
response = client.optimize_tours request
|
37
|
+
```
|
38
|
+
|
39
|
+
View the [Client Library Documentation](https://cloud.google.com/ruby/docs/reference/google-cloud-optimization-v1/latest)
|
40
|
+
for class and method documentation.
|
41
|
+
|
42
|
+
## Enabling Logging
|
43
|
+
|
44
|
+
To enable logging for this library, set the logger for the underlying [gRPC](https://github.com/grpc/grpc/tree/master/src/ruby) library.
|
45
|
+
The logger that you set may be a Ruby stdlib [`Logger`](https://ruby-doc.org/stdlib/libdoc/logger/rdoc/Logger.html) as shown below,
|
46
|
+
or a [`Google::Cloud::Logging::Logger`](https://googleapis.dev/ruby/google-cloud-logging/latest)
|
47
|
+
that will write logs to [Cloud Logging](https://cloud.google.com/logging/). See [grpc/logconfig.rb](https://github.com/grpc/grpc/blob/master/src/ruby/lib/grpc/logconfig.rb)
|
48
|
+
and the gRPC [spec_helper.rb](https://github.com/grpc/grpc/blob/master/src/ruby/spec/spec_helper.rb) for additional information.
|
49
|
+
|
50
|
+
Configuring a Ruby stdlib logger:
|
51
|
+
|
52
|
+
```ruby
|
53
|
+
require "logger"
|
54
|
+
|
55
|
+
module MyLogger
|
56
|
+
LOGGER = Logger.new $stderr, level: Logger::WARN
|
57
|
+
def logger
|
58
|
+
LOGGER
|
59
|
+
end
|
60
|
+
end
|
61
|
+
|
62
|
+
# Define a gRPC module-level logger method before grpc/logconfig.rb loads.
|
63
|
+
module GRPC
|
64
|
+
extend MyLogger
|
65
|
+
end
|
66
|
+
```
|
67
|
+
|
68
|
+
## Supported Ruby Versions
|
69
|
+
|
70
|
+
This library is supported on Ruby 2.5+.
|
71
|
+
|
72
|
+
Google provides official support for Ruby versions that are actively supported
|
73
|
+
by Ruby Core—that is, Ruby versions that are either in normal maintenance or
|
74
|
+
in security maintenance, and not end of life. Currently, this means Ruby 2.5
|
75
|
+
and later. Older versions of Ruby _may_ still work, but are unsupported and not
|
76
|
+
recommended. See https://www.ruby-lang.org/en/downloads/branches/ for details
|
77
|
+
about the Ruby support schedule.
|
78
|
+
|
79
|
+
## Which client should I use?
|
80
|
+
|
81
|
+
Most modern Ruby client libraries for Google APIs come in two flavors: the main
|
82
|
+
client library with a name such as `google-cloud-optimization`,
|
83
|
+
and lower-level _versioned_ client libraries with names such as
|
84
|
+
`google-cloud-optimization-v1`.
|
85
|
+
_In most cases, you should install the main client._
|
86
|
+
|
87
|
+
### What's the difference between the main client and a versioned client?
|
88
|
+
|
89
|
+
A _versioned client_ provides a basic set of data types and client classes for
|
90
|
+
a _single version_ of a specific service. (That is, for a service with multiple
|
91
|
+
versions, there might be a separate versioned client for each service version.)
|
92
|
+
Most versioned clients are written and maintained by a code generator.
|
93
|
+
|
94
|
+
The _main client_ is designed to provide you with the _recommended_ client
|
95
|
+
interfaces for the service. There will be only one main client for any given
|
96
|
+
service, even a service with multiple versions. The main client includes
|
97
|
+
factory methods for constructing the client objects we recommend for most
|
98
|
+
users. In some cases, those will be classes provided by an underlying versioned
|
99
|
+
client; in other cases, they will be handwritten higher-level client objects
|
100
|
+
with additional capabilities, convenience methods, or best practices built in.
|
101
|
+
Generally, the main client will default to a recommended service version,
|
102
|
+
although in some cases you can override this if you need to talk to a specific
|
103
|
+
service version.
|
104
|
+
|
105
|
+
### Why would I want to use the main client?
|
106
|
+
|
107
|
+
We recommend that most users install the main client gem for a service. You can
|
108
|
+
identify this gem as the one _without_ a version in its name, e.g.
|
109
|
+
`google-cloud-optimization`.
|
110
|
+
The main client is recommended because it will embody the best practices for
|
111
|
+
accessing the service, and may also provide more convenient interfaces or
|
112
|
+
tighter integration into frameworks and third-party libraries. In addition, the
|
113
|
+
documentation and samples published by Google will generally demonstrate use of
|
114
|
+
the main client.
|
115
|
+
|
116
|
+
### Why would I want to use a versioned client?
|
117
|
+
|
118
|
+
You can use a versioned client if you are content with a possibly lower-level
|
119
|
+
class interface, you explicitly want to avoid features provided by the main
|
120
|
+
client, or you want to access a specific service version not be covered by the
|
121
|
+
main client. You can identify versioned client gems because the service version
|
122
|
+
is part of the name, e.g. `google-cloud-optimization-v1`.
|
123
|
+
|
124
|
+
### What about the google-apis-<name> clients?
|
125
|
+
|
126
|
+
Client library gems with names that begin with `google-apis-` are based on an
|
127
|
+
older code generation technology. They talk to a REST/JSON backend (whereas
|
128
|
+
most modern clients talk to a [gRPC](https://grpc.io/) backend) and they may
|
129
|
+
not offer the same performance, features, and ease of use provided by more
|
130
|
+
modern clients.
|
131
|
+
|
132
|
+
The `google-apis-` clients have wide coverage across Google services, so you
|
133
|
+
might need to use one if there is no modern client available for the service.
|
134
|
+
However, if a modern client is available, we generally recommend it over the
|
135
|
+
older `google-apis-` clients.
|
@@ -0,0 +1,63 @@
|
|
1
|
+
# Generated by the protocol buffer compiler. DO NOT EDIT!
|
2
|
+
# source: google/cloud/optimization/v1/async_model.proto
|
3
|
+
|
4
|
+
require 'google/api/field_behavior_pb'
|
5
|
+
require 'google/protobuf/timestamp_pb'
|
6
|
+
require 'google/protobuf'
|
7
|
+
|
8
|
+
Google::Protobuf::DescriptorPool.generated_pool.build do
|
9
|
+
add_file("google/cloud/optimization/v1/async_model.proto", :syntax => :proto3) do
|
10
|
+
add_message "google.cloud.optimization.v1.InputConfig" do
|
11
|
+
optional :data_format, :enum, 2, "google.cloud.optimization.v1.DataFormat"
|
12
|
+
oneof :source do
|
13
|
+
optional :gcs_source, :message, 1, "google.cloud.optimization.v1.GcsSource"
|
14
|
+
end
|
15
|
+
end
|
16
|
+
add_message "google.cloud.optimization.v1.OutputConfig" do
|
17
|
+
optional :data_format, :enum, 2, "google.cloud.optimization.v1.DataFormat"
|
18
|
+
oneof :destination do
|
19
|
+
optional :gcs_destination, :message, 1, "google.cloud.optimization.v1.GcsDestination"
|
20
|
+
end
|
21
|
+
end
|
22
|
+
add_message "google.cloud.optimization.v1.GcsSource" do
|
23
|
+
optional :uri, :string, 1
|
24
|
+
end
|
25
|
+
add_message "google.cloud.optimization.v1.GcsDestination" do
|
26
|
+
optional :uri, :string, 1
|
27
|
+
end
|
28
|
+
add_message "google.cloud.optimization.v1.AsyncModelMetadata" do
|
29
|
+
optional :state, :enum, 1, "google.cloud.optimization.v1.AsyncModelMetadata.State"
|
30
|
+
optional :state_message, :string, 2
|
31
|
+
optional :create_time, :message, 3, "google.protobuf.Timestamp"
|
32
|
+
optional :update_time, :message, 4, "google.protobuf.Timestamp"
|
33
|
+
end
|
34
|
+
add_enum "google.cloud.optimization.v1.AsyncModelMetadata.State" do
|
35
|
+
value :STATE_UNSPECIFIED, 0
|
36
|
+
value :RUNNING, 1
|
37
|
+
value :SUCCEEDED, 2
|
38
|
+
value :CANCELLED, 3
|
39
|
+
value :FAILED, 4
|
40
|
+
end
|
41
|
+
add_enum "google.cloud.optimization.v1.DataFormat" do
|
42
|
+
value :DATA_FORMAT_UNSPECIFIED, 0
|
43
|
+
value :JSON, 1
|
44
|
+
value :STRING, 2
|
45
|
+
end
|
46
|
+
end
|
47
|
+
end
|
48
|
+
|
49
|
+
module Google
|
50
|
+
module Cloud
|
51
|
+
module Optimization
|
52
|
+
module V1
|
53
|
+
InputConfig = ::Google::Protobuf::DescriptorPool.generated_pool.lookup("google.cloud.optimization.v1.InputConfig").msgclass
|
54
|
+
OutputConfig = ::Google::Protobuf::DescriptorPool.generated_pool.lookup("google.cloud.optimization.v1.OutputConfig").msgclass
|
55
|
+
GcsSource = ::Google::Protobuf::DescriptorPool.generated_pool.lookup("google.cloud.optimization.v1.GcsSource").msgclass
|
56
|
+
GcsDestination = ::Google::Protobuf::DescriptorPool.generated_pool.lookup("google.cloud.optimization.v1.GcsDestination").msgclass
|
57
|
+
AsyncModelMetadata = ::Google::Protobuf::DescriptorPool.generated_pool.lookup("google.cloud.optimization.v1.AsyncModelMetadata").msgclass
|
58
|
+
AsyncModelMetadata::State = ::Google::Protobuf::DescriptorPool.generated_pool.lookup("google.cloud.optimization.v1.AsyncModelMetadata.State").enummodule
|
59
|
+
DataFormat = ::Google::Protobuf::DescriptorPool.generated_pool.lookup("google.cloud.optimization.v1.DataFormat").enummodule
|
60
|
+
end
|
61
|
+
end
|
62
|
+
end
|
63
|
+
end
|