google-apis-deploymentmanager_v2beta 0.25.0 → 0.27.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:
|
|
4
|
-
data.tar.gz:
|
|
3
|
+
metadata.gz: 49d70d6e2d54e7695cfdec1d420894365927c187f45c5a523d734f13eaf7be6f
|
|
4
|
+
data.tar.gz: 2bda06f0f73f4a739efe3b4f8e861ad773fc8eddd6005fe2abb18f5526914c96
|
|
5
5
|
SHA512:
|
|
6
|
-
metadata.gz:
|
|
7
|
-
data.tar.gz:
|
|
6
|
+
metadata.gz: 2d794d462b5478bd1f6cc3000bbd113c4b294a034203d34ba60aa6e19dc89b25db1f114c33fb7a35fc96fed13b69c30e9054657f29aef645a074be25735046d2
|
|
7
|
+
data.tar.gz: eba275593c8012ec08026a7a20d13d921dc6aea8cc4af3f83e13f13df97aafb60b7c137774b86a395171ba361b2f876f783824472041c6df277ca5e5cda7f234
|
data/CHANGELOG.md
CHANGED
|
@@ -1,5 +1,13 @@
|
|
|
1
1
|
# Release history for google-apis-deploymentmanager_v2beta
|
|
2
2
|
|
|
3
|
+
### v0.27.0 (2023-12-24)
|
|
4
|
+
|
|
5
|
+
* Regenerated from discovery document revision 20231214
|
|
6
|
+
|
|
7
|
+
### v0.26.0 (2023-10-01)
|
|
8
|
+
|
|
9
|
+
* Regenerated from discovery document revision 20230921
|
|
10
|
+
|
|
3
11
|
### v0.25.0 (2023-08-27)
|
|
4
12
|
|
|
5
13
|
* Regenerated from discovery document revision 20230821
|
|
@@ -222,21 +222,43 @@ module Google
|
|
|
222
222
|
# project.svc.id.goog[my-namespace/my-kubernetes-sa]`. * `group:`emailid``: An
|
|
223
223
|
# email address that represents a Google group. For example, `admins@example.com`
|
|
224
224
|
# . * `domain:`domain``: The G Suite domain (primary) that represents all the
|
|
225
|
-
# users of that domain. For example, `google.com` or `example.com`. * `
|
|
226
|
-
#
|
|
227
|
-
#
|
|
228
|
-
#
|
|
229
|
-
#
|
|
230
|
-
#
|
|
231
|
-
#
|
|
232
|
-
#
|
|
225
|
+
# users of that domain. For example, `google.com` or `example.com`. * `principal:
|
|
226
|
+
# //iam.googleapis.com/locations/global/workforcePools/`pool_id`/subject/`
|
|
227
|
+
# subject_attribute_value``: A single identity in a workforce identity pool. * `
|
|
228
|
+
# principalSet://iam.googleapis.com/locations/global/workforcePools/`pool_id`/
|
|
229
|
+
# group/`group_id``: All workforce identities in a group. * `principalSet://iam.
|
|
230
|
+
# googleapis.com/locations/global/workforcePools/`pool_id`/attribute.`
|
|
231
|
+
# attribute_name`/`attribute_value``: All workforce identities with a specific
|
|
232
|
+
# attribute value. * `principalSet://iam.googleapis.com/locations/global/
|
|
233
|
+
# workforcePools/`pool_id`/*`: All identities in a workforce identity pool. * `
|
|
234
|
+
# principal://iam.googleapis.com/projects/`project_number`/locations/global/
|
|
235
|
+
# workloadIdentityPools/`pool_id`/subject/`subject_attribute_value``: A single
|
|
236
|
+
# identity in a workload identity pool. * `principalSet://iam.googleapis.com/
|
|
237
|
+
# projects/`project_number`/locations/global/workloadIdentityPools/`pool_id`/
|
|
238
|
+
# group/`group_id``: A workload identity pool group. * `principalSet://iam.
|
|
239
|
+
# googleapis.com/projects/`project_number`/locations/global/
|
|
240
|
+
# workloadIdentityPools/`pool_id`/attribute.`attribute_name`/`attribute_value``:
|
|
241
|
+
# All identities in a workload identity pool with a certain attribute. * `
|
|
242
|
+
# principalSet://iam.googleapis.com/projects/`project_number`/locations/global/
|
|
243
|
+
# workloadIdentityPools/`pool_id`/*`: All identities in a workload identity pool.
|
|
244
|
+
# * `deleted:user:`emailid`?uid=`uniqueid``: An email address (plus unique
|
|
245
|
+
# identifier) representing a user that has been recently deleted. For example, `
|
|
246
|
+
# alice@example.com?uid=123456789012345678901`. If the user is recovered, this
|
|
247
|
+
# value reverts to `user:`emailid`` and the recovered user retains the role in
|
|
248
|
+
# the binding. * `deleted:serviceAccount:`emailid`?uid=`uniqueid``: An email
|
|
249
|
+
# address (plus unique identifier) representing a service account that has been
|
|
250
|
+
# recently deleted. For example, `my-other-app@appspot.gserviceaccount.com?uid=
|
|
233
251
|
# 123456789012345678901`. If the service account is undeleted, this value
|
|
234
252
|
# reverts to `serviceAccount:`emailid`` and the undeleted service account
|
|
235
253
|
# retains the role in the binding. * `deleted:group:`emailid`?uid=`uniqueid``:
|
|
236
254
|
# An email address (plus unique identifier) representing a Google group that has
|
|
237
255
|
# been recently deleted. For example, `admins@example.com?uid=
|
|
238
256
|
# 123456789012345678901`. If the group is recovered, this value reverts to `
|
|
239
|
-
# group:`emailid`` and the recovered group retains the role in the binding.
|
|
257
|
+
# group:`emailid`` and the recovered group retains the role in the binding. * `
|
|
258
|
+
# deleted:principal://iam.googleapis.com/locations/global/workforcePools/`
|
|
259
|
+
# pool_id`/subject/`subject_attribute_value``: Deleted single identity in a
|
|
260
|
+
# workforce identity pool. For example, `deleted:principal://iam.googleapis.com/
|
|
261
|
+
# locations/global/workforcePools/my-pool-id/subject/my-subject-attribute-value`.
|
|
240
262
|
# Corresponds to the JSON property `members`
|
|
241
263
|
# @return [Array<String>]
|
|
242
264
|
attr_accessor :members
|
|
@@ -16,13 +16,13 @@ module Google
|
|
|
16
16
|
module Apis
|
|
17
17
|
module DeploymentmanagerV2beta
|
|
18
18
|
# Version of the google-apis-deploymentmanager_v2beta gem
|
|
19
|
-
GEM_VERSION = "0.
|
|
19
|
+
GEM_VERSION = "0.27.0"
|
|
20
20
|
|
|
21
21
|
# Version of the code generator used to generate this client
|
|
22
22
|
GENERATOR_VERSION = "0.12.0"
|
|
23
23
|
|
|
24
24
|
# Revision of the discovery document this client was generated from
|
|
25
|
-
REVISION = "
|
|
25
|
+
REVISION = "20231214"
|
|
26
26
|
end
|
|
27
27
|
end
|
|
28
28
|
end
|
|
@@ -157,33 +157,34 @@ module Google
|
|
|
157
157
|
# A filter expression that filters resources listed in the response. Most
|
|
158
158
|
# Compute resources support two types of filter expressions: expressions that
|
|
159
159
|
# support regular expressions and expressions that follow API improvement
|
|
160
|
-
# proposal AIP-160.
|
|
161
|
-
#
|
|
162
|
-
#
|
|
163
|
-
#
|
|
160
|
+
# proposal AIP-160. These two types of filter expressions cannot be mixed in one
|
|
161
|
+
# request. If you want to use AIP-160, your expression must specify the field
|
|
162
|
+
# name, an operator, and the value that you want to use for filtering. The value
|
|
163
|
+
# must be a string, a number, or a boolean. The operator must be either `=`, `!=`
|
|
164
|
+
# , `>`, `<`, `<=`, `>=` or `:`. For example, if you are filtering Compute
|
|
164
165
|
# Engine instances, you can exclude instances named `example-instance` by
|
|
165
|
-
# specifying `name != example-instance`. The
|
|
166
|
-
#
|
|
167
|
-
#
|
|
168
|
-
#
|
|
169
|
-
#
|
|
170
|
-
#
|
|
171
|
-
#
|
|
172
|
-
#
|
|
173
|
-
#
|
|
174
|
-
#
|
|
175
|
-
#
|
|
176
|
-
#
|
|
177
|
-
#
|
|
178
|
-
#
|
|
179
|
-
#
|
|
180
|
-
#
|
|
181
|
-
#
|
|
182
|
-
#
|
|
183
|
-
# literal
|
|
184
|
-
#
|
|
185
|
-
#
|
|
186
|
-
#
|
|
166
|
+
# specifying `name != example-instance`. The `:*` comparison can be used to test
|
|
167
|
+
# whether a key has been defined. For example, to find all objects with `owner`
|
|
168
|
+
# label use: ``` labels.owner:* ``` You can also filter nested fields. For
|
|
169
|
+
# example, you could specify `scheduling.automaticRestart = false` to include
|
|
170
|
+
# instances only if they are not scheduled for automatic restarts. You can use
|
|
171
|
+
# filtering on nested fields to filter based on resource labels. To filter on
|
|
172
|
+
# multiple expressions, provide each separate expression within parentheses. For
|
|
173
|
+
# example: ``` (scheduling.automaticRestart = true) (cpuPlatform = "Intel
|
|
174
|
+
# Skylake") ``` By default, each expression is an `AND` expression. However, you
|
|
175
|
+
# can include `AND` and `OR` expressions explicitly. For example: ``` (
|
|
176
|
+
# cpuPlatform = "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (
|
|
177
|
+
# scheduling.automaticRestart = true) ``` If you want to use a regular
|
|
178
|
+
# expression, use the `eq` (equal) or `ne` (not equal) operator against a single
|
|
179
|
+
# un-parenthesized expression with or without quotes or against multiple
|
|
180
|
+
# parenthesized expressions. Examples: `fieldname eq unquoted literal` `
|
|
181
|
+
# fieldname eq 'single quoted literal'` `fieldname eq "double quoted literal"` `(
|
|
182
|
+
# fieldname1 eq literal) (fieldname2 ne "literal")` The literal value is
|
|
183
|
+
# interpreted as a regular expression using Google RE2 library syntax. The
|
|
184
|
+
# literal value must match the entire field. For example, to filter for
|
|
185
|
+
# instances that do not end with name "instance", you would use `name ne .*
|
|
186
|
+
# instance`. You cannot combine constraints on multiple fields using regular
|
|
187
|
+
# expressions.
|
|
187
188
|
# @param [Fixnum] max_results
|
|
188
189
|
# The maximum number of results per page that should be returned. If the number
|
|
189
190
|
# of available results is larger than `maxResults`, Compute Engine returns a `
|
|
@@ -498,33 +499,34 @@ module Google
|
|
|
498
499
|
# A filter expression that filters resources listed in the response. Most
|
|
499
500
|
# Compute resources support two types of filter expressions: expressions that
|
|
500
501
|
# support regular expressions and expressions that follow API improvement
|
|
501
|
-
# proposal AIP-160.
|
|
502
|
-
#
|
|
503
|
-
#
|
|
504
|
-
#
|
|
502
|
+
# proposal AIP-160. These two types of filter expressions cannot be mixed in one
|
|
503
|
+
# request. If you want to use AIP-160, your expression must specify the field
|
|
504
|
+
# name, an operator, and the value that you want to use for filtering. The value
|
|
505
|
+
# must be a string, a number, or a boolean. The operator must be either `=`, `!=`
|
|
506
|
+
# , `>`, `<`, `<=`, `>=` or `:`. For example, if you are filtering Compute
|
|
505
507
|
# Engine instances, you can exclude instances named `example-instance` by
|
|
506
|
-
# specifying `name != example-instance`. The
|
|
507
|
-
#
|
|
508
|
-
#
|
|
509
|
-
#
|
|
510
|
-
#
|
|
511
|
-
#
|
|
512
|
-
#
|
|
513
|
-
#
|
|
514
|
-
#
|
|
515
|
-
#
|
|
516
|
-
#
|
|
517
|
-
#
|
|
518
|
-
#
|
|
519
|
-
#
|
|
520
|
-
#
|
|
521
|
-
#
|
|
522
|
-
#
|
|
523
|
-
#
|
|
524
|
-
# literal
|
|
525
|
-
#
|
|
526
|
-
#
|
|
527
|
-
#
|
|
508
|
+
# specifying `name != example-instance`. The `:*` comparison can be used to test
|
|
509
|
+
# whether a key has been defined. For example, to find all objects with `owner`
|
|
510
|
+
# label use: ``` labels.owner:* ``` You can also filter nested fields. For
|
|
511
|
+
# example, you could specify `scheduling.automaticRestart = false` to include
|
|
512
|
+
# instances only if they are not scheduled for automatic restarts. You can use
|
|
513
|
+
# filtering on nested fields to filter based on resource labels. To filter on
|
|
514
|
+
# multiple expressions, provide each separate expression within parentheses. For
|
|
515
|
+
# example: ``` (scheduling.automaticRestart = true) (cpuPlatform = "Intel
|
|
516
|
+
# Skylake") ``` By default, each expression is an `AND` expression. However, you
|
|
517
|
+
# can include `AND` and `OR` expressions explicitly. For example: ``` (
|
|
518
|
+
# cpuPlatform = "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (
|
|
519
|
+
# scheduling.automaticRestart = true) ``` If you want to use a regular
|
|
520
|
+
# expression, use the `eq` (equal) or `ne` (not equal) operator against a single
|
|
521
|
+
# un-parenthesized expression with or without quotes or against multiple
|
|
522
|
+
# parenthesized expressions. Examples: `fieldname eq unquoted literal` `
|
|
523
|
+
# fieldname eq 'single quoted literal'` `fieldname eq "double quoted literal"` `(
|
|
524
|
+
# fieldname1 eq literal) (fieldname2 ne "literal")` The literal value is
|
|
525
|
+
# interpreted as a regular expression using Google RE2 library syntax. The
|
|
526
|
+
# literal value must match the entire field. For example, to filter for
|
|
527
|
+
# instances that do not end with name "instance", you would use `name ne .*
|
|
528
|
+
# instance`. You cannot combine constraints on multiple fields using regular
|
|
529
|
+
# expressions.
|
|
528
530
|
# @param [Fixnum] max_results
|
|
529
531
|
# The maximum number of results per page that should be returned. If the number
|
|
530
532
|
# of available results is larger than `maxResults`, Compute Engine returns a `
|
|
@@ -837,33 +839,34 @@ module Google
|
|
|
837
839
|
# A filter expression that filters resources listed in the response. Most
|
|
838
840
|
# Compute resources support two types of filter expressions: expressions that
|
|
839
841
|
# support regular expressions and expressions that follow API improvement
|
|
840
|
-
# proposal AIP-160.
|
|
841
|
-
#
|
|
842
|
-
#
|
|
843
|
-
#
|
|
842
|
+
# proposal AIP-160. These two types of filter expressions cannot be mixed in one
|
|
843
|
+
# request. If you want to use AIP-160, your expression must specify the field
|
|
844
|
+
# name, an operator, and the value that you want to use for filtering. The value
|
|
845
|
+
# must be a string, a number, or a boolean. The operator must be either `=`, `!=`
|
|
846
|
+
# , `>`, `<`, `<=`, `>=` or `:`. For example, if you are filtering Compute
|
|
844
847
|
# Engine instances, you can exclude instances named `example-instance` by
|
|
845
|
-
# specifying `name != example-instance`. The
|
|
846
|
-
#
|
|
847
|
-
#
|
|
848
|
-
#
|
|
849
|
-
#
|
|
850
|
-
#
|
|
851
|
-
#
|
|
852
|
-
#
|
|
853
|
-
#
|
|
854
|
-
#
|
|
855
|
-
#
|
|
856
|
-
#
|
|
857
|
-
#
|
|
858
|
-
#
|
|
859
|
-
#
|
|
860
|
-
#
|
|
861
|
-
#
|
|
862
|
-
#
|
|
863
|
-
# literal
|
|
864
|
-
#
|
|
865
|
-
#
|
|
866
|
-
#
|
|
848
|
+
# specifying `name != example-instance`. The `:*` comparison can be used to test
|
|
849
|
+
# whether a key has been defined. For example, to find all objects with `owner`
|
|
850
|
+
# label use: ``` labels.owner:* ``` You can also filter nested fields. For
|
|
851
|
+
# example, you could specify `scheduling.automaticRestart = false` to include
|
|
852
|
+
# instances only if they are not scheduled for automatic restarts. You can use
|
|
853
|
+
# filtering on nested fields to filter based on resource labels. To filter on
|
|
854
|
+
# multiple expressions, provide each separate expression within parentheses. For
|
|
855
|
+
# example: ``` (scheduling.automaticRestart = true) (cpuPlatform = "Intel
|
|
856
|
+
# Skylake") ``` By default, each expression is an `AND` expression. However, you
|
|
857
|
+
# can include `AND` and `OR` expressions explicitly. For example: ``` (
|
|
858
|
+
# cpuPlatform = "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (
|
|
859
|
+
# scheduling.automaticRestart = true) ``` If you want to use a regular
|
|
860
|
+
# expression, use the `eq` (equal) or `ne` (not equal) operator against a single
|
|
861
|
+
# un-parenthesized expression with or without quotes or against multiple
|
|
862
|
+
# parenthesized expressions. Examples: `fieldname eq unquoted literal` `
|
|
863
|
+
# fieldname eq 'single quoted literal'` `fieldname eq "double quoted literal"` `(
|
|
864
|
+
# fieldname1 eq literal) (fieldname2 ne "literal")` The literal value is
|
|
865
|
+
# interpreted as a regular expression using Google RE2 library syntax. The
|
|
866
|
+
# literal value must match the entire field. For example, to filter for
|
|
867
|
+
# instances that do not end with name "instance", you would use `name ne .*
|
|
868
|
+
# instance`. You cannot combine constraints on multiple fields using regular
|
|
869
|
+
# expressions.
|
|
867
870
|
# @param [Fixnum] max_results
|
|
868
871
|
# The maximum number of results per page that should be returned. If the number
|
|
869
872
|
# of available results is larger than `maxResults`, Compute Engine returns a `
|
|
@@ -952,33 +955,34 @@ module Google
|
|
|
952
955
|
# A filter expression that filters resources listed in the response. Most
|
|
953
956
|
# Compute resources support two types of filter expressions: expressions that
|
|
954
957
|
# support regular expressions and expressions that follow API improvement
|
|
955
|
-
# proposal AIP-160.
|
|
956
|
-
#
|
|
957
|
-
#
|
|
958
|
-
#
|
|
958
|
+
# proposal AIP-160. These two types of filter expressions cannot be mixed in one
|
|
959
|
+
# request. If you want to use AIP-160, your expression must specify the field
|
|
960
|
+
# name, an operator, and the value that you want to use for filtering. The value
|
|
961
|
+
# must be a string, a number, or a boolean. The operator must be either `=`, `!=`
|
|
962
|
+
# , `>`, `<`, `<=`, `>=` or `:`. For example, if you are filtering Compute
|
|
959
963
|
# Engine instances, you can exclude instances named `example-instance` by
|
|
960
|
-
# specifying `name != example-instance`. The
|
|
961
|
-
#
|
|
962
|
-
#
|
|
963
|
-
#
|
|
964
|
-
#
|
|
965
|
-
#
|
|
966
|
-
#
|
|
967
|
-
#
|
|
968
|
-
#
|
|
969
|
-
#
|
|
970
|
-
#
|
|
971
|
-
#
|
|
972
|
-
#
|
|
973
|
-
#
|
|
974
|
-
#
|
|
975
|
-
#
|
|
976
|
-
#
|
|
977
|
-
#
|
|
978
|
-
# literal
|
|
979
|
-
#
|
|
980
|
-
#
|
|
981
|
-
#
|
|
964
|
+
# specifying `name != example-instance`. The `:*` comparison can be used to test
|
|
965
|
+
# whether a key has been defined. For example, to find all objects with `owner`
|
|
966
|
+
# label use: ``` labels.owner:* ``` You can also filter nested fields. For
|
|
967
|
+
# example, you could specify `scheduling.automaticRestart = false` to include
|
|
968
|
+
# instances only if they are not scheduled for automatic restarts. You can use
|
|
969
|
+
# filtering on nested fields to filter based on resource labels. To filter on
|
|
970
|
+
# multiple expressions, provide each separate expression within parentheses. For
|
|
971
|
+
# example: ``` (scheduling.automaticRestart = true) (cpuPlatform = "Intel
|
|
972
|
+
# Skylake") ``` By default, each expression is an `AND` expression. However, you
|
|
973
|
+
# can include `AND` and `OR` expressions explicitly. For example: ``` (
|
|
974
|
+
# cpuPlatform = "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (
|
|
975
|
+
# scheduling.automaticRestart = true) ``` If you want to use a regular
|
|
976
|
+
# expression, use the `eq` (equal) or `ne` (not equal) operator against a single
|
|
977
|
+
# un-parenthesized expression with or without quotes or against multiple
|
|
978
|
+
# parenthesized expressions. Examples: `fieldname eq unquoted literal` `
|
|
979
|
+
# fieldname eq 'single quoted literal'` `fieldname eq "double quoted literal"` `(
|
|
980
|
+
# fieldname1 eq literal) (fieldname2 ne "literal")` The literal value is
|
|
981
|
+
# interpreted as a regular expression using Google RE2 library syntax. The
|
|
982
|
+
# literal value must match the entire field. For example, to filter for
|
|
983
|
+
# instances that do not end with name "instance", you would use `name ne .*
|
|
984
|
+
# instance`. You cannot combine constraints on multiple fields using regular
|
|
985
|
+
# expressions.
|
|
982
986
|
# @param [Fixnum] max_results
|
|
983
987
|
# The maximum number of results per page that should be returned. If the number
|
|
984
988
|
# of available results is larger than `maxResults`, Compute Engine returns a `
|
|
@@ -1071,33 +1075,34 @@ module Google
|
|
|
1071
1075
|
# A filter expression that filters resources listed in the response. Most
|
|
1072
1076
|
# Compute resources support two types of filter expressions: expressions that
|
|
1073
1077
|
# support regular expressions and expressions that follow API improvement
|
|
1074
|
-
# proposal AIP-160.
|
|
1075
|
-
#
|
|
1076
|
-
#
|
|
1077
|
-
#
|
|
1078
|
+
# proposal AIP-160. These two types of filter expressions cannot be mixed in one
|
|
1079
|
+
# request. If you want to use AIP-160, your expression must specify the field
|
|
1080
|
+
# name, an operator, and the value that you want to use for filtering. The value
|
|
1081
|
+
# must be a string, a number, or a boolean. The operator must be either `=`, `!=`
|
|
1082
|
+
# , `>`, `<`, `<=`, `>=` or `:`. For example, if you are filtering Compute
|
|
1078
1083
|
# Engine instances, you can exclude instances named `example-instance` by
|
|
1079
|
-
# specifying `name != example-instance`. The
|
|
1080
|
-
#
|
|
1081
|
-
#
|
|
1082
|
-
#
|
|
1083
|
-
#
|
|
1084
|
-
#
|
|
1085
|
-
#
|
|
1086
|
-
#
|
|
1087
|
-
#
|
|
1088
|
-
#
|
|
1089
|
-
#
|
|
1090
|
-
#
|
|
1091
|
-
#
|
|
1092
|
-
#
|
|
1093
|
-
#
|
|
1094
|
-
#
|
|
1095
|
-
#
|
|
1096
|
-
#
|
|
1097
|
-
# literal
|
|
1098
|
-
#
|
|
1099
|
-
#
|
|
1100
|
-
#
|
|
1084
|
+
# specifying `name != example-instance`. The `:*` comparison can be used to test
|
|
1085
|
+
# whether a key has been defined. For example, to find all objects with `owner`
|
|
1086
|
+
# label use: ``` labels.owner:* ``` You can also filter nested fields. For
|
|
1087
|
+
# example, you could specify `scheduling.automaticRestart = false` to include
|
|
1088
|
+
# instances only if they are not scheduled for automatic restarts. You can use
|
|
1089
|
+
# filtering on nested fields to filter based on resource labels. To filter on
|
|
1090
|
+
# multiple expressions, provide each separate expression within parentheses. For
|
|
1091
|
+
# example: ``` (scheduling.automaticRestart = true) (cpuPlatform = "Intel
|
|
1092
|
+
# Skylake") ``` By default, each expression is an `AND` expression. However, you
|
|
1093
|
+
# can include `AND` and `OR` expressions explicitly. For example: ``` (
|
|
1094
|
+
# cpuPlatform = "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (
|
|
1095
|
+
# scheduling.automaticRestart = true) ``` If you want to use a regular
|
|
1096
|
+
# expression, use the `eq` (equal) or `ne` (not equal) operator against a single
|
|
1097
|
+
# un-parenthesized expression with or without quotes or against multiple
|
|
1098
|
+
# parenthesized expressions. Examples: `fieldname eq unquoted literal` `
|
|
1099
|
+
# fieldname eq 'single quoted literal'` `fieldname eq "double quoted literal"` `(
|
|
1100
|
+
# fieldname1 eq literal) (fieldname2 ne "literal")` The literal value is
|
|
1101
|
+
# interpreted as a regular expression using Google RE2 library syntax. The
|
|
1102
|
+
# literal value must match the entire field. For example, to filter for
|
|
1103
|
+
# instances that do not end with name "instance", you would use `name ne .*
|
|
1104
|
+
# instance`. You cannot combine constraints on multiple fields using regular
|
|
1105
|
+
# expressions.
|
|
1101
1106
|
# @param [Fixnum] max_results
|
|
1102
1107
|
# The maximum number of results per page that should be returned. If the number
|
|
1103
1108
|
# of available results is larger than `maxResults`, Compute Engine returns a `
|
|
@@ -1288,33 +1293,34 @@ module Google
|
|
|
1288
1293
|
# A filter expression that filters resources listed in the response. Most
|
|
1289
1294
|
# Compute resources support two types of filter expressions: expressions that
|
|
1290
1295
|
# support regular expressions and expressions that follow API improvement
|
|
1291
|
-
# proposal AIP-160.
|
|
1292
|
-
#
|
|
1293
|
-
#
|
|
1294
|
-
#
|
|
1296
|
+
# proposal AIP-160. These two types of filter expressions cannot be mixed in one
|
|
1297
|
+
# request. If you want to use AIP-160, your expression must specify the field
|
|
1298
|
+
# name, an operator, and the value that you want to use for filtering. The value
|
|
1299
|
+
# must be a string, a number, or a boolean. The operator must be either `=`, `!=`
|
|
1300
|
+
# , `>`, `<`, `<=`, `>=` or `:`. For example, if you are filtering Compute
|
|
1295
1301
|
# Engine instances, you can exclude instances named `example-instance` by
|
|
1296
|
-
# specifying `name != example-instance`. The
|
|
1297
|
-
#
|
|
1298
|
-
#
|
|
1299
|
-
#
|
|
1300
|
-
#
|
|
1301
|
-
#
|
|
1302
|
-
#
|
|
1303
|
-
#
|
|
1304
|
-
#
|
|
1305
|
-
#
|
|
1306
|
-
#
|
|
1307
|
-
#
|
|
1308
|
-
#
|
|
1309
|
-
#
|
|
1310
|
-
#
|
|
1311
|
-
#
|
|
1312
|
-
#
|
|
1313
|
-
#
|
|
1314
|
-
# literal
|
|
1315
|
-
#
|
|
1316
|
-
#
|
|
1317
|
-
#
|
|
1302
|
+
# specifying `name != example-instance`. The `:*` comparison can be used to test
|
|
1303
|
+
# whether a key has been defined. For example, to find all objects with `owner`
|
|
1304
|
+
# label use: ``` labels.owner:* ``` You can also filter nested fields. For
|
|
1305
|
+
# example, you could specify `scheduling.automaticRestart = false` to include
|
|
1306
|
+
# instances only if they are not scheduled for automatic restarts. You can use
|
|
1307
|
+
# filtering on nested fields to filter based on resource labels. To filter on
|
|
1308
|
+
# multiple expressions, provide each separate expression within parentheses. For
|
|
1309
|
+
# example: ``` (scheduling.automaticRestart = true) (cpuPlatform = "Intel
|
|
1310
|
+
# Skylake") ``` By default, each expression is an `AND` expression. However, you
|
|
1311
|
+
# can include `AND` and `OR` expressions explicitly. For example: ``` (
|
|
1312
|
+
# cpuPlatform = "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (
|
|
1313
|
+
# scheduling.automaticRestart = true) ``` If you want to use a regular
|
|
1314
|
+
# expression, use the `eq` (equal) or `ne` (not equal) operator against a single
|
|
1315
|
+
# un-parenthesized expression with or without quotes or against multiple
|
|
1316
|
+
# parenthesized expressions. Examples: `fieldname eq unquoted literal` `
|
|
1317
|
+
# fieldname eq 'single quoted literal'` `fieldname eq "double quoted literal"` `(
|
|
1318
|
+
# fieldname1 eq literal) (fieldname2 ne "literal")` The literal value is
|
|
1319
|
+
# interpreted as a regular expression using Google RE2 library syntax. The
|
|
1320
|
+
# literal value must match the entire field. For example, to filter for
|
|
1321
|
+
# instances that do not end with name "instance", you would use `name ne .*
|
|
1322
|
+
# instance`. You cannot combine constraints on multiple fields using regular
|
|
1323
|
+
# expressions.
|
|
1318
1324
|
# @param [Fixnum] max_results
|
|
1319
1325
|
# The maximum number of results per page that should be returned. If the number
|
|
1320
1326
|
# of available results is larger than `maxResults`, Compute Engine returns a `
|
|
@@ -1371,33 +1377,34 @@ module Google
|
|
|
1371
1377
|
# A filter expression that filters resources listed in the response. Most
|
|
1372
1378
|
# Compute resources support two types of filter expressions: expressions that
|
|
1373
1379
|
# support regular expressions and expressions that follow API improvement
|
|
1374
|
-
# proposal AIP-160.
|
|
1375
|
-
#
|
|
1376
|
-
#
|
|
1377
|
-
#
|
|
1380
|
+
# proposal AIP-160. These two types of filter expressions cannot be mixed in one
|
|
1381
|
+
# request. If you want to use AIP-160, your expression must specify the field
|
|
1382
|
+
# name, an operator, and the value that you want to use for filtering. The value
|
|
1383
|
+
# must be a string, a number, or a boolean. The operator must be either `=`, `!=`
|
|
1384
|
+
# , `>`, `<`, `<=`, `>=` or `:`. For example, if you are filtering Compute
|
|
1378
1385
|
# Engine instances, you can exclude instances named `example-instance` by
|
|
1379
|
-
# specifying `name != example-instance`. The
|
|
1380
|
-
#
|
|
1381
|
-
#
|
|
1382
|
-
#
|
|
1383
|
-
#
|
|
1384
|
-
#
|
|
1385
|
-
#
|
|
1386
|
-
#
|
|
1387
|
-
#
|
|
1388
|
-
#
|
|
1389
|
-
#
|
|
1390
|
-
#
|
|
1391
|
-
#
|
|
1392
|
-
#
|
|
1393
|
-
#
|
|
1394
|
-
#
|
|
1395
|
-
#
|
|
1396
|
-
#
|
|
1397
|
-
# literal
|
|
1398
|
-
#
|
|
1399
|
-
#
|
|
1400
|
-
#
|
|
1386
|
+
# specifying `name != example-instance`. The `:*` comparison can be used to test
|
|
1387
|
+
# whether a key has been defined. For example, to find all objects with `owner`
|
|
1388
|
+
# label use: ``` labels.owner:* ``` You can also filter nested fields. For
|
|
1389
|
+
# example, you could specify `scheduling.automaticRestart = false` to include
|
|
1390
|
+
# instances only if they are not scheduled for automatic restarts. You can use
|
|
1391
|
+
# filtering on nested fields to filter based on resource labels. To filter on
|
|
1392
|
+
# multiple expressions, provide each separate expression within parentheses. For
|
|
1393
|
+
# example: ``` (scheduling.automaticRestart = true) (cpuPlatform = "Intel
|
|
1394
|
+
# Skylake") ``` By default, each expression is an `AND` expression. However, you
|
|
1395
|
+
# can include `AND` and `OR` expressions explicitly. For example: ``` (
|
|
1396
|
+
# cpuPlatform = "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (
|
|
1397
|
+
# scheduling.automaticRestart = true) ``` If you want to use a regular
|
|
1398
|
+
# expression, use the `eq` (equal) or `ne` (not equal) operator against a single
|
|
1399
|
+
# un-parenthesized expression with or without quotes or against multiple
|
|
1400
|
+
# parenthesized expressions. Examples: `fieldname eq unquoted literal` `
|
|
1401
|
+
# fieldname eq 'single quoted literal'` `fieldname eq "double quoted literal"` `(
|
|
1402
|
+
# fieldname1 eq literal) (fieldname2 ne "literal")` The literal value is
|
|
1403
|
+
# interpreted as a regular expression using Google RE2 library syntax. The
|
|
1404
|
+
# literal value must match the entire field. For example, to filter for
|
|
1405
|
+
# instances that do not end with name "instance", you would use `name ne .*
|
|
1406
|
+
# instance`. You cannot combine constraints on multiple fields using regular
|
|
1407
|
+
# expressions.
|
|
1401
1408
|
# @param [Fixnum] max_results
|
|
1402
1409
|
# The maximum number of results per page that should be returned. If the number
|
|
1403
1410
|
# of available results is larger than `maxResults`, Compute Engine returns a `
|
|
@@ -1525,33 +1532,34 @@ module Google
|
|
|
1525
1532
|
# A filter expression that filters resources listed in the response. Most
|
|
1526
1533
|
# Compute resources support two types of filter expressions: expressions that
|
|
1527
1534
|
# support regular expressions and expressions that follow API improvement
|
|
1528
|
-
# proposal AIP-160.
|
|
1529
|
-
#
|
|
1530
|
-
#
|
|
1531
|
-
#
|
|
1535
|
+
# proposal AIP-160. These two types of filter expressions cannot be mixed in one
|
|
1536
|
+
# request. If you want to use AIP-160, your expression must specify the field
|
|
1537
|
+
# name, an operator, and the value that you want to use for filtering. The value
|
|
1538
|
+
# must be a string, a number, or a boolean. The operator must be either `=`, `!=`
|
|
1539
|
+
# , `>`, `<`, `<=`, `>=` or `:`. For example, if you are filtering Compute
|
|
1532
1540
|
# Engine instances, you can exclude instances named `example-instance` by
|
|
1533
|
-
# specifying `name != example-instance`. The
|
|
1534
|
-
#
|
|
1535
|
-
#
|
|
1536
|
-
#
|
|
1537
|
-
#
|
|
1538
|
-
#
|
|
1539
|
-
#
|
|
1540
|
-
#
|
|
1541
|
-
#
|
|
1542
|
-
#
|
|
1543
|
-
#
|
|
1544
|
-
#
|
|
1545
|
-
#
|
|
1546
|
-
#
|
|
1547
|
-
#
|
|
1548
|
-
#
|
|
1549
|
-
#
|
|
1550
|
-
#
|
|
1551
|
-
# literal
|
|
1552
|
-
#
|
|
1553
|
-
#
|
|
1554
|
-
#
|
|
1541
|
+
# specifying `name != example-instance`. The `:*` comparison can be used to test
|
|
1542
|
+
# whether a key has been defined. For example, to find all objects with `owner`
|
|
1543
|
+
# label use: ``` labels.owner:* ``` You can also filter nested fields. For
|
|
1544
|
+
# example, you could specify `scheduling.automaticRestart = false` to include
|
|
1545
|
+
# instances only if they are not scheduled for automatic restarts. You can use
|
|
1546
|
+
# filtering on nested fields to filter based on resource labels. To filter on
|
|
1547
|
+
# multiple expressions, provide each separate expression within parentheses. For
|
|
1548
|
+
# example: ``` (scheduling.automaticRestart = true) (cpuPlatform = "Intel
|
|
1549
|
+
# Skylake") ``` By default, each expression is an `AND` expression. However, you
|
|
1550
|
+
# can include `AND` and `OR` expressions explicitly. For example: ``` (
|
|
1551
|
+
# cpuPlatform = "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (
|
|
1552
|
+
# scheduling.automaticRestart = true) ``` If you want to use a regular
|
|
1553
|
+
# expression, use the `eq` (equal) or `ne` (not equal) operator against a single
|
|
1554
|
+
# un-parenthesized expression with or without quotes or against multiple
|
|
1555
|
+
# parenthesized expressions. Examples: `fieldname eq unquoted literal` `
|
|
1556
|
+
# fieldname eq 'single quoted literal'` `fieldname eq "double quoted literal"` `(
|
|
1557
|
+
# fieldname1 eq literal) (fieldname2 ne "literal")` The literal value is
|
|
1558
|
+
# interpreted as a regular expression using Google RE2 library syntax. The
|
|
1559
|
+
# literal value must match the entire field. For example, to filter for
|
|
1560
|
+
# instances that do not end with name "instance", you would use `name ne .*
|
|
1561
|
+
# instance`. You cannot combine constraints on multiple fields using regular
|
|
1562
|
+
# expressions.
|
|
1555
1563
|
# @param [Fixnum] max_results
|
|
1556
1564
|
# The maximum number of results per page that should be returned. If the number
|
|
1557
1565
|
# of available results is larger than `maxResults`, Compute Engine returns a `
|
metadata
CHANGED
|
@@ -1,14 +1,14 @@
|
|
|
1
1
|
--- !ruby/object:Gem::Specification
|
|
2
2
|
name: google-apis-deploymentmanager_v2beta
|
|
3
3
|
version: !ruby/object:Gem::Version
|
|
4
|
-
version: 0.
|
|
4
|
+
version: 0.27.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: 2023-
|
|
11
|
+
date: 2023-12-24 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-deploymentmanager_v2beta/CHANGELOG.md
|
|
61
|
-
documentation_uri: https://googleapis.dev/ruby/google-apis-deploymentmanager_v2beta/v0.
|
|
61
|
+
documentation_uri: https://googleapis.dev/ruby/google-apis-deploymentmanager_v2beta/v0.27.0
|
|
62
62
|
source_code_uri: https://github.com/googleapis/google-api-ruby-client/tree/main/generated/google-apis-deploymentmanager_v2beta
|
|
63
63
|
post_install_message:
|
|
64
64
|
rdoc_options: []
|