google-apis-admin_reports_v1 0.14.0 → 0.15.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 +5 -0
- data/lib/google/apis/admin_reports_v1/gem_version.rb +3 -3
- data/lib/google/apis/admin_reports_v1/service.rb +60 -62
- 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: 2e46444ea88e1ef0219a07abe3848969f24b3a58bb8daaec16d845d92178b0e4
|
4
|
+
data.tar.gz: e2a036693b1cc21c9e8702f999b91ad7fc999ffdb3aa491feee9a781f96093e9
|
5
5
|
SHA512:
|
6
|
-
metadata.gz:
|
7
|
-
data.tar.gz:
|
6
|
+
metadata.gz: 74931339b3fe7de20f19cbe9b6945b861645dc3e65b4b0d1e24cf4932263a6494af57ee3c5ee4775bccfbf570a20d55a5012badd26a116725017489157bffa70
|
7
|
+
data.tar.gz: 650f3336131cc0b83051bfbf027822b30f950c34635b32c77ea654df5f8ef7e998120c01b5fc55a385c8d6117e564cd167bc54940a09e18e7d83dc1e1db79ad7
|
data/CHANGELOG.md
CHANGED
@@ -1,5 +1,10 @@
|
|
1
1
|
# Release history for google-apis-admin_reports_v1
|
2
2
|
|
3
|
+
### v0.15.0 (2022-11-19)
|
4
|
+
|
5
|
+
* Regenerated from discovery document revision 20221108
|
6
|
+
* Regenerated using generator version 0.11.0
|
7
|
+
|
3
8
|
### v0.14.0 (2022-09-21)
|
4
9
|
|
5
10
|
* Regenerated using generator version 0.10.0
|
@@ -16,13 +16,13 @@ module Google
|
|
16
16
|
module Apis
|
17
17
|
module AdminReportsV1
|
18
18
|
# Version of the google-apis-admin_reports_v1 gem
|
19
|
-
GEM_VERSION = "0.
|
19
|
+
GEM_VERSION = "0.15.0"
|
20
20
|
|
21
21
|
# Version of the code generator used to generate this client
|
22
|
-
GENERATOR_VERSION = "0.
|
22
|
+
GENERATOR_VERSION = "0.11.0"
|
23
23
|
|
24
24
|
# Revision of the discovery document this client was generated from
|
25
|
-
REVISION = "
|
25
|
+
REVISION = "20221108"
|
26
26
|
end
|
27
27
|
end
|
28
28
|
end
|
@@ -98,35 +98,33 @@ module Google
|
|
98
98
|
# eventName` query strings and parameters, see the list of event names for
|
99
99
|
# various applications above in `applicationName`.
|
100
100
|
# @param [String] filters
|
101
|
-
# The `filters` query string is a comma-separated list
|
102
|
-
#
|
103
|
-
#
|
104
|
-
# parameter2 value
|
105
|
-
# eventName`. An empty report is returned if the
|
106
|
-
#
|
107
|
-
#
|
108
|
-
#
|
109
|
-
#
|
110
|
-
#
|
111
|
-
#
|
112
|
-
#
|
113
|
-
#
|
114
|
-
#
|
115
|
-
#
|
116
|
-
#
|
117
|
-
#
|
118
|
-
#
|
119
|
-
#
|
120
|
-
#
|
121
|
-
#
|
122
|
-
#
|
123
|
-
#
|
124
|
-
#
|
125
|
-
#
|
126
|
-
#
|
127
|
-
#
|
128
|
-
# valid request parameters. If no parameters are requested, all parameters are
|
129
|
-
# returned.
|
101
|
+
# The `filters` query string is a comma-separated list composed of event
|
102
|
+
# parameters manipulated by relational operators. Event parameters are in the
|
103
|
+
# form ``parameter1 name``relational operator``parameter1 value`,`parameter2
|
104
|
+
# name``relational operator``parameter2 value`,...` These event parameters are
|
105
|
+
# associated with a specific `eventName`. An empty report is returned if the
|
106
|
+
# request's parameter doesn't belong to the `eventName`. For more information
|
107
|
+
# about the available `eventName` fields for each application and their
|
108
|
+
# associated parameters, go to the [ApplicationName](#applicationname) table,
|
109
|
+
# then click through to the Activity Events page in the Appendix for the
|
110
|
+
# application you want. In the following Drive activity examples, the returned
|
111
|
+
# list consists of all `edit` events where the `doc_id` parameter value matches
|
112
|
+
# the conditions defined by the relational operator. In the first example, the
|
113
|
+
# request returns all edited documents with a `doc_id` value equal to `12345`.
|
114
|
+
# In the second example, the report returns any edited documents where the `
|
115
|
+
# doc_id` value is not equal to `98765`. The `<>` operator is URL-encoded in the
|
116
|
+
# request's query string (`%3C%3E`): ``` GET...&eventName=edit&filters=doc_id==
|
117
|
+
# 12345 GET...&eventName=edit&filters=doc_id%3C%3E98765 ``` A `filters` query
|
118
|
+
# supports these relational operators: * `==`—'equal to'. * `<>`—'not equal to'.
|
119
|
+
# Must be URL-encoded (%3C%3E). * `<`—'less than'. Must be URL-encoded (%3C). * `
|
120
|
+
# <=`—'less than or equal to'. Must be URL-encoded (%3C=). * `>`—'greater than'.
|
121
|
+
# Must be URL-encoded (%3E). * `>=`—'greater than or equal to'. Must be URL-
|
122
|
+
# encoded (%3E=). **Note:** The API doesn't accept multiple values of the same
|
123
|
+
# parameter. If a parameter is supplied more than once in the API request, the
|
124
|
+
# API only accepts the last value of that parameter. In addition, if an invalid
|
125
|
+
# parameter is supplied in the API request, the API ignores that parameter and
|
126
|
+
# returns the response corresponding to the remaining valid parameters. If no
|
127
|
+
# parameters are requested, all parameters are returned.
|
130
128
|
# @param [String] group_id_filter
|
131
129
|
# Comma separated group ids (obfuscated) on which user activities are filtered,
|
132
130
|
# i.e. the response will contain activities for only those users that are a part
|
@@ -235,35 +233,33 @@ module Google
|
|
235
233
|
# eventName` query strings and parameters, see the list of event names for
|
236
234
|
# various applications above in `applicationName`.
|
237
235
|
# @param [String] filters
|
238
|
-
# The `filters` query string is a comma-separated list
|
239
|
-
#
|
240
|
-
#
|
241
|
-
# parameter2 value
|
242
|
-
# eventName`. An empty report is returned if the
|
243
|
-
#
|
244
|
-
#
|
245
|
-
#
|
246
|
-
#
|
247
|
-
#
|
248
|
-
#
|
249
|
-
#
|
250
|
-
#
|
251
|
-
#
|
252
|
-
#
|
253
|
-
#
|
254
|
-
#
|
255
|
-
#
|
256
|
-
#
|
257
|
-
#
|
258
|
-
#
|
259
|
-
#
|
260
|
-
#
|
261
|
-
#
|
262
|
-
#
|
263
|
-
#
|
264
|
-
#
|
265
|
-
# valid request parameters. If no parameters are requested, all parameters are
|
266
|
-
# returned.
|
236
|
+
# The `filters` query string is a comma-separated list composed of event
|
237
|
+
# parameters manipulated by relational operators. Event parameters are in the
|
238
|
+
# form ``parameter1 name``relational operator``parameter1 value`,`parameter2
|
239
|
+
# name``relational operator``parameter2 value`,...` These event parameters are
|
240
|
+
# associated with a specific `eventName`. An empty report is returned if the
|
241
|
+
# request's parameter doesn't belong to the `eventName`. For more information
|
242
|
+
# about the available `eventName` fields for each application and their
|
243
|
+
# associated parameters, go to the [ApplicationName](#applicationname) table,
|
244
|
+
# then click through to the Activity Events page in the Appendix for the
|
245
|
+
# application you want. In the following Drive activity examples, the returned
|
246
|
+
# list consists of all `edit` events where the `doc_id` parameter value matches
|
247
|
+
# the conditions defined by the relational operator. In the first example, the
|
248
|
+
# request returns all edited documents with a `doc_id` value equal to `12345`.
|
249
|
+
# In the second example, the report returns any edited documents where the `
|
250
|
+
# doc_id` value is not equal to `98765`. The `<>` operator is URL-encoded in the
|
251
|
+
# request's query string (`%3C%3E`): ``` GET...&eventName=edit&filters=doc_id==
|
252
|
+
# 12345 GET...&eventName=edit&filters=doc_id%3C%3E98765 ``` A `filters` query
|
253
|
+
# supports these relational operators: * `==`—'equal to'. * `<>`—'not equal to'.
|
254
|
+
# Must be URL-encoded (%3C%3E). * `<`—'less than'. Must be URL-encoded (%3C). * `
|
255
|
+
# <=`—'less than or equal to'. Must be URL-encoded (%3C=). * `>`—'greater than'.
|
256
|
+
# Must be URL-encoded (%3E). * `>=`—'greater than or equal to'. Must be URL-
|
257
|
+
# encoded (%3E=). **Note:** The API doesn't accept multiple values of the same
|
258
|
+
# parameter. If a parameter is supplied more than once in the API request, the
|
259
|
+
# API only accepts the last value of that parameter. In addition, if an invalid
|
260
|
+
# parameter is supplied in the API request, the API ignores that parameter and
|
261
|
+
# returns the response corresponding to the remaining valid parameters. If no
|
262
|
+
# parameters are requested, all parameters are returned.
|
267
263
|
# @param [String] group_id_filter
|
268
264
|
# Comma separated group ids (obfuscated) on which user activities are filtered,
|
269
265
|
# i.e. the response will contain activities for only those users that are a part
|
@@ -362,8 +358,9 @@ module Google
|
|
362
358
|
# Report guide. For more information about the customer report's parameters, see
|
363
359
|
# the Customers Usage parameters reference guides.
|
364
360
|
# @param [String] date
|
365
|
-
# Represents the date the usage occurred
|
366
|
-
# format, yyyy-mm-
|
361
|
+
# Represents the date the usage occurred, based on PST time zone. The timestamp
|
362
|
+
# is in the [ISO 8601 format](https://en.wikipedia.org/wiki/ISO_8601), `yyyy-mm-
|
363
|
+
# dd`.
|
367
364
|
# @param [String] customer_id
|
368
365
|
# The unique ID of the customer to retrieve data for.
|
369
366
|
# @param [String] page_token
|
@@ -516,8 +513,9 @@ module Google
|
|
516
513
|
# deleted user. For a deleted user, call `users.list` in Directory API with `
|
517
514
|
# showDeleted=true`, then use the returned `ID` as the `userKey`.
|
518
515
|
# @param [String] date
|
519
|
-
# Represents the date the usage occurred
|
520
|
-
#
|
516
|
+
# Represents the date the usage occurred, based on GMT-7:00 (Pacific Standard
|
517
|
+
# Time). The timestamp is in the [ISO 8601 format](https://en.wikipedia.org/wiki/
|
518
|
+
# ISO_8601), `yyyy-mm-dd`.
|
521
519
|
# @param [String] customer_id
|
522
520
|
# The unique ID of the customer to retrieve data for.
|
523
521
|
# @param [String] filters
|
metadata
CHANGED
@@ -1,14 +1,14 @@
|
|
1
1
|
--- !ruby/object:Gem::Specification
|
2
2
|
name: google-apis-admin_reports_v1
|
3
3
|
version: !ruby/object:Gem::Version
|
4
|
-
version: 0.
|
4
|
+
version: 0.15.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: 2022-
|
11
|
+
date: 2022-12-12 00:00:00.000000000 Z
|
12
12
|
dependencies:
|
13
13
|
- !ruby/object:Gem::Dependency
|
14
14
|
name: google-apis-core
|
@@ -16,7 +16,7 @@ dependencies:
|
|
16
16
|
requirements:
|
17
17
|
- - ">="
|
18
18
|
- !ruby/object:Gem::Version
|
19
|
-
version: 0.9.
|
19
|
+
version: 0.9.1
|
20
20
|
- - "<"
|
21
21
|
- !ruby/object:Gem::Version
|
22
22
|
version: 2.a
|
@@ -26,7 +26,7 @@ dependencies:
|
|
26
26
|
requirements:
|
27
27
|
- - ">="
|
28
28
|
- !ruby/object:Gem::Version
|
29
|
-
version: 0.9.
|
29
|
+
version: 0.9.1
|
30
30
|
- - "<"
|
31
31
|
- !ruby/object:Gem::Version
|
32
32
|
version: 2.a
|
@@ -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-admin_reports_v1/CHANGELOG.md
|
61
|
-
documentation_uri: https://googleapis.dev/ruby/google-apis-admin_reports_v1/v0.
|
61
|
+
documentation_uri: https://googleapis.dev/ruby/google-apis-admin_reports_v1/v0.15.0
|
62
62
|
source_code_uri: https://github.com/googleapis/google-api-ruby-client/tree/main/generated/google-apis-admin_reports_v1
|
63
63
|
post_install_message:
|
64
64
|
rdoc_options: []
|