google-apis-admin_reports_v1 0.14.0 → 0.16.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
checksums.yaml CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  SHA256:
3
- metadata.gz: 993afaff9d475c3fc44417add0bf949c628e95ab60bd24c4fdbe29ceee624621
4
- data.tar.gz: e92ffb15bb66e9c3958949185a0303865102fd77958d330d92f8a66b08789e62
3
+ metadata.gz: 5d0302fc1f8288be27f90d7800c291b6e0ed362d7c2719e98fb07dafbded8c0a
4
+ data.tar.gz: 54f3c35998d56f3ed34d6eed6e5b59e9d8ce38e9c859d6734b2b2a71a61470a9
5
5
  SHA512:
6
- metadata.gz: ce91d2a5f97c744ae5181bc5580c6794faa1e7d6295111956d505948f7d90ee4e04d3f5131926a2f92f46c6fd0c39e26ffb2ca9f96117948b9c71be6aaefb4c3
7
- data.tar.gz: 6ed6011b18b216ba0ad6b5e53a291b3303a0b76782bb04b773bbdd3a0c210afdb20a3c698d1f35d0e0c99cff083ffd137583aff628852f5ac8c6a22ca5b5a008
6
+ metadata.gz: f050646021fbb6eecffbf94bc3d7b2dccf9ebbae5ffafe7b9ee49d2d51b2db80d399976f8168c504ec4cce8a9910ebb3a92f851419608c0e8a016423028eb8f2
7
+ data.tar.gz: d88155c59bf6144a9999a0661486318bf1020d00c0388a066eb5452fc96496c79ac3e52ac5574a3d2e08d51478004bf7cb59952eacaa705abe9f53967bd17698
data/CHANGELOG.md CHANGED
@@ -1,5 +1,14 @@
1
1
  # Release history for google-apis-admin_reports_v1
2
2
 
3
+ ### v0.16.0 (2023-02-15)
4
+
5
+ * Regenerated using generator version 0.12.0
6
+
7
+ ### v0.15.0 (2022-11-19)
8
+
9
+ * Regenerated from discovery document revision 20221108
10
+ * Regenerated using generator version 0.11.0
11
+
3
12
  ### v0.14.0 (2022-09-21)
4
13
 
5
14
  * 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.14.0"
19
+ GEM_VERSION = "0.16.0"
20
20
 
21
21
  # Version of the code generator used to generate this client
22
- GENERATOR_VERSION = "0.10.0"
22
+ GENERATOR_VERSION = "0.12.0"
23
23
 
24
24
  # Revision of the discovery document this client was generated from
25
- REVISION = "20211207"
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. The list is composed of
102
- # event parameters that are manipulated by relational operators. Event
103
- # parameters are in the form `parameter1 name[parameter1 value],parameter2 name[
104
- # parameter2 value],...` These event parameters are associated with a specific `
105
- # eventName`. An empty report is returned if the filtered request's parameter
106
- # does not belong to the `eventName`. For more information about `eventName`
107
- # parameters, see the list of event names for various applications above in `
108
- # applicationName`. In the following Admin Activity example, the <> operator is
109
- # URL-encoded in the request's query string (%3C%3E): GET...&eventName=
110
- # CHANGE_CALENDAR_SETTING &filters=NEW_VALUE%3C%3EREAD_ONLY_ACCESS In the
111
- # following Drive example, the list can be a view or edit event's `doc_id`
112
- # parameter with a value that is manipulated by an 'equal to' (==) or 'not equal
113
- # to' (<>) relational operator. In the first example, the report returns each
114
- # edited document's `doc_id`. In the second example, the report returns each
115
- # viewed document's `doc_id` that equals the value 12345 and does not return any
116
- # viewed document's which have a `doc_id` value of 98765. The <> operator is URL-
117
- # encoded in the request's query string (%3C%3E): GET...&eventName=edit&filters=
118
- # doc_id GET...&eventName=view&filters=doc_id==12345,doc_id%3C%3E98765 The
119
- # relational operators include: - `==` - 'equal to'. - `<>` - 'not equal to'. It
120
- # is URL-encoded (%3C%3E). - `<` - 'less than'. It is URL-encoded (%3C). - `<=` -
121
- # 'less than or equal to'. It is URL-encoded (%3C=). - `>` - 'greater than'. It
122
- # is URL-encoded (%3E). - `>=` - 'greater than or equal to'. It is URL-encoded (%
123
- # 3E=). *Note:* The API doesn't accept multiple values of a parameter. If a
124
- # particular parameter is supplied more than once in the API request, the API
125
- # only accepts the last value of that request parameter. In addition, if an
126
- # invalid request parameter is supplied in the API request, the API ignores that
127
- # request parameter and returns the response corresponding to the remaining
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. The list is composed of
239
- # event parameters that are manipulated by relational operators. Event
240
- # parameters are in the form `parameter1 name[parameter1 value],parameter2 name[
241
- # parameter2 value],...` These event parameters are associated with a specific `
242
- # eventName`. An empty report is returned if the filtered request's parameter
243
- # does not belong to the `eventName`. For more information about `eventName`
244
- # parameters, see the list of event names for various applications above in `
245
- # applicationName`. In the following Admin Activity example, the <> operator is
246
- # URL-encoded in the request's query string (%3C%3E): GET...&eventName=
247
- # CHANGE_CALENDAR_SETTING &filters=NEW_VALUE%3C%3EREAD_ONLY_ACCESS In the
248
- # following Drive example, the list can be a view or edit event's `doc_id`
249
- # parameter with a value that is manipulated by an 'equal to' (==) or 'not equal
250
- # to' (<>) relational operator. In the first example, the report returns each
251
- # edited document's `doc_id`. In the second example, the report returns each
252
- # viewed document's `doc_id` that equals the value 12345 and does not return any
253
- # viewed document's which have a `doc_id` value of 98765. The <> operator is URL-
254
- # encoded in the request's query string (%3C%3E): GET...&eventName=edit&filters=
255
- # doc_id GET...&eventName=view&filters=doc_id==12345,doc_id%3C%3E98765 The
256
- # relational operators include: - `==` - 'equal to'. - `<>` - 'not equal to'. It
257
- # is URL-encoded (%3C%3E). - `<` - 'less than'. It is URL-encoded (%3C). - `<=` -
258
- # 'less than or equal to'. It is URL-encoded (%3C=). - `>` - 'greater than'. It
259
- # is URL-encoded (%3E). - `>=` - 'greater than or equal to'. It is URL-encoded (%
260
- # 3E=). *Note:* The API doesn't accept multiple values of a parameter. If a
261
- # particular parameter is supplied more than once in the API request, the API
262
- # only accepts the last value of that request parameter. In addition, if an
263
- # invalid request parameter is supplied in the API request, the API ignores that
264
- # request parameter and returns the response corresponding to the remaining
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. The timestamp is in the ISO 8601
366
- # format, yyyy-mm-dd. We recommend you use your account's time zone for this.
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. The timestamp is in the ISO 8601
520
- # format, yyyy-mm-dd. We recommend you use your account's time zone for this.
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.14.0
4
+ version: 0.16.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-09-26 00:00:00.000000000 Z
11
+ date: 2023-02-19 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.0
19
+ version: 0.11.0
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.0
29
+ version: 0.11.0
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.14.0
61
+ documentation_uri: https://googleapis.dev/ruby/google-apis-admin_reports_v1/v0.16.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: []
@@ -75,7 +75,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
75
75
  - !ruby/object:Gem::Version
76
76
  version: '0'
77
77
  requirements: []
78
- rubygems_version: 3.3.14
78
+ rubygems_version: 3.4.2
79
79
  signing_key:
80
80
  specification_version: 4
81
81
  summary: Simple REST client for Admin SDK API ReportsV1