google-cloud-logging-v2 0.5.2 → 0.5.6
Sign up to get free protection for your applications and to get access to all the features.
- checksums.yaml +4 -4
- data/.yardopts +1 -1
- data/AUTHENTICATION.md +10 -28
- data/lib/google/cloud/logging/v2/config_service/client.rb +582 -128
- data/lib/google/cloud/logging/v2/logging_service/client.rb +168 -48
- data/lib/google/cloud/logging/v2/metrics_service/client.rb +150 -56
- data/lib/google/cloud/logging/v2/version.rb +1 -1
- data/lib/google/logging/v2/log_entry_pb.rb +2 -2
- data/lib/google/logging/v2/logging_config_pb.rb +2 -2
- data/lib/google/logging/v2/logging_config_services_pb.rb +1 -1
- data/lib/google/logging/v2/logging_metrics_pb.rb +2 -2
- data/lib/google/logging/v2/logging_metrics_services_pb.rb +1 -1
- data/lib/google/logging/v2/logging_pb.rb +2 -2
- data/lib/google/logging/v2/logging_services_pb.rb +1 -1
- data/proto_docs/google/api/resource.rb +10 -71
- metadata +5 -5
checksums.yaml
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
---
|
|
2
2
|
SHA256:
|
|
3
|
-
metadata.gz:
|
|
4
|
-
data.tar.gz:
|
|
3
|
+
metadata.gz: d37896e2f4fd0a45e15c939b81ddb15fa56f1daa79ddf9449049bb53f0437f39
|
|
4
|
+
data.tar.gz: 4035d46a8bb97cd38e532b91f340b3aad614714079befcb6037d80c5b6f53ee1
|
|
5
5
|
SHA512:
|
|
6
|
-
metadata.gz:
|
|
7
|
-
data.tar.gz:
|
|
6
|
+
metadata.gz: a2fc1bf047fd4f9bff3859f3f9dd533b7b1521205983371046a5a1cff1befe0bb8fdc1870ae06e16f496d30cc84a7388285260a203f6e8cbafbfcb4326a401a7
|
|
7
|
+
data.tar.gz: f842fa2c10c3017a4347d266734cb41d4929b6918f15947f5f37d0bff44b7ea916a9abf510f816ea0cbda6b4a3e8899661a739d73ba419764254afa6e30f6a0b
|
data/.yardopts
CHANGED
data/AUTHENTICATION.md
CHANGED
|
@@ -82,8 +82,8 @@ client = ::Google::Cloud::Logging::V2::ConfigService::Client.new
|
|
|
82
82
|
|
|
83
83
|
### Configuration
|
|
84
84
|
|
|
85
|
-
The **Credentials JSON** can be configured instead of
|
|
86
|
-
environment
|
|
85
|
+
The path to the **Credentials JSON** file can be configured instead of storing
|
|
86
|
+
it in an environment variable. Either on an individual client initialization:
|
|
87
87
|
|
|
88
88
|
```ruby
|
|
89
89
|
require "google/cloud/logging/v2"
|
|
@@ -93,7 +93,7 @@ client = ::Google::Cloud::Logging::V2::ConfigService::Client.new do |config|
|
|
|
93
93
|
end
|
|
94
94
|
```
|
|
95
95
|
|
|
96
|
-
Or
|
|
96
|
+
Or globally for all clients:
|
|
97
97
|
|
|
98
98
|
```ruby
|
|
99
99
|
require "google/cloud/logging/v2"
|
|
@@ -120,15 +120,6 @@ To configure your system for this, simply:
|
|
|
120
120
|
**NOTE:** This is _not_ recommended for running in production. The Cloud SDK
|
|
121
121
|
*should* only be used during development.
|
|
122
122
|
|
|
123
|
-
[gce-how-to]: https://cloud.google.com/compute/docs/authentication#using
|
|
124
|
-
[dev-console]: https://console.cloud.google.com/project
|
|
125
|
-
|
|
126
|
-
[enable-apis]: https://raw.githubusercontent.com/GoogleCloudPlatform/gcloud-common/master/authentication/enable-apis.png
|
|
127
|
-
|
|
128
|
-
[create-new-service-account]: https://raw.githubusercontent.com/GoogleCloudPlatform/gcloud-common/master/authentication/create-new-service-account.png
|
|
129
|
-
[create-new-service-account-existing-keys]: https://raw.githubusercontent.com/GoogleCloudPlatform/gcloud-common/master/authentication/create-new-service-account-existing-keys.png
|
|
130
|
-
[reuse-service-account]: https://raw.githubusercontent.com/GoogleCloudPlatform/gcloud-common/master/authentication/reuse-service-account.png
|
|
131
|
-
|
|
132
123
|
## Creating a Service Account
|
|
133
124
|
|
|
134
125
|
Google Cloud requires **Service Account Credentials** to
|
|
@@ -139,31 +130,22 @@ If you are not running this client within
|
|
|
139
130
|
[Google Cloud Platform environments](#google-cloud-platform-environments), you
|
|
140
131
|
need a Google Developers service account.
|
|
141
132
|
|
|
142
|
-
1. Visit the [Google
|
|
133
|
+
1. Visit the [Google Cloud Console](https://console.cloud.google.com/project).
|
|
143
134
|
2. Create a new project or click on an existing project.
|
|
144
|
-
3. Activate the
|
|
135
|
+
3. Activate the menu in the upper left and select **APIs & Services**. From
|
|
145
136
|
here, you will enable the APIs that your application requires.
|
|
146
137
|
|
|
147
|
-
![Enable the APIs that your application requires][enable-apis]
|
|
148
|
-
|
|
149
138
|
*Note: You may need to enable billing in order to use these services.*
|
|
150
139
|
|
|
151
140
|
4. Select **Credentials** from the side navigation.
|
|
152
141
|
|
|
153
|
-
|
|
154
|
-
|
|
155
|
-
![Create a new service account][create-new-service-account]
|
|
156
|
-
|
|
157
|
-
![Create a new service account With Existing Keys][create-new-service-account-existing-keys]
|
|
158
|
-
|
|
159
|
-
Find the "Add credentials" drop down and select "Service account" to be
|
|
160
|
-
guided through downloading a new JSON key file.
|
|
142
|
+
Find the "Create credentials" drop down near the top of the page, and select
|
|
143
|
+
"Service account" to be guided through downloading a new JSON key file.
|
|
161
144
|
|
|
162
145
|
If you want to re-use an existing service account, you can easily generate a
|
|
163
|
-
new key file. Just select the account you wish to re-use,
|
|
164
|
-
|
|
165
|
-
|
|
166
|
-
![Re-use an existing service account][reuse-service-account]
|
|
146
|
+
new key file. Just select the account you wish to re-use, click the pencil
|
|
147
|
+
tool on the right side to edit the service account, select the **Keys** tab,
|
|
148
|
+
and then select **Add Key**.
|
|
167
149
|
|
|
168
150
|
The key file you download will be used by this library to authenticate API
|
|
169
151
|
requests and should be stored in a secure location.
|