google-apis-beyondcorp_v1 0.8.0 → 0.9.0

Sign up to get free protection for your applications and to get access to all the features.
checksums.yaml CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  SHA256:
3
- metadata.gz: dd2139fe029cc3456c2734f9932ab054e24569d18f0bc12af9e1ad20327d3b23
4
- data.tar.gz: 157a171fff67856563850a66e944cd0053294d86bafaeb6f27ccce93772b45a7
3
+ metadata.gz: 1d51671af06e98358fc90e80b5679baedfa4035b42a5672184fbf338e4a049ac
4
+ data.tar.gz: 2f1693e9fc5a9b65c1a78e8813be24074050fd05da617871a226f5a65affadb4
5
5
  SHA512:
6
- metadata.gz: a6958ff3722382faa05c3572ebba0827121d7f2336cb9ee6b1f8d135cdb451ebd4f27a7492bcd8da0247dbc32a5466b07d8d0f733564b9c206a1638180e3a73e
7
- data.tar.gz: '069d02eb341c17dffb9b346a6a09778a43255c485fc1b94455c65246d6422d09c25ac2c417bab24980dbfbc9c01bfde6b66561c43f39f051abb2f58ae81e4e30'
6
+ metadata.gz: ce5da8de30b0883127f7b89b766c6372ad2df196834d1dceb79b152229c4525615cc40327ec0474366b1ee11634129750fa67abf02fdeffd01304dd7b8a7f047
7
+ data.tar.gz: 71212bafad91c33d17bfb69257aded2a7b10fab787c862a6527d68614277c38f5ade1f54942ab069236b755376aaedfa82418768c6bacf944cb13a77b759c88b
data/CHANGELOG.md CHANGED
@@ -1,5 +1,10 @@
1
1
  # Release history for google-apis-beyondcorp_v1
2
2
 
3
+ ### v0.9.0 (2023-02-12)
4
+
5
+ * Regenerated from discovery document revision 20230206
6
+ * Regenerated using generator version 0.11.1
7
+
3
8
  ### v0.8.0 (2022-11-01)
4
9
 
5
10
  * Regenerated from discovery document revision 20221019
@@ -1391,7 +1391,7 @@ module Google
1391
1391
  # request ID so that if you must retry your request, the server will know to
1392
1392
  # ignore the request if it has already been completed. The server will guarantee
1393
1393
  # that for at least 60 minutes since the first request. For example, consider a
1394
- # situation where you make an initial request and t he request times out. If you
1394
+ # situation where you make an initial request and the request times out. If you
1395
1395
  # make the request again with the same request ID, the server can check if
1396
1396
  # original operation with the same request ID was received, and if so, will
1397
1397
  # ignore the second request. This prevents clients from accidentally creating
@@ -2128,22 +2128,22 @@ module Google
2128
2128
  # kubernetes-engine/docs/how-to/kubernetes-service-accounts). For example, `my-
2129
2129
  # project.svc.id.goog[my-namespace/my-kubernetes-sa]`. * `group:`emailid``: An
2130
2130
  # email address that represents a Google group. For example, `admins@example.com`
2131
- # . * `deleted:user:`emailid`?uid=`uniqueid``: An email address (plus unique
2132
- # identifier) representing a user that has been recently deleted. For example, `
2133
- # alice@example.com?uid=123456789012345678901`. If the user is recovered, this
2134
- # value reverts to `user:`emailid`` and the recovered user retains the role in
2135
- # the binding. * `deleted:serviceAccount:`emailid`?uid=`uniqueid``: An email
2136
- # address (plus unique identifier) representing a service account that has been
2137
- # recently deleted. For example, `my-other-app@appspot.gserviceaccount.com?uid=
2131
+ # . * `domain:`domain``: The G Suite domain (primary) that represents all the
2132
+ # users of that domain. For example, `google.com` or `example.com`. * `deleted:
2133
+ # user:`emailid`?uid=`uniqueid``: An email address (plus unique identifier)
2134
+ # representing a user that has been recently deleted. For example, `alice@
2135
+ # example.com?uid=123456789012345678901`. If the user is recovered, this value
2136
+ # reverts to `user:`emailid`` and the recovered user retains the role in the
2137
+ # binding. * `deleted:serviceAccount:`emailid`?uid=`uniqueid``: An email address
2138
+ # (plus unique identifier) representing a service account that has been recently
2139
+ # deleted. For example, `my-other-app@appspot.gserviceaccount.com?uid=
2138
2140
  # 123456789012345678901`. If the service account is undeleted, this value
2139
2141
  # reverts to `serviceAccount:`emailid`` and the undeleted service account
2140
2142
  # retains the role in the binding. * `deleted:group:`emailid`?uid=`uniqueid``:
2141
2143
  # An email address (plus unique identifier) representing a Google group that has
2142
2144
  # been recently deleted. For example, `admins@example.com?uid=
2143
2145
  # 123456789012345678901`. If the group is recovered, this value reverts to `
2144
- # group:`emailid`` and the recovered group retains the role in the binding. * `
2145
- # domain:`domain``: The G Suite domain (primary) that represents all the users
2146
- # of that domain. For example, `google.com` or `example.com`.
2146
+ # group:`emailid`` and the recovered group retains the role in the binding.
2147
2147
  # Corresponds to the JSON property `members`
2148
2148
  # @return [Array<String>]
2149
2149
  attr_accessor :members
@@ -16,13 +16,13 @@ module Google
16
16
  module Apis
17
17
  module BeyondcorpV1
18
18
  # Version of the google-apis-beyondcorp_v1 gem
19
- GEM_VERSION = "0.8.0"
19
+ GEM_VERSION = "0.9.0"
20
20
 
21
21
  # Version of the code generator used to generate this client
22
- GENERATOR_VERSION = "0.11.0"
22
+ GENERATOR_VERSION = "0.11.1"
23
23
 
24
24
  # Revision of the discovery document this client was generated from
25
- REVISION = "20221019"
25
+ REVISION = "20230206"
26
26
  end
27
27
  end
28
28
  end
@@ -139,7 +139,7 @@ module Google
139
139
  # request ID so that if you must retry your request, the server will know to
140
140
  # ignore the request if it has already been completed. The server will guarantee
141
141
  # that for at least 60 minutes since the first request. For example, consider a
142
- # situation where you make an initial request and t he request times out. If you
142
+ # situation where you make an initial request and the request times out. If you
143
143
  # make the request again with the same request ID, the server can check if
144
144
  # original operation with the same request ID was received, and if so, will
145
145
  # ignore the second request. This prevents clients from accidentally creating
@@ -189,7 +189,7 @@ module Google
189
189
  # request ID so that if you must retry your request, the server will know to
190
190
  # ignore the request if it has already been completed. The server will guarantee
191
191
  # that for at least 60 minutes after the first request. For example, consider a
192
- # situation where you make an initial request and t he request times out. If you
192
+ # situation where you make an initial request and the request times out. If you
193
193
  # make the request again with the same request ID, the server can check if
194
194
  # original operation with the same request ID was received, and if so, will
195
195
  # ignore the second request. This prevents clients from accidentally creating
@@ -364,7 +364,7 @@ module Google
364
364
  # request ID so that if you must retry your request, the server will know to
365
365
  # ignore the request if it has already been completed. The server will guarantee
366
366
  # that for at least 60 minutes since the first request. For example, consider a
367
- # situation where you make an initial request and t he request times out. If you
367
+ # situation where you make an initial request and the request times out. If you
368
368
  # make the request again with the same request ID, the server can check if
369
369
  # original operation with the same request ID was received, and if so, will
370
370
  # ignore the second request. This prevents clients from accidentally creating
@@ -549,7 +549,7 @@ module Google
549
549
  # request ID so that if you must retry your request, the server will know to
550
550
  # ignore the request if it has already been completed. The server will guarantee
551
551
  # that for at least 60 minutes since the first request. For example, consider a
552
- # situation where you make an initial request and t he request times out. If you
552
+ # situation where you make an initial request and the request times out. If you
553
553
  # make the request again with the same request ID, the server can check if
554
554
  # original operation with the same request ID was received, and if so, will
555
555
  # ignore the second request. This prevents clients from accidentally creating
@@ -599,7 +599,7 @@ module Google
599
599
  # request ID so that if you must retry your request, the server will know to
600
600
  # ignore the request if it has already been completed. The server will guarantee
601
601
  # that for at least 60 minutes after the first request. For example, consider a
602
- # situation where you make an initial request and t he request times out. If you
602
+ # situation where you make an initial request and the request times out. If you
603
603
  # make the request again with the same request ID, the server can check if
604
604
  # original operation with the same request ID was received, and if so, will
605
605
  # ignore the second request. This prevents clients from accidentally creating
@@ -772,7 +772,7 @@ module Google
772
772
  # request ID so that if you must retry your request, the server will know to
773
773
  # ignore the request if it has already been completed. The server will guarantee
774
774
  # that for at least 60 minutes since the first request. For example, consider a
775
- # situation where you make an initial request and t he request times out. If you
775
+ # situation where you make an initial request and the request times out. If you
776
776
  # make the request again with the same request ID, the server can check if
777
777
  # original operation with the same request ID was received, and if so, will
778
778
  # ignore the second request. This prevents clients from accidentally creating
@@ -973,7 +973,7 @@ module Google
973
973
  # request ID so that if you must retry your request, the server will know to
974
974
  # ignore the request if it has already been completed. The server will guarantee
975
975
  # that for at least 60 minutes since the first request. For example, consider a
976
- # situation where you make an initial request and t he request times out. If you
976
+ # situation where you make an initial request and the request times out. If you
977
977
  # make the request again with the same request ID, the server can check if
978
978
  # original operation with the same request ID was received, and if so, will
979
979
  # ignore the second request. This prevents clients from accidentally creating
@@ -1023,7 +1023,7 @@ module Google
1023
1023
  # request ID so that if you must retry your request, the server will know to
1024
1024
  # ignore the request if it has already been completed. The server will guarantee
1025
1025
  # that for at least 60 minutes after the first request. For example, consider a
1026
- # situation where you make an initial request and t he request times out. If you
1026
+ # situation where you make an initial request and the request times out. If you
1027
1027
  # make the request again with the same request ID, the server can check if
1028
1028
  # original operation with the same request ID was received, and if so, will
1029
1029
  # ignore the second request. This prevents clients from accidentally creating
@@ -1630,7 +1630,7 @@ module Google
1630
1630
  # request ID so that if you must retry your request, the server will know to
1631
1631
  # ignore the request if it has already been completed. The server will guarantee
1632
1632
  # that for at least 60 minutes since the first request. For example, consider a
1633
- # situation where you make an initial request and t he request times out. If you
1633
+ # situation where you make an initial request and the request times out. If you
1634
1634
  # make the request again with the same request ID, the server can check if
1635
1635
  # original operation with the same request ID was received, and if so, will
1636
1636
  # ignore the second request. This prevents clients from accidentally creating
@@ -1679,7 +1679,7 @@ module Google
1679
1679
  # request ID so that if you must retry your request, the server will know to
1680
1680
  # ignore the request if it has already been completed. The server will guarantee
1681
1681
  # that for at least 60 minutes after the first request. For example, consider a
1682
- # situation where you make an initial request and t he request times out. If you
1682
+ # situation where you make an initial request and the request times out. If you
1683
1683
  # make the request again with the same request ID, the server can check if
1684
1684
  # original operation with the same request ID was received, and if so, will
1685
1685
  # ignore the second request. This prevents clients from accidentally creating
metadata CHANGED
@@ -1,14 +1,14 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: google-apis-beyondcorp_v1
3
3
  version: !ruby/object:Gem::Version
4
- version: 0.8.0
4
+ version: 0.9.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-07 00:00:00.000000000 Z
11
+ date: 2023-02-12 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-beyondcorp_v1/CHANGELOG.md
61
- documentation_uri: https://googleapis.dev/ruby/google-apis-beyondcorp_v1/v0.8.0
61
+ documentation_uri: https://googleapis.dev/ruby/google-apis-beyondcorp_v1/v0.9.0
62
62
  source_code_uri: https://github.com/googleapis/google-api-ruby-client/tree/main/generated/google-apis-beyondcorp_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 BeyondCorp API V1