google-apis-deploymentmanager_alpha 0.15.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: 0d3323c54db0c4abf45cd1614f2c78a8b7e7fefa7756af02f79865b1dc81834e
4
- data.tar.gz: '08be671c5c799c01f010e4f4f025f98a957903e4b70fc342648705dbafd46b51'
3
+ metadata.gz: 1efd3a243c81a7ffd30b9729631ea424b2a5a205dd98389ccda5292f0541bb46
4
+ data.tar.gz: 050acb8aae8f2a2bba2a10e9f1b3d8116f394c6d02bf6ce5ba4335393faeb0c6
5
5
  SHA512:
6
- metadata.gz: 620ddf8e277b8c656e3908f1e577e68d016a5445ed54c87011a7b5b07d148dd61729dd43101c20ffd8ab47ea2c7466aa28973daa6a606bcc8fe2718e6f54adbd
7
- data.tar.gz: 5a1af8cf123566e6b77f3ec89dcb0708ec58cbe8395e2137114114fda20f36503e0d72d23e9e31a5c59a511ec4190c8d9d467aaaee7252dd7a0dca253c09faf1
6
+ metadata.gz: 0226c8b1cb67ddf1e9b421b2409a8470f4eab6fa70e445b7ce34c3f27b7064a5e45be778cf64272c9ec67afe7b10e29b0189d685f927801fa65264b06f78c4e6
7
+ data.tar.gz: a795a2175dd439b7458b9012f1e7684143e9937f9f57102bb2889bad150a787611540af278c7cb9e17e3c26cb4edb5add5c43f63cf211b225f02b97396490469
data/CHANGELOG.md CHANGED
@@ -1,5 +1,9 @@
1
1
  # Release history for google-apis-deploymentmanager_alpha
2
2
 
3
+ ### v0.16.0 (2022-05-27)
4
+
5
+ * Regenerated from discovery document revision 20220520
6
+
3
7
  ### v0.15.0 (2022-05-05)
4
8
 
5
9
  * Regenerated from discovery document revision 20220429
@@ -16,13 +16,13 @@ module Google
16
16
  module Apis
17
17
  module DeploymentmanagerAlpha
18
18
  # Version of the google-apis-deploymentmanager_alpha gem
19
- GEM_VERSION = "0.15.0"
19
+ GEM_VERSION = "0.16.0"
20
20
 
21
21
  # Version of the code generator used to generate this client
22
22
  GENERATOR_VERSION = "0.4.1"
23
23
 
24
24
  # Revision of the discovery document this client was generated from
25
- REVISION = "20220429"
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. The
158
- # expression must specify the field name, an operator, and the value that you
159
- # want to use for filtering. The value must be a string, a number, or a boolean.
160
- # The operator must be either `=`, `!=`, `>`, `<`, `<=`, `>=` or `:`. For
161
- # example, if you are filtering Compute Engine instances, you can exclude
162
- # instances named `example-instance` by specifying `name != example-instance`.
163
- # The `:` operator can be used with string fields to match substrings. For non-
164
- # string fields it is equivalent to the `=` operator. The `:*` comparison can be
165
- # used to test whether a key has been defined. For example, to find all objects
166
- # with `owner` label use: ``` labels.owner:* ``` You can also filter nested
167
- # fields. For example, you could specify `scheduling.automaticRestart = false`
168
- # to include instances only if they are not scheduled for automatic restarts.
169
- # You can use filtering on nested fields to filter based on resource labels. To
170
- # filter on multiple expressions, provide each separate expression within
171
- # parentheses. For example: ``` (scheduling.automaticRestart = true) (
172
- # cpuPlatform = "Intel Skylake") ``` By default, each expression is an `AND`
173
- # expression. However, you can include `AND` and `OR` expressions explicitly.
174
- # For example: ``` (cpuPlatform = "Intel Skylake") OR (cpuPlatform = "Intel
175
- # Broadwell") AND (scheduling.automaticRestart = true) ```
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. The
488
- # expression must specify the field name, an operator, and the value that you
489
- # want to use for filtering. The value must be a string, a number, or a boolean.
490
- # The operator must be either `=`, `!=`, `>`, `<`, `<=`, `>=` or `:`. For
491
- # example, if you are filtering Compute Engine instances, you can exclude
492
- # instances named `example-instance` by specifying `name != example-instance`.
493
- # The `:` operator can be used with string fields to match substrings. For non-
494
- # string fields it is equivalent to the `=` operator. The `:*` comparison can be
495
- # used to test whether a key has been defined. For example, to find all objects
496
- # with `owner` label use: ``` labels.owner:* ``` You can also filter nested
497
- # fields. For example, you could specify `scheduling.automaticRestart = false`
498
- # to include instances only if they are not scheduled for automatic restarts.
499
- # You can use filtering on nested fields to filter based on resource labels. To
500
- # filter on multiple expressions, provide each separate expression within
501
- # parentheses. For example: ``` (scheduling.automaticRestart = true) (
502
- # cpuPlatform = "Intel Skylake") ``` By default, each expression is an `AND`
503
- # expression. However, you can include `AND` and `OR` expressions explicitly.
504
- # For example: ``` (cpuPlatform = "Intel Skylake") OR (cpuPlatform = "Intel
505
- # Broadwell") AND (scheduling.automaticRestart = true) ```
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. The
816
- # expression must specify the field name, an operator, and the value that you
817
- # want to use for filtering. The value must be a string, a number, or a boolean.
818
- # The operator must be either `=`, `!=`, `>`, `<`, `<=`, `>=` or `:`. For
819
- # example, if you are filtering Compute Engine instances, you can exclude
820
- # instances named `example-instance` by specifying `name != example-instance`.
821
- # The `:` operator can be used with string fields to match substrings. For non-
822
- # string fields it is equivalent to the `=` operator. The `:*` comparison can be
823
- # used to test whether a key has been defined. For example, to find all objects
824
- # with `owner` label use: ``` labels.owner:* ``` You can also filter nested
825
- # fields. For example, you could specify `scheduling.automaticRestart = false`
826
- # to include instances only if they are not scheduled for automatic restarts.
827
- # You can use filtering on nested fields to filter based on resource labels. To
828
- # filter on multiple expressions, provide each separate expression within
829
- # parentheses. For example: ``` (scheduling.automaticRestart = true) (
830
- # cpuPlatform = "Intel Skylake") ``` By default, each expression is an `AND`
831
- # expression. However, you can include `AND` and `OR` expressions explicitly.
832
- # For example: ``` (cpuPlatform = "Intel Skylake") OR (cpuPlatform = "Intel
833
- # Broadwell") AND (scheduling.automaticRestart = true) ```
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. The
920
- # expression must specify the field name, an operator, and the value that you
921
- # want to use for filtering. The value must be a string, a number, or a boolean.
922
- # The operator must be either `=`, `!=`, `>`, `<`, `<=`, `>=` or `:`. For
923
- # example, if you are filtering Compute Engine instances, you can exclude
924
- # instances named `example-instance` by specifying `name != example-instance`.
925
- # The `:` operator can be used with string fields to match substrings. For non-
926
- # string fields it is equivalent to the `=` operator. The `:*` comparison can be
927
- # used to test whether a key has been defined. For example, to find all objects
928
- # with `owner` label use: ``` labels.owner:* ``` You can also filter nested
929
- # fields. For example, you could specify `scheduling.automaticRestart = false`
930
- # to include instances only if they are not scheduled for automatic restarts.
931
- # You can use filtering on nested fields to filter based on resource labels. To
932
- # filter on multiple expressions, provide each separate expression within
933
- # parentheses. For example: ``` (scheduling.automaticRestart = true) (
934
- # cpuPlatform = "Intel Skylake") ``` By default, each expression is an `AND`
935
- # expression. However, you can include `AND` and `OR` expressions explicitly.
936
- # For example: ``` (cpuPlatform = "Intel Skylake") OR (cpuPlatform = "Intel
937
- # Broadwell") AND (scheduling.automaticRestart = true) ```
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. The
1028
- # expression must specify the field name, an operator, and the value that you
1029
- # want to use for filtering. The value must be a string, a number, or a boolean.
1030
- # The operator must be either `=`, `!=`, `>`, `<`, `<=`, `>=` or `:`. For
1031
- # example, if you are filtering Compute Engine instances, you can exclude
1032
- # instances named `example-instance` by specifying `name != example-instance`.
1033
- # The `:` operator can be used with string fields to match substrings. For non-
1034
- # string fields it is equivalent to the `=` operator. The `:*` comparison can be
1035
- # used to test whether a key has been defined. For example, to find all objects
1036
- # with `owner` label use: ``` labels.owner:* ``` You can also filter nested
1037
- # fields. For example, you could specify `scheduling.automaticRestart = false`
1038
- # to include instances only if they are not scheduled for automatic restarts.
1039
- # You can use filtering on nested fields to filter based on resource labels. To
1040
- # filter on multiple expressions, provide each separate expression within
1041
- # parentheses. For example: ``` (scheduling.automaticRestart = true) (
1042
- # cpuPlatform = "Intel Skylake") ``` By default, each expression is an `AND`
1043
- # expression. However, you can include `AND` and `OR` expressions explicitly.
1044
- # For example: ``` (cpuPlatform = "Intel Skylake") OR (cpuPlatform = "Intel
1045
- # Broadwell") AND (scheduling.automaticRestart = true) ```
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. The
1234
- # expression must specify the field name, an operator, and the value that you
1235
- # want to use for filtering. The value must be a string, a number, or a boolean.
1236
- # The operator must be either `=`, `!=`, `>`, `<`, `<=`, `>=` or `:`. For
1237
- # example, if you are filtering Compute Engine instances, you can exclude
1238
- # instances named `example-instance` by specifying `name != example-instance`.
1239
- # The `:` operator can be used with string fields to match substrings. For non-
1240
- # string fields it is equivalent to the `=` operator. The `:*` comparison can be
1241
- # used to test whether a key has been defined. For example, to find all objects
1242
- # with `owner` label use: ``` labels.owner:* ``` You can also filter nested
1243
- # fields. For example, you could specify `scheduling.automaticRestart = false`
1244
- # to include instances only if they are not scheduled for automatic restarts.
1245
- # You can use filtering on nested fields to filter based on resource labels. To
1246
- # filter on multiple expressions, provide each separate expression within
1247
- # parentheses. For example: ``` (scheduling.automaticRestart = true) (
1248
- # cpuPlatform = "Intel Skylake") ``` By default, each expression is an `AND`
1249
- # expression. However, you can include `AND` and `OR` expressions explicitly.
1250
- # For example: ``` (cpuPlatform = "Intel Skylake") OR (cpuPlatform = "Intel
1251
- # Broadwell") AND (scheduling.automaticRestart = true) ```
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. The
1306
- # expression must specify the field name, an operator, and the value that you
1307
- # want to use for filtering. The value must be a string, a number, or a boolean.
1308
- # The operator must be either `=`, `!=`, `>`, `<`, `<=`, `>=` or `:`. For
1309
- # example, if you are filtering Compute Engine instances, you can exclude
1310
- # instances named `example-instance` by specifying `name != example-instance`.
1311
- # The `:` operator can be used with string fields to match substrings. For non-
1312
- # string fields it is equivalent to the `=` operator. The `:*` comparison can be
1313
- # used to test whether a key has been defined. For example, to find all objects
1314
- # with `owner` label use: ``` labels.owner:* ``` You can also filter nested
1315
- # fields. For example, you could specify `scheduling.automaticRestart = false`
1316
- # to include instances only if they are not scheduled for automatic restarts.
1317
- # You can use filtering on nested fields to filter based on resource labels. To
1318
- # filter on multiple expressions, provide each separate expression within
1319
- # parentheses. For example: ``` (scheduling.automaticRestart = true) (
1320
- # cpuPlatform = "Intel Skylake") ``` By default, each expression is an `AND`
1321
- # expression. However, you can include `AND` and `OR` expressions explicitly.
1322
- # For example: ``` (cpuPlatform = "Intel Skylake") OR (cpuPlatform = "Intel
1323
- # Broadwell") AND (scheduling.automaticRestart = true) ```
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 `
@@ -1478,25 +1555,36 @@ module Google
1478
1555
  # @param [String] project
1479
1556
  # The project ID for this request.
1480
1557
  # @param [String] filter
1481
- # A filter expression that filters resources listed in the response. The
1482
- # expression must specify the field name, an operator, and the value that you
1483
- # want to use for filtering. The value must be a string, a number, or a boolean.
1484
- # The operator must be either `=`, `!=`, `>`, `<`, `<=`, `>=` or `:`. For
1485
- # example, if you are filtering Compute Engine instances, you can exclude
1486
- # instances named `example-instance` by specifying `name != example-instance`.
1487
- # The `:` operator can be used with string fields to match substrings. For non-
1488
- # string fields it is equivalent to the `=` operator. The `:*` comparison can be
1489
- # used to test whether a key has been defined. For example, to find all objects
1490
- # with `owner` label use: ``` labels.owner:* ``` You can also filter nested
1491
- # fields. For example, you could specify `scheduling.automaticRestart = false`
1492
- # to include instances only if they are not scheduled for automatic restarts.
1493
- # You can use filtering on nested fields to filter based on resource labels. To
1494
- # filter on multiple expressions, provide each separate expression within
1495
- # parentheses. For example: ``` (scheduling.automaticRestart = true) (
1496
- # cpuPlatform = "Intel Skylake") ``` By default, each expression is an `AND`
1497
- # expression. However, you can include `AND` and `OR` expressions explicitly.
1498
- # For example: ``` (cpuPlatform = "Intel Skylake") OR (cpuPlatform = "Intel
1499
- # Broadwell") AND (scheduling.automaticRestart = true) ```
1558
+ # A filter expression that filters resources listed in the response. Most
1559
+ # Compute resources support two types of filter expressions: expressions that
1560
+ # support regular expressions and expressions that follow API improvement
1561
+ # proposal AIP-160. If you want to use AIP-160, your expression must specify the
1562
+ # field name, an operator, and the value that you want to use for filtering. The
1563
+ # value must be a string, a number, or a boolean. The operator must be either `=`
1564
+ # , `!=`, `>`, `<`, `<=`, `>=` or `:`. For example, if you are filtering Compute
1565
+ # Engine instances, you can exclude instances named `example-instance` by
1566
+ # specifying `name != example-instance`. The `:` operator can be used with
1567
+ # string fields to match substrings. For non-string fields it is equivalent to
1568
+ # the `=` operator. The `:*` comparison can be used to test whether a key has
1569
+ # been defined. For example, to find all objects with `owner` label use: ```
1570
+ # labels.owner:* ``` You can also filter nested fields. For example, you could
1571
+ # specify `scheduling.automaticRestart = false` to include instances only if
1572
+ # they are not scheduled for automatic restarts. You can use filtering on nested
1573
+ # fields to filter based on resource labels. To filter on multiple expressions,
1574
+ # provide each separate expression within parentheses. For example: ``` (
1575
+ # scheduling.automaticRestart = true) (cpuPlatform = "Intel Skylake") ``` By
1576
+ # default, each expression is an `AND` expression. However, you can include `AND`
1577
+ # and `OR` expressions explicitly. For example: ``` (cpuPlatform = "Intel
1578
+ # Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.
1579
+ # automaticRestart = true) ``` If you want to use a regular expression, use the `
1580
+ # eq` (equal) or `ne` (not equal) operator against a single un-parenthesized
1581
+ # expression with or without quotes or against multiple parenthesized
1582
+ # expressions. Examples: `fieldname eq unquoted literal` `fieldname eq 'single
1583
+ # quoted literal'` `fieldname eq "double quoted literal"` `(fieldname1 eq
1584
+ # literal) (fieldname2 ne "literal")` The literal value is interpreted as a
1585
+ # regular expression using Google RE2 library syntax. The literal value must
1586
+ # match the entire field. For example, to filter for instances that do not end
1587
+ # with name "instance", you would use `name ne .*instance`.
1500
1588
  # @param [Fixnum] max_results
1501
1589
  # The maximum number of results per page that should be returned. If the number
1502
1590
  # 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_alpha
3
3
  version: !ruby/object:Gem::Version
4
- version: 0.15.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-05-09 00:00:00.000000000 Z
11
+ date: 2022-05-30 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_alpha/CHANGELOG.md
61
- documentation_uri: https://googleapis.dev/ruby/google-apis-deploymentmanager_alpha/v0.15.0
61
+ documentation_uri: https://googleapis.dev/ruby/google-apis-deploymentmanager_alpha/v0.16.0
62
62
  source_code_uri: https://github.com/googleapis/google-api-ruby-client/tree/main/generated/google-apis-deploymentmanager_alpha
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.5
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 Alpha