google-apis-deploymentmanager_v2beta 0.14.0 → 0.17.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: 39319aeb9867ed354a73b232bf3c0d858daabf491ec5b601a1c8ef132ec2efe8
|
4
|
+
data.tar.gz: a6e99eb71a705921b059ce542e8dd8609f519e10917b0d219e51532eb8155c1b
|
5
5
|
SHA512:
|
6
|
-
metadata.gz:
|
7
|
-
data.tar.gz:
|
6
|
+
metadata.gz: 2f574e7259a37249b92777cd3bffd0e67598b4d23219bc26e824a06a38e99f1ef24e4c4c3f97602f6b317339edea4c993ae5ebc0e7ebbecde870279974eea756
|
7
|
+
data.tar.gz: 1a123d2a6e66ab03af193582f8dd22707cc28c66e57cc6bdf4b312170db559deb5b0a0ab929819f74ebab9cadafe8166360a3c74f0815f11a43700b2bb51b944
|
data/CHANGELOG.md
CHANGED
@@ -1,5 +1,17 @@
|
|
1
1
|
# Release history for google-apis-deploymentmanager_v2beta
|
2
2
|
|
3
|
+
### v0.17.0 (2022-06-07)
|
4
|
+
|
5
|
+
* Regenerated using generator version 0.5.0
|
6
|
+
|
7
|
+
### v0.16.0 (2022-05-27)
|
8
|
+
|
9
|
+
* Regenerated from discovery document revision 20220520
|
10
|
+
|
11
|
+
### v0.15.0 (2022-05-05)
|
12
|
+
|
13
|
+
* Regenerated from discovery document revision 20220429
|
14
|
+
|
3
15
|
### v0.14.0 (2022-04-14)
|
4
16
|
|
5
17
|
* Regenerated from discovery document revision 20220407
|
@@ -62,8 +62,8 @@ module Google
|
|
62
62
|
# "audit_log_configs": [ ` "log_type": "DATA_READ" `, ` "log_type": "DATA_WRITE"
|
63
63
|
# , "exempted_members": [ "user:aliya@example.com" ] ` ] ` ] ` For sampleservice,
|
64
64
|
# this policy enables DATA_READ, DATA_WRITE and ADMIN_READ logging. It also
|
65
|
-
# exempts jose@example.com from DATA_READ logging, and aliya@example.com
|
66
|
-
# DATA_WRITE logging.
|
65
|
+
# exempts `jose@example.com` from DATA_READ logging, and `aliya@example.com`
|
66
|
+
# from DATA_WRITE logging.
|
67
67
|
class AuditConfig
|
68
68
|
include Google::Apis::Core::Hashable
|
69
69
|
|
@@ -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.17.0"
|
20
20
|
|
21
21
|
# Version of the code generator used to generate this client
|
22
|
-
GENERATOR_VERSION = "0.
|
22
|
+
GENERATOR_VERSION = "0.5.0"
|
23
23
|
|
24
24
|
# Revision of the discovery document this client was generated from
|
25
|
-
REVISION = "
|
25
|
+
REVISION = "20220520"
|
26
26
|
end
|
27
27
|
end
|
28
28
|
end
|
@@ -154,25 +154,36 @@ module Google
|
|
154
154
|
# @param [String] project
|
155
155
|
# The project ID for this request.
|
156
156
|
# @param [String] filter
|
157
|
-
# A filter expression that filters resources listed in the response.
|
158
|
-
#
|
159
|
-
#
|
160
|
-
#
|
161
|
-
#
|
162
|
-
#
|
163
|
-
#
|
164
|
-
#
|
165
|
-
#
|
166
|
-
#
|
167
|
-
#
|
168
|
-
#
|
169
|
-
# You can
|
170
|
-
#
|
171
|
-
#
|
172
|
-
#
|
173
|
-
#
|
174
|
-
#
|
175
|
-
#
|
157
|
+
# A filter expression that filters resources listed in the response. Most
|
158
|
+
# Compute resources support two types of filter expressions: expressions that
|
159
|
+
# support regular expressions and expressions that follow API improvement
|
160
|
+
# proposal AIP-160. If you want to use AIP-160, your expression must specify the
|
161
|
+
# field name, an operator, and the value that you want to use for filtering. The
|
162
|
+
# value must be a string, a number, or a boolean. The operator must be either `=`
|
163
|
+
# , `!=`, `>`, `<`, `<=`, `>=` or `:`. For example, if you are filtering Compute
|
164
|
+
# Engine instances, you can exclude instances named `example-instance` by
|
165
|
+
# specifying `name != example-instance`. The `:` operator can be used with
|
166
|
+
# string fields to match substrings. For non-string fields it is equivalent to
|
167
|
+
# the `=` operator. The `:*` comparison can be used to test whether a key has
|
168
|
+
# been defined. For example, to find all objects with `owner` label use: ```
|
169
|
+
# labels.owner:* ``` You can also filter nested fields. For example, you could
|
170
|
+
# specify `scheduling.automaticRestart = false` to include instances only if
|
171
|
+
# they are not scheduled for automatic restarts. You can use filtering on nested
|
172
|
+
# fields to filter based on resource labels. To filter on multiple expressions,
|
173
|
+
# provide each separate expression within parentheses. For example: ``` (
|
174
|
+
# scheduling.automaticRestart = true) (cpuPlatform = "Intel Skylake") ``` By
|
175
|
+
# default, each expression is an `AND` expression. However, you can include `AND`
|
176
|
+
# and `OR` expressions explicitly. For example: ``` (cpuPlatform = "Intel
|
177
|
+
# Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.
|
178
|
+
# automaticRestart = true) ``` If you want to use a regular expression, use the `
|
179
|
+
# eq` (equal) or `ne` (not equal) operator against a single un-parenthesized
|
180
|
+
# expression with or without quotes or against multiple parenthesized
|
181
|
+
# expressions. Examples: `fieldname eq unquoted literal` `fieldname eq 'single
|
182
|
+
# quoted literal'` `fieldname eq "double quoted literal"` `(fieldname1 eq
|
183
|
+
# literal) (fieldname2 ne "literal")` The literal value is interpreted as a
|
184
|
+
# regular expression using Google RE2 library syntax. The literal value must
|
185
|
+
# match the entire field. For example, to filter for instances that do not end
|
186
|
+
# with name "instance", you would use `name ne .*instance`.
|
176
187
|
# @param [Fixnum] max_results
|
177
188
|
# The maximum number of results per page that should be returned. If the number
|
178
189
|
# of available results is larger than `maxResults`, Compute Engine returns a `
|
@@ -484,25 +495,36 @@ module Google
|
|
484
495
|
# @param [String] project
|
485
496
|
# The project ID for this request.
|
486
497
|
# @param [String] filter
|
487
|
-
# A filter expression that filters resources listed in the response.
|
488
|
-
#
|
489
|
-
#
|
490
|
-
#
|
491
|
-
#
|
492
|
-
#
|
493
|
-
#
|
494
|
-
#
|
495
|
-
#
|
496
|
-
#
|
497
|
-
#
|
498
|
-
#
|
499
|
-
# You can
|
500
|
-
#
|
501
|
-
#
|
502
|
-
#
|
503
|
-
#
|
504
|
-
#
|
505
|
-
#
|
498
|
+
# A filter expression that filters resources listed in the response. Most
|
499
|
+
# Compute resources support two types of filter expressions: expressions that
|
500
|
+
# support regular expressions and expressions that follow API improvement
|
501
|
+
# proposal AIP-160. If you want to use AIP-160, your expression must specify the
|
502
|
+
# field name, an operator, and the value that you want to use for filtering. The
|
503
|
+
# value must be a string, a number, or a boolean. The operator must be either `=`
|
504
|
+
# , `!=`, `>`, `<`, `<=`, `>=` or `:`. For example, if you are filtering Compute
|
505
|
+
# Engine instances, you can exclude instances named `example-instance` by
|
506
|
+
# specifying `name != example-instance`. The `:` operator can be used with
|
507
|
+
# string fields to match substrings. For non-string fields it is equivalent to
|
508
|
+
# the `=` operator. The `:*` comparison can be used to test whether a key has
|
509
|
+
# been defined. For example, to find all objects with `owner` label use: ```
|
510
|
+
# labels.owner:* ``` You can also filter nested fields. For example, you could
|
511
|
+
# specify `scheduling.automaticRestart = false` to include instances only if
|
512
|
+
# they are not scheduled for automatic restarts. You can use filtering on nested
|
513
|
+
# fields to filter based on resource labels. To filter on multiple expressions,
|
514
|
+
# provide each separate expression within parentheses. For example: ``` (
|
515
|
+
# scheduling.automaticRestart = true) (cpuPlatform = "Intel Skylake") ``` By
|
516
|
+
# default, each expression is an `AND` expression. However, you can include `AND`
|
517
|
+
# and `OR` expressions explicitly. For example: ``` (cpuPlatform = "Intel
|
518
|
+
# Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.
|
519
|
+
# automaticRestart = true) ``` If you want to use a regular expression, use the `
|
520
|
+
# eq` (equal) or `ne` (not equal) operator against a single un-parenthesized
|
521
|
+
# expression with or without quotes or against multiple parenthesized
|
522
|
+
# expressions. Examples: `fieldname eq unquoted literal` `fieldname eq 'single
|
523
|
+
# quoted literal'` `fieldname eq "double quoted literal"` `(fieldname1 eq
|
524
|
+
# literal) (fieldname2 ne "literal")` The literal value is interpreted as a
|
525
|
+
# regular expression using Google RE2 library syntax. The literal value must
|
526
|
+
# match the entire field. For example, to filter for instances that do not end
|
527
|
+
# with name "instance", you would use `name ne .*instance`.
|
506
528
|
# @param [Fixnum] max_results
|
507
529
|
# The maximum number of results per page that should be returned. If the number
|
508
530
|
# of available results is larger than `maxResults`, Compute Engine returns a `
|
@@ -812,25 +834,36 @@ module Google
|
|
812
834
|
# @param [String] deployment
|
813
835
|
# The name of the deployment for this request.
|
814
836
|
# @param [String] filter
|
815
|
-
# A filter expression that filters resources listed in the response.
|
816
|
-
#
|
817
|
-
#
|
818
|
-
#
|
819
|
-
#
|
820
|
-
#
|
821
|
-
#
|
822
|
-
#
|
823
|
-
#
|
824
|
-
#
|
825
|
-
#
|
826
|
-
#
|
827
|
-
# You can
|
828
|
-
#
|
829
|
-
#
|
830
|
-
#
|
831
|
-
#
|
832
|
-
#
|
833
|
-
#
|
837
|
+
# A filter expression that filters resources listed in the response. Most
|
838
|
+
# Compute resources support two types of filter expressions: expressions that
|
839
|
+
# support regular expressions and expressions that follow API improvement
|
840
|
+
# proposal AIP-160. If you want to use AIP-160, your expression must specify the
|
841
|
+
# field name, an operator, and the value that you want to use for filtering. The
|
842
|
+
# value must be a string, a number, or a boolean. The operator must be either `=`
|
843
|
+
# , `!=`, `>`, `<`, `<=`, `>=` or `:`. For example, if you are filtering Compute
|
844
|
+
# Engine instances, you can exclude instances named `example-instance` by
|
845
|
+
# specifying `name != example-instance`. The `:` operator can be used with
|
846
|
+
# string fields to match substrings. For non-string fields it is equivalent to
|
847
|
+
# the `=` operator. The `:*` comparison can be used to test whether a key has
|
848
|
+
# been defined. For example, to find all objects with `owner` label use: ```
|
849
|
+
# labels.owner:* ``` You can also filter nested fields. For example, you could
|
850
|
+
# specify `scheduling.automaticRestart = false` to include instances only if
|
851
|
+
# they are not scheduled for automatic restarts. You can use filtering on nested
|
852
|
+
# fields to filter based on resource labels. To filter on multiple expressions,
|
853
|
+
# provide each separate expression within parentheses. For example: ``` (
|
854
|
+
# scheduling.automaticRestart = true) (cpuPlatform = "Intel Skylake") ``` By
|
855
|
+
# default, each expression is an `AND` expression. However, you can include `AND`
|
856
|
+
# and `OR` expressions explicitly. For example: ``` (cpuPlatform = "Intel
|
857
|
+
# Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.
|
858
|
+
# automaticRestart = true) ``` If you want to use a regular expression, use the `
|
859
|
+
# eq` (equal) or `ne` (not equal) operator against a single un-parenthesized
|
860
|
+
# expression with or without quotes or against multiple parenthesized
|
861
|
+
# expressions. Examples: `fieldname eq unquoted literal` `fieldname eq 'single
|
862
|
+
# quoted literal'` `fieldname eq "double quoted literal"` `(fieldname1 eq
|
863
|
+
# literal) (fieldname2 ne "literal")` The literal value is interpreted as a
|
864
|
+
# regular expression using Google RE2 library syntax. The literal value must
|
865
|
+
# match the entire field. For example, to filter for instances that do not end
|
866
|
+
# with name "instance", you would use `name ne .*instance`.
|
834
867
|
# @param [Fixnum] max_results
|
835
868
|
# The maximum number of results per page that should be returned. If the number
|
836
869
|
# of available results is larger than `maxResults`, Compute Engine returns a `
|
@@ -916,25 +949,36 @@ module Google
|
|
916
949
|
# @param [String] project
|
917
950
|
# The project ID for this request.
|
918
951
|
# @param [String] filter
|
919
|
-
# A filter expression that filters resources listed in the response.
|
920
|
-
#
|
921
|
-
#
|
922
|
-
#
|
923
|
-
#
|
924
|
-
#
|
925
|
-
#
|
926
|
-
#
|
927
|
-
#
|
928
|
-
#
|
929
|
-
#
|
930
|
-
#
|
931
|
-
# You can
|
932
|
-
#
|
933
|
-
#
|
934
|
-
#
|
935
|
-
#
|
936
|
-
#
|
937
|
-
#
|
952
|
+
# A filter expression that filters resources listed in the response. Most
|
953
|
+
# Compute resources support two types of filter expressions: expressions that
|
954
|
+
# support regular expressions and expressions that follow API improvement
|
955
|
+
# proposal AIP-160. If you want to use AIP-160, your expression must specify the
|
956
|
+
# field name, an operator, and the value that you want to use for filtering. The
|
957
|
+
# value must be a string, a number, or a boolean. The operator must be either `=`
|
958
|
+
# , `!=`, `>`, `<`, `<=`, `>=` or `:`. For example, if you are filtering Compute
|
959
|
+
# Engine instances, you can exclude instances named `example-instance` by
|
960
|
+
# specifying `name != example-instance`. The `:` operator can be used with
|
961
|
+
# string fields to match substrings. For non-string fields it is equivalent to
|
962
|
+
# the `=` operator. The `:*` comparison can be used to test whether a key has
|
963
|
+
# been defined. For example, to find all objects with `owner` label use: ```
|
964
|
+
# labels.owner:* ``` You can also filter nested fields. For example, you could
|
965
|
+
# specify `scheduling.automaticRestart = false` to include instances only if
|
966
|
+
# they are not scheduled for automatic restarts. You can use filtering on nested
|
967
|
+
# fields to filter based on resource labels. To filter on multiple expressions,
|
968
|
+
# provide each separate expression within parentheses. For example: ``` (
|
969
|
+
# scheduling.automaticRestart = true) (cpuPlatform = "Intel Skylake") ``` By
|
970
|
+
# default, each expression is an `AND` expression. However, you can include `AND`
|
971
|
+
# and `OR` expressions explicitly. For example: ``` (cpuPlatform = "Intel
|
972
|
+
# Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.
|
973
|
+
# automaticRestart = true) ``` If you want to use a regular expression, use the `
|
974
|
+
# eq` (equal) or `ne` (not equal) operator against a single un-parenthesized
|
975
|
+
# expression with or without quotes or against multiple parenthesized
|
976
|
+
# expressions. Examples: `fieldname eq unquoted literal` `fieldname eq 'single
|
977
|
+
# quoted literal'` `fieldname eq "double quoted literal"` `(fieldname1 eq
|
978
|
+
# literal) (fieldname2 ne "literal")` The literal value is interpreted as a
|
979
|
+
# regular expression using Google RE2 library syntax. The literal value must
|
980
|
+
# match the entire field. For example, to filter for instances that do not end
|
981
|
+
# with name "instance", you would use `name ne .*instance`.
|
938
982
|
# @param [Fixnum] max_results
|
939
983
|
# The maximum number of results per page that should be returned. If the number
|
940
984
|
# of available results is larger than `maxResults`, Compute Engine returns a `
|
@@ -1024,25 +1068,36 @@ module Google
|
|
1024
1068
|
# @param [String] deployment
|
1025
1069
|
# The name of the deployment for this request.
|
1026
1070
|
# @param [String] filter
|
1027
|
-
# A filter expression that filters resources listed in the response.
|
1028
|
-
#
|
1029
|
-
#
|
1030
|
-
#
|
1031
|
-
#
|
1032
|
-
#
|
1033
|
-
#
|
1034
|
-
#
|
1035
|
-
#
|
1036
|
-
#
|
1037
|
-
#
|
1038
|
-
#
|
1039
|
-
# You can
|
1040
|
-
#
|
1041
|
-
#
|
1042
|
-
#
|
1043
|
-
#
|
1044
|
-
#
|
1045
|
-
#
|
1071
|
+
# A filter expression that filters resources listed in the response. Most
|
1072
|
+
# Compute resources support two types of filter expressions: expressions that
|
1073
|
+
# support regular expressions and expressions that follow API improvement
|
1074
|
+
# proposal AIP-160. If you want to use AIP-160, your expression must specify the
|
1075
|
+
# field name, an operator, and the value that you want to use for filtering. The
|
1076
|
+
# value must be a string, a number, or a boolean. The operator must be either `=`
|
1077
|
+
# , `!=`, `>`, `<`, `<=`, `>=` or `:`. For example, if you are filtering Compute
|
1078
|
+
# Engine instances, you can exclude instances named `example-instance` by
|
1079
|
+
# specifying `name != example-instance`. The `:` operator can be used with
|
1080
|
+
# string fields to match substrings. For non-string fields it is equivalent to
|
1081
|
+
# the `=` operator. The `:*` comparison can be used to test whether a key has
|
1082
|
+
# been defined. For example, to find all objects with `owner` label use: ```
|
1083
|
+
# labels.owner:* ``` You can also filter nested fields. For example, you could
|
1084
|
+
# specify `scheduling.automaticRestart = false` to include instances only if
|
1085
|
+
# they are not scheduled for automatic restarts. You can use filtering on nested
|
1086
|
+
# fields to filter based on resource labels. To filter on multiple expressions,
|
1087
|
+
# provide each separate expression within parentheses. For example: ``` (
|
1088
|
+
# scheduling.automaticRestart = true) (cpuPlatform = "Intel Skylake") ``` By
|
1089
|
+
# default, each expression is an `AND` expression. However, you can include `AND`
|
1090
|
+
# and `OR` expressions explicitly. For example: ``` (cpuPlatform = "Intel
|
1091
|
+
# Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.
|
1092
|
+
# automaticRestart = true) ``` If you want to use a regular expression, use the `
|
1093
|
+
# eq` (equal) or `ne` (not equal) operator against a single un-parenthesized
|
1094
|
+
# expression with or without quotes or against multiple parenthesized
|
1095
|
+
# expressions. Examples: `fieldname eq unquoted literal` `fieldname eq 'single
|
1096
|
+
# quoted literal'` `fieldname eq "double quoted literal"` `(fieldname1 eq
|
1097
|
+
# literal) (fieldname2 ne "literal")` The literal value is interpreted as a
|
1098
|
+
# regular expression using Google RE2 library syntax. The literal value must
|
1099
|
+
# match the entire field. For example, to filter for instances that do not end
|
1100
|
+
# with name "instance", you would use `name ne .*instance`.
|
1046
1101
|
# @param [Fixnum] max_results
|
1047
1102
|
# The maximum number of results per page that should be returned. If the number
|
1048
1103
|
# of available results is larger than `maxResults`, Compute Engine returns a `
|
@@ -1230,25 +1285,36 @@ module Google
|
|
1230
1285
|
# @param [String] project
|
1231
1286
|
# The project ID for this request.
|
1232
1287
|
# @param [String] filter
|
1233
|
-
# A filter expression that filters resources listed in the response.
|
1234
|
-
#
|
1235
|
-
#
|
1236
|
-
#
|
1237
|
-
#
|
1238
|
-
#
|
1239
|
-
#
|
1240
|
-
#
|
1241
|
-
#
|
1242
|
-
#
|
1243
|
-
#
|
1244
|
-
#
|
1245
|
-
# You can
|
1246
|
-
#
|
1247
|
-
#
|
1248
|
-
#
|
1249
|
-
#
|
1250
|
-
#
|
1251
|
-
#
|
1288
|
+
# A filter expression that filters resources listed in the response. Most
|
1289
|
+
# Compute resources support two types of filter expressions: expressions that
|
1290
|
+
# support regular expressions and expressions that follow API improvement
|
1291
|
+
# proposal AIP-160. If you want to use AIP-160, your expression must specify the
|
1292
|
+
# field name, an operator, and the value that you want to use for filtering. The
|
1293
|
+
# value must be a string, a number, or a boolean. The operator must be either `=`
|
1294
|
+
# , `!=`, `>`, `<`, `<=`, `>=` or `:`. For example, if you are filtering Compute
|
1295
|
+
# Engine instances, you can exclude instances named `example-instance` by
|
1296
|
+
# specifying `name != example-instance`. The `:` operator can be used with
|
1297
|
+
# string fields to match substrings. For non-string fields it is equivalent to
|
1298
|
+
# the `=` operator. The `:*` comparison can be used to test whether a key has
|
1299
|
+
# been defined. For example, to find all objects with `owner` label use: ```
|
1300
|
+
# labels.owner:* ``` You can also filter nested fields. For example, you could
|
1301
|
+
# specify `scheduling.automaticRestart = false` to include instances only if
|
1302
|
+
# they are not scheduled for automatic restarts. You can use filtering on nested
|
1303
|
+
# fields to filter based on resource labels. To filter on multiple expressions,
|
1304
|
+
# provide each separate expression within parentheses. For example: ``` (
|
1305
|
+
# scheduling.automaticRestart = true) (cpuPlatform = "Intel Skylake") ``` By
|
1306
|
+
# default, each expression is an `AND` expression. However, you can include `AND`
|
1307
|
+
# and `OR` expressions explicitly. For example: ``` (cpuPlatform = "Intel
|
1308
|
+
# Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.
|
1309
|
+
# automaticRestart = true) ``` If you want to use a regular expression, use the `
|
1310
|
+
# eq` (equal) or `ne` (not equal) operator against a single un-parenthesized
|
1311
|
+
# expression with or without quotes or against multiple parenthesized
|
1312
|
+
# expressions. Examples: `fieldname eq unquoted literal` `fieldname eq 'single
|
1313
|
+
# quoted literal'` `fieldname eq "double quoted literal"` `(fieldname1 eq
|
1314
|
+
# literal) (fieldname2 ne "literal")` The literal value is interpreted as a
|
1315
|
+
# regular expression using Google RE2 library syntax. The literal value must
|
1316
|
+
# match the entire field. For example, to filter for instances that do not end
|
1317
|
+
# with name "instance", you would use `name ne .*instance`.
|
1252
1318
|
# @param [Fixnum] max_results
|
1253
1319
|
# The maximum number of results per page that should be returned. If the number
|
1254
1320
|
# of available results is larger than `maxResults`, Compute Engine returns a `
|
@@ -1302,25 +1368,36 @@ module Google
|
|
1302
1368
|
# @param [String] type_provider
|
1303
1369
|
# The name of the type provider for this request.
|
1304
1370
|
# @param [String] filter
|
1305
|
-
# A filter expression that filters resources listed in the response.
|
1306
|
-
#
|
1307
|
-
#
|
1308
|
-
#
|
1309
|
-
#
|
1310
|
-
#
|
1311
|
-
#
|
1312
|
-
#
|
1313
|
-
#
|
1314
|
-
#
|
1315
|
-
#
|
1316
|
-
#
|
1317
|
-
# You can
|
1318
|
-
#
|
1319
|
-
#
|
1320
|
-
#
|
1321
|
-
#
|
1322
|
-
#
|
1323
|
-
#
|
1371
|
+
# A filter expression that filters resources listed in the response. Most
|
1372
|
+
# Compute resources support two types of filter expressions: expressions that
|
1373
|
+
# support regular expressions and expressions that follow API improvement
|
1374
|
+
# proposal AIP-160. If you want to use AIP-160, your expression must specify the
|
1375
|
+
# field name, an operator, and the value that you want to use for filtering. The
|
1376
|
+
# value must be a string, a number, or a boolean. The operator must be either `=`
|
1377
|
+
# , `!=`, `>`, `<`, `<=`, `>=` or `:`. For example, if you are filtering Compute
|
1378
|
+
# Engine instances, you can exclude instances named `example-instance` by
|
1379
|
+
# specifying `name != example-instance`. The `:` operator can be used with
|
1380
|
+
# string fields to match substrings. For non-string fields it is equivalent to
|
1381
|
+
# the `=` operator. The `:*` comparison can be used to test whether a key has
|
1382
|
+
# been defined. For example, to find all objects with `owner` label use: ```
|
1383
|
+
# labels.owner:* ``` You can also filter nested fields. For example, you could
|
1384
|
+
# specify `scheduling.automaticRestart = false` to include instances only if
|
1385
|
+
# they are not scheduled for automatic restarts. You can use filtering on nested
|
1386
|
+
# fields to filter based on resource labels. To filter on multiple expressions,
|
1387
|
+
# provide each separate expression within parentheses. For example: ``` (
|
1388
|
+
# scheduling.automaticRestart = true) (cpuPlatform = "Intel Skylake") ``` By
|
1389
|
+
# default, each expression is an `AND` expression. However, you can include `AND`
|
1390
|
+
# and `OR` expressions explicitly. For example: ``` (cpuPlatform = "Intel
|
1391
|
+
# Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.
|
1392
|
+
# automaticRestart = true) ``` If you want to use a regular expression, use the `
|
1393
|
+
# eq` (equal) or `ne` (not equal) operator against a single un-parenthesized
|
1394
|
+
# expression with or without quotes or against multiple parenthesized
|
1395
|
+
# expressions. Examples: `fieldname eq unquoted literal` `fieldname eq 'single
|
1396
|
+
# quoted literal'` `fieldname eq "double quoted literal"` `(fieldname1 eq
|
1397
|
+
# literal) (fieldname2 ne "literal")` The literal value is interpreted as a
|
1398
|
+
# regular expression using Google RE2 library syntax. The literal value must
|
1399
|
+
# match the entire field. For example, to filter for instances that do not end
|
1400
|
+
# with name "instance", you would use `name ne .*instance`.
|
1324
1401
|
# @param [Fixnum] max_results
|
1325
1402
|
# The maximum number of results per page that should be returned. If the number
|
1326
1403
|
# of available results is larger than `maxResults`, Compute Engine returns a `
|
@@ -1445,25 +1522,36 @@ module Google
|
|
1445
1522
|
# @param [String] project
|
1446
1523
|
# The project ID for this request.
|
1447
1524
|
# @param [String] filter
|
1448
|
-
# A filter expression that filters resources listed in the response.
|
1449
|
-
#
|
1450
|
-
#
|
1451
|
-
#
|
1452
|
-
#
|
1453
|
-
#
|
1454
|
-
#
|
1455
|
-
#
|
1456
|
-
#
|
1457
|
-
#
|
1458
|
-
#
|
1459
|
-
#
|
1460
|
-
# You can
|
1461
|
-
#
|
1462
|
-
#
|
1463
|
-
#
|
1464
|
-
#
|
1465
|
-
#
|
1466
|
-
#
|
1525
|
+
# A filter expression that filters resources listed in the response. Most
|
1526
|
+
# Compute resources support two types of filter expressions: expressions that
|
1527
|
+
# support regular expressions and expressions that follow API improvement
|
1528
|
+
# proposal AIP-160. If you want to use AIP-160, your expression must specify the
|
1529
|
+
# field name, an operator, and the value that you want to use for filtering. The
|
1530
|
+
# value must be a string, a number, or a boolean. The operator must be either `=`
|
1531
|
+
# , `!=`, `>`, `<`, `<=`, `>=` or `:`. For example, if you are filtering Compute
|
1532
|
+
# Engine instances, you can exclude instances named `example-instance` by
|
1533
|
+
# specifying `name != example-instance`. The `:` operator can be used with
|
1534
|
+
# string fields to match substrings. For non-string fields it is equivalent to
|
1535
|
+
# the `=` operator. The `:*` comparison can be used to test whether a key has
|
1536
|
+
# been defined. For example, to find all objects with `owner` label use: ```
|
1537
|
+
# labels.owner:* ``` You can also filter nested fields. For example, you could
|
1538
|
+
# specify `scheduling.automaticRestart = false` to include instances only if
|
1539
|
+
# they are not scheduled for automatic restarts. You can use filtering on nested
|
1540
|
+
# fields to filter based on resource labels. To filter on multiple expressions,
|
1541
|
+
# provide each separate expression within parentheses. For example: ``` (
|
1542
|
+
# scheduling.automaticRestart = true) (cpuPlatform = "Intel Skylake") ``` By
|
1543
|
+
# default, each expression is an `AND` expression. However, you can include `AND`
|
1544
|
+
# and `OR` expressions explicitly. For example: ``` (cpuPlatform = "Intel
|
1545
|
+
# Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.
|
1546
|
+
# automaticRestart = true) ``` If you want to use a regular expression, use the `
|
1547
|
+
# eq` (equal) or `ne` (not equal) operator against a single un-parenthesized
|
1548
|
+
# expression with or without quotes or against multiple parenthesized
|
1549
|
+
# expressions. Examples: `fieldname eq unquoted literal` `fieldname eq 'single
|
1550
|
+
# quoted literal'` `fieldname eq "double quoted literal"` `(fieldname1 eq
|
1551
|
+
# literal) (fieldname2 ne "literal")` The literal value is interpreted as a
|
1552
|
+
# regular expression using Google RE2 library syntax. The literal value must
|
1553
|
+
# match the entire field. For example, to filter for instances that do not end
|
1554
|
+
# with name "instance", you would use `name ne .*instance`.
|
1467
1555
|
# @param [Fixnum] max_results
|
1468
1556
|
# The maximum number of results per page that should be returned. If the number
|
1469
1557
|
# 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.17.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-06-13 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.
|
19
|
+
version: '0.5'
|
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.
|
29
|
+
version: '0.5'
|
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-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.17.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: []
|
@@ -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.
|
78
|
+
rubygems_version: 3.3.14
|
79
79
|
signing_key:
|
80
80
|
specification_version: 4
|
81
81
|
summary: Simple REST client for Cloud Deployment Manager V2 API V2beta
|