google-apis-deploymentmanager_v2 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: cc066a43360b200866db817f0b51815818e987e9a9814d389270868ed01620a7
|
|
4
|
+
data.tar.gz: 8f5ca034076c1bc48020762e15ed86afe6f58bb8ec5b5d2723a1b3bf22286768
|
|
5
5
|
SHA512:
|
|
6
|
-
metadata.gz:
|
|
7
|
-
data.tar.gz:
|
|
6
|
+
metadata.gz: 4f146b5ccbff98954e8e85223b8c4ba47f66877580a3658bc88dd0f83ecd2d766a6240b828d370d08a569587516e31d5f126b70b22fc86a5213eb359c1762549
|
|
7
|
+
data.tar.gz: a67a4e507b28d12a11ead0f24529fa3a378e3807079c931afe7017e964eeb4757ff4e652e5cd5fe3a879f4f882050e87ab2b92fa8f33296a53590396328204a9
|
data/CHANGELOG.md
CHANGED
|
@@ -1,5 +1,13 @@
|
|
|
1
1
|
# Release history for google-apis-deploymentmanager_v2
|
|
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
|
|
@@ -132,21 +132,43 @@ module Google
|
|
|
132
132
|
# project.svc.id.goog[my-namespace/my-kubernetes-sa]`. * `group:`emailid``: An
|
|
133
133
|
# email address that represents a Google group. For example, `admins@example.com`
|
|
134
134
|
# . * `domain:`domain``: The G Suite domain (primary) that represents all the
|
|
135
|
-
# users of that domain. For example, `google.com` or `example.com`. * `
|
|
136
|
-
#
|
|
137
|
-
#
|
|
138
|
-
#
|
|
139
|
-
#
|
|
140
|
-
#
|
|
141
|
-
#
|
|
142
|
-
#
|
|
135
|
+
# users of that domain. For example, `google.com` or `example.com`. * `principal:
|
|
136
|
+
# //iam.googleapis.com/locations/global/workforcePools/`pool_id`/subject/`
|
|
137
|
+
# subject_attribute_value``: A single identity in a workforce identity pool. * `
|
|
138
|
+
# principalSet://iam.googleapis.com/locations/global/workforcePools/`pool_id`/
|
|
139
|
+
# group/`group_id``: All workforce identities in a group. * `principalSet://iam.
|
|
140
|
+
# googleapis.com/locations/global/workforcePools/`pool_id`/attribute.`
|
|
141
|
+
# attribute_name`/`attribute_value``: All workforce identities with a specific
|
|
142
|
+
# attribute value. * `principalSet://iam.googleapis.com/locations/global/
|
|
143
|
+
# workforcePools/`pool_id`/*`: All identities in a workforce identity pool. * `
|
|
144
|
+
# principal://iam.googleapis.com/projects/`project_number`/locations/global/
|
|
145
|
+
# workloadIdentityPools/`pool_id`/subject/`subject_attribute_value``: A single
|
|
146
|
+
# identity in a workload identity pool. * `principalSet://iam.googleapis.com/
|
|
147
|
+
# projects/`project_number`/locations/global/workloadIdentityPools/`pool_id`/
|
|
148
|
+
# group/`group_id``: A workload identity pool group. * `principalSet://iam.
|
|
149
|
+
# googleapis.com/projects/`project_number`/locations/global/
|
|
150
|
+
# workloadIdentityPools/`pool_id`/attribute.`attribute_name`/`attribute_value``:
|
|
151
|
+
# All identities in a workload identity pool with a certain attribute. * `
|
|
152
|
+
# principalSet://iam.googleapis.com/projects/`project_number`/locations/global/
|
|
153
|
+
# workloadIdentityPools/`pool_id`/*`: All identities in a workload identity pool.
|
|
154
|
+
# * `deleted:user:`emailid`?uid=`uniqueid``: An email address (plus unique
|
|
155
|
+
# identifier) representing a user that has been recently deleted. For example, `
|
|
156
|
+
# alice@example.com?uid=123456789012345678901`. If the user is recovered, this
|
|
157
|
+
# value reverts to `user:`emailid`` and the recovered user retains the role in
|
|
158
|
+
# the binding. * `deleted:serviceAccount:`emailid`?uid=`uniqueid``: An email
|
|
159
|
+
# address (plus unique identifier) representing a service account that has been
|
|
160
|
+
# recently deleted. For example, `my-other-app@appspot.gserviceaccount.com?uid=
|
|
143
161
|
# 123456789012345678901`. If the service account is undeleted, this value
|
|
144
162
|
# reverts to `serviceAccount:`emailid`` and the undeleted service account
|
|
145
163
|
# retains the role in the binding. * `deleted:group:`emailid`?uid=`uniqueid``:
|
|
146
164
|
# An email address (plus unique identifier) representing a Google group that has
|
|
147
165
|
# been recently deleted. For example, `admins@example.com?uid=
|
|
148
166
|
# 123456789012345678901`. If the group is recovered, this value reverts to `
|
|
149
|
-
# group:`emailid`` and the recovered group retains the role in the binding.
|
|
167
|
+
# group:`emailid`` and the recovered group retains the role in the binding. * `
|
|
168
|
+
# deleted:principal://iam.googleapis.com/locations/global/workforcePools/`
|
|
169
|
+
# pool_id`/subject/`subject_attribute_value``: Deleted single identity in a
|
|
170
|
+
# workforce identity pool. For example, `deleted:principal://iam.googleapis.com/
|
|
171
|
+
# locations/global/workforcePools/my-pool-id/subject/my-subject-attribute-value`.
|
|
150
172
|
# Corresponds to the JSON property `members`
|
|
151
173
|
# @return [Array<String>]
|
|
152
174
|
attr_accessor :members
|
|
@@ -16,13 +16,13 @@ module Google
|
|
|
16
16
|
module Apis
|
|
17
17
|
module DeploymentmanagerV2
|
|
18
18
|
# Version of the google-apis-deploymentmanager_v2 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
|
|
@@ -246,33 +246,34 @@ module Google
|
|
|
246
246
|
# A filter expression that filters resources listed in the response. Most
|
|
247
247
|
# Compute resources support two types of filter expressions: expressions that
|
|
248
248
|
# support regular expressions and expressions that follow API improvement
|
|
249
|
-
# proposal AIP-160.
|
|
250
|
-
#
|
|
251
|
-
#
|
|
252
|
-
#
|
|
249
|
+
# proposal AIP-160. These two types of filter expressions cannot be mixed in one
|
|
250
|
+
# request. If you want to use AIP-160, your expression must specify the field
|
|
251
|
+
# name, an operator, and the value that you want to use for filtering. The value
|
|
252
|
+
# must be a string, a number, or a boolean. The operator must be either `=`, `!=`
|
|
253
|
+
# , `>`, `<`, `<=`, `>=` or `:`. For example, if you are filtering Compute
|
|
253
254
|
# Engine instances, you can exclude instances named `example-instance` by
|
|
254
|
-
# specifying `name != example-instance`. The
|
|
255
|
-
#
|
|
256
|
-
#
|
|
257
|
-
#
|
|
258
|
-
#
|
|
259
|
-
#
|
|
260
|
-
#
|
|
261
|
-
#
|
|
262
|
-
#
|
|
263
|
-
#
|
|
264
|
-
#
|
|
265
|
-
#
|
|
266
|
-
#
|
|
267
|
-
#
|
|
268
|
-
#
|
|
269
|
-
#
|
|
270
|
-
#
|
|
271
|
-
#
|
|
272
|
-
# literal
|
|
273
|
-
#
|
|
274
|
-
#
|
|
275
|
-
#
|
|
255
|
+
# specifying `name != example-instance`. The `:*` comparison can be used to test
|
|
256
|
+
# whether a key has been defined. For example, to find all objects with `owner`
|
|
257
|
+
# label use: ``` labels.owner:* ``` You can also filter nested fields. For
|
|
258
|
+
# example, you could specify `scheduling.automaticRestart = false` to include
|
|
259
|
+
# instances only if they are not scheduled for automatic restarts. You can use
|
|
260
|
+
# filtering on nested fields to filter based on resource labels. To filter on
|
|
261
|
+
# multiple expressions, provide each separate expression within parentheses. For
|
|
262
|
+
# example: ``` (scheduling.automaticRestart = true) (cpuPlatform = "Intel
|
|
263
|
+
# Skylake") ``` By default, each expression is an `AND` expression. However, you
|
|
264
|
+
# can include `AND` and `OR` expressions explicitly. For example: ``` (
|
|
265
|
+
# cpuPlatform = "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (
|
|
266
|
+
# scheduling.automaticRestart = true) ``` If you want to use a regular
|
|
267
|
+
# expression, use the `eq` (equal) or `ne` (not equal) operator against a single
|
|
268
|
+
# un-parenthesized expression with or without quotes or against multiple
|
|
269
|
+
# parenthesized expressions. Examples: `fieldname eq unquoted literal` `
|
|
270
|
+
# fieldname eq 'single quoted literal'` `fieldname eq "double quoted literal"` `(
|
|
271
|
+
# fieldname1 eq literal) (fieldname2 ne "literal")` The literal value is
|
|
272
|
+
# interpreted as a regular expression using Google RE2 library syntax. The
|
|
273
|
+
# literal value must match the entire field. For example, to filter for
|
|
274
|
+
# instances that do not end with name "instance", you would use `name ne .*
|
|
275
|
+
# instance`. You cannot combine constraints on multiple fields using regular
|
|
276
|
+
# expressions.
|
|
276
277
|
# @param [Fixnum] max_results
|
|
277
278
|
# The maximum number of results per page that should be returned. If the number
|
|
278
279
|
# of available results is larger than `maxResults`, Compute Engine returns a `
|
|
@@ -585,33 +586,34 @@ module Google
|
|
|
585
586
|
# A filter expression that filters resources listed in the response. Most
|
|
586
587
|
# Compute resources support two types of filter expressions: expressions that
|
|
587
588
|
# support regular expressions and expressions that follow API improvement
|
|
588
|
-
# proposal AIP-160.
|
|
589
|
-
#
|
|
590
|
-
#
|
|
591
|
-
#
|
|
589
|
+
# proposal AIP-160. These two types of filter expressions cannot be mixed in one
|
|
590
|
+
# request. If you want to use AIP-160, your expression must specify the field
|
|
591
|
+
# name, an operator, and the value that you want to use for filtering. The value
|
|
592
|
+
# must be a string, a number, or a boolean. The operator must be either `=`, `!=`
|
|
593
|
+
# , `>`, `<`, `<=`, `>=` or `:`. For example, if you are filtering Compute
|
|
592
594
|
# Engine instances, you can exclude instances named `example-instance` by
|
|
593
|
-
# specifying `name != example-instance`. The
|
|
594
|
-
#
|
|
595
|
-
#
|
|
596
|
-
#
|
|
597
|
-
#
|
|
598
|
-
#
|
|
599
|
-
#
|
|
600
|
-
#
|
|
601
|
-
#
|
|
602
|
-
#
|
|
603
|
-
#
|
|
604
|
-
#
|
|
605
|
-
#
|
|
606
|
-
#
|
|
607
|
-
#
|
|
608
|
-
#
|
|
609
|
-
#
|
|
610
|
-
#
|
|
611
|
-
# literal
|
|
612
|
-
#
|
|
613
|
-
#
|
|
614
|
-
#
|
|
595
|
+
# specifying `name != example-instance`. The `:*` comparison can be used to test
|
|
596
|
+
# whether a key has been defined. For example, to find all objects with `owner`
|
|
597
|
+
# label use: ``` labels.owner:* ``` You can also filter nested fields. For
|
|
598
|
+
# example, you could specify `scheduling.automaticRestart = false` to include
|
|
599
|
+
# instances only if they are not scheduled for automatic restarts. You can use
|
|
600
|
+
# filtering on nested fields to filter based on resource labels. To filter on
|
|
601
|
+
# multiple expressions, provide each separate expression within parentheses. For
|
|
602
|
+
# example: ``` (scheduling.automaticRestart = true) (cpuPlatform = "Intel
|
|
603
|
+
# Skylake") ``` By default, each expression is an `AND` expression. However, you
|
|
604
|
+
# can include `AND` and `OR` expressions explicitly. For example: ``` (
|
|
605
|
+
# cpuPlatform = "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (
|
|
606
|
+
# scheduling.automaticRestart = true) ``` If you want to use a regular
|
|
607
|
+
# expression, use the `eq` (equal) or `ne` (not equal) operator against a single
|
|
608
|
+
# un-parenthesized expression with or without quotes or against multiple
|
|
609
|
+
# parenthesized expressions. Examples: `fieldname eq unquoted literal` `
|
|
610
|
+
# fieldname eq 'single quoted literal'` `fieldname eq "double quoted literal"` `(
|
|
611
|
+
# fieldname1 eq literal) (fieldname2 ne "literal")` The literal value is
|
|
612
|
+
# interpreted as a regular expression using Google RE2 library syntax. The
|
|
613
|
+
# literal value must match the entire field. For example, to filter for
|
|
614
|
+
# instances that do not end with name "instance", you would use `name ne .*
|
|
615
|
+
# instance`. You cannot combine constraints on multiple fields using regular
|
|
616
|
+
# expressions.
|
|
615
617
|
# @param [Fixnum] max_results
|
|
616
618
|
# The maximum number of results per page that should be returned. If the number
|
|
617
619
|
# of available results is larger than `maxResults`, Compute Engine returns a `
|
|
@@ -700,33 +702,34 @@ module Google
|
|
|
700
702
|
# A filter expression that filters resources listed in the response. Most
|
|
701
703
|
# Compute resources support two types of filter expressions: expressions that
|
|
702
704
|
# support regular expressions and expressions that follow API improvement
|
|
703
|
-
# proposal AIP-160.
|
|
704
|
-
#
|
|
705
|
-
#
|
|
706
|
-
#
|
|
705
|
+
# proposal AIP-160. These two types of filter expressions cannot be mixed in one
|
|
706
|
+
# request. If you want to use AIP-160, your expression must specify the field
|
|
707
|
+
# name, an operator, and the value that you want to use for filtering. The value
|
|
708
|
+
# must be a string, a number, or a boolean. The operator must be either `=`, `!=`
|
|
709
|
+
# , `>`, `<`, `<=`, `>=` or `:`. For example, if you are filtering Compute
|
|
707
710
|
# Engine instances, you can exclude instances named `example-instance` by
|
|
708
|
-
# specifying `name != example-instance`. The
|
|
709
|
-
#
|
|
710
|
-
#
|
|
711
|
-
#
|
|
712
|
-
#
|
|
713
|
-
#
|
|
714
|
-
#
|
|
715
|
-
#
|
|
716
|
-
#
|
|
717
|
-
#
|
|
718
|
-
#
|
|
719
|
-
#
|
|
720
|
-
#
|
|
721
|
-
#
|
|
722
|
-
#
|
|
723
|
-
#
|
|
724
|
-
#
|
|
725
|
-
#
|
|
726
|
-
# literal
|
|
727
|
-
#
|
|
728
|
-
#
|
|
729
|
-
#
|
|
711
|
+
# specifying `name != example-instance`. The `:*` comparison can be used to test
|
|
712
|
+
# whether a key has been defined. For example, to find all objects with `owner`
|
|
713
|
+
# label use: ``` labels.owner:* ``` You can also filter nested fields. For
|
|
714
|
+
# example, you could specify `scheduling.automaticRestart = false` to include
|
|
715
|
+
# instances only if they are not scheduled for automatic restarts. You can use
|
|
716
|
+
# filtering on nested fields to filter based on resource labels. To filter on
|
|
717
|
+
# multiple expressions, provide each separate expression within parentheses. For
|
|
718
|
+
# example: ``` (scheduling.automaticRestart = true) (cpuPlatform = "Intel
|
|
719
|
+
# Skylake") ``` By default, each expression is an `AND` expression. However, you
|
|
720
|
+
# can include `AND` and `OR` expressions explicitly. For example: ``` (
|
|
721
|
+
# cpuPlatform = "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (
|
|
722
|
+
# scheduling.automaticRestart = true) ``` If you want to use a regular
|
|
723
|
+
# expression, use the `eq` (equal) or `ne` (not equal) operator against a single
|
|
724
|
+
# un-parenthesized expression with or without quotes or against multiple
|
|
725
|
+
# parenthesized expressions. Examples: `fieldname eq unquoted literal` `
|
|
726
|
+
# fieldname eq 'single quoted literal'` `fieldname eq "double quoted literal"` `(
|
|
727
|
+
# fieldname1 eq literal) (fieldname2 ne "literal")` The literal value is
|
|
728
|
+
# interpreted as a regular expression using Google RE2 library syntax. The
|
|
729
|
+
# literal value must match the entire field. For example, to filter for
|
|
730
|
+
# instances that do not end with name "instance", you would use `name ne .*
|
|
731
|
+
# instance`. You cannot combine constraints on multiple fields using regular
|
|
732
|
+
# expressions.
|
|
730
733
|
# @param [Fixnum] max_results
|
|
731
734
|
# The maximum number of results per page that should be returned. If the number
|
|
732
735
|
# of available results is larger than `maxResults`, Compute Engine returns a `
|
|
@@ -819,33 +822,34 @@ module Google
|
|
|
819
822
|
# A filter expression that filters resources listed in the response. Most
|
|
820
823
|
# Compute resources support two types of filter expressions: expressions that
|
|
821
824
|
# support regular expressions and expressions that follow API improvement
|
|
822
|
-
# proposal AIP-160.
|
|
823
|
-
#
|
|
824
|
-
#
|
|
825
|
-
#
|
|
825
|
+
# proposal AIP-160. These two types of filter expressions cannot be mixed in one
|
|
826
|
+
# request. If you want to use AIP-160, your expression must specify the field
|
|
827
|
+
# name, an operator, and the value that you want to use for filtering. The value
|
|
828
|
+
# must be a string, a number, or a boolean. The operator must be either `=`, `!=`
|
|
829
|
+
# , `>`, `<`, `<=`, `>=` or `:`. For example, if you are filtering Compute
|
|
826
830
|
# Engine instances, you can exclude instances named `example-instance` by
|
|
827
|
-
# specifying `name != example-instance`. The
|
|
828
|
-
#
|
|
829
|
-
#
|
|
830
|
-
#
|
|
831
|
-
#
|
|
832
|
-
#
|
|
833
|
-
#
|
|
834
|
-
#
|
|
835
|
-
#
|
|
836
|
-
#
|
|
837
|
-
#
|
|
838
|
-
#
|
|
839
|
-
#
|
|
840
|
-
#
|
|
841
|
-
#
|
|
842
|
-
#
|
|
843
|
-
#
|
|
844
|
-
#
|
|
845
|
-
# literal
|
|
846
|
-
#
|
|
847
|
-
#
|
|
848
|
-
#
|
|
831
|
+
# specifying `name != example-instance`. The `:*` comparison can be used to test
|
|
832
|
+
# whether a key has been defined. For example, to find all objects with `owner`
|
|
833
|
+
# label use: ``` labels.owner:* ``` You can also filter nested fields. For
|
|
834
|
+
# example, you could specify `scheduling.automaticRestart = false` to include
|
|
835
|
+
# instances only if they are not scheduled for automatic restarts. You can use
|
|
836
|
+
# filtering on nested fields to filter based on resource labels. To filter on
|
|
837
|
+
# multiple expressions, provide each separate expression within parentheses. For
|
|
838
|
+
# example: ``` (scheduling.automaticRestart = true) (cpuPlatform = "Intel
|
|
839
|
+
# Skylake") ``` By default, each expression is an `AND` expression. However, you
|
|
840
|
+
# can include `AND` and `OR` expressions explicitly. For example: ``` (
|
|
841
|
+
# cpuPlatform = "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (
|
|
842
|
+
# scheduling.automaticRestart = true) ``` If you want to use a regular
|
|
843
|
+
# expression, use the `eq` (equal) or `ne` (not equal) operator against a single
|
|
844
|
+
# un-parenthesized expression with or without quotes or against multiple
|
|
845
|
+
# parenthesized expressions. Examples: `fieldname eq unquoted literal` `
|
|
846
|
+
# fieldname eq 'single quoted literal'` `fieldname eq "double quoted literal"` `(
|
|
847
|
+
# fieldname1 eq literal) (fieldname2 ne "literal")` The literal value is
|
|
848
|
+
# interpreted as a regular expression using Google RE2 library syntax. The
|
|
849
|
+
# literal value must match the entire field. For example, to filter for
|
|
850
|
+
# instances that do not end with name "instance", you would use `name ne .*
|
|
851
|
+
# instance`. You cannot combine constraints on multiple fields using regular
|
|
852
|
+
# expressions.
|
|
849
853
|
# @param [Fixnum] max_results
|
|
850
854
|
# The maximum number of results per page that should be returned. If the number
|
|
851
855
|
# of available results is larger than `maxResults`, Compute Engine returns a `
|
|
@@ -901,33 +905,34 @@ module Google
|
|
|
901
905
|
# A filter expression that filters resources listed in the response. Most
|
|
902
906
|
# Compute resources support two types of filter expressions: expressions that
|
|
903
907
|
# support regular expressions and expressions that follow API improvement
|
|
904
|
-
# proposal AIP-160.
|
|
905
|
-
#
|
|
906
|
-
#
|
|
907
|
-
#
|
|
908
|
+
# proposal AIP-160. These two types of filter expressions cannot be mixed in one
|
|
909
|
+
# request. If you want to use AIP-160, your expression must specify the field
|
|
910
|
+
# name, an operator, and the value that you want to use for filtering. The value
|
|
911
|
+
# must be a string, a number, or a boolean. The operator must be either `=`, `!=`
|
|
912
|
+
# , `>`, `<`, `<=`, `>=` or `:`. For example, if you are filtering Compute
|
|
908
913
|
# Engine instances, you can exclude instances named `example-instance` by
|
|
909
|
-
# specifying `name != example-instance`. The
|
|
910
|
-
#
|
|
911
|
-
#
|
|
912
|
-
#
|
|
913
|
-
#
|
|
914
|
-
#
|
|
915
|
-
#
|
|
916
|
-
#
|
|
917
|
-
#
|
|
918
|
-
#
|
|
919
|
-
#
|
|
920
|
-
#
|
|
921
|
-
#
|
|
922
|
-
#
|
|
923
|
-
#
|
|
924
|
-
#
|
|
925
|
-
#
|
|
926
|
-
#
|
|
927
|
-
# literal
|
|
928
|
-
#
|
|
929
|
-
#
|
|
930
|
-
#
|
|
914
|
+
# specifying `name != example-instance`. The `:*` comparison can be used to test
|
|
915
|
+
# whether a key has been defined. For example, to find all objects with `owner`
|
|
916
|
+
# label use: ``` labels.owner:* ``` You can also filter nested fields. For
|
|
917
|
+
# example, you could specify `scheduling.automaticRestart = false` to include
|
|
918
|
+
# instances only if they are not scheduled for automatic restarts. You can use
|
|
919
|
+
# filtering on nested fields to filter based on resource labels. To filter on
|
|
920
|
+
# multiple expressions, provide each separate expression within parentheses. For
|
|
921
|
+
# example: ``` (scheduling.automaticRestart = true) (cpuPlatform = "Intel
|
|
922
|
+
# Skylake") ``` By default, each expression is an `AND` expression. However, you
|
|
923
|
+
# can include `AND` and `OR` expressions explicitly. For example: ``` (
|
|
924
|
+
# cpuPlatform = "Intel Skylake") OR (cpuPlatform = "Intel Broadwell") AND (
|
|
925
|
+
# scheduling.automaticRestart = true) ``` If you want to use a regular
|
|
926
|
+
# expression, use the `eq` (equal) or `ne` (not equal) operator against a single
|
|
927
|
+
# un-parenthesized expression with or without quotes or against multiple
|
|
928
|
+
# parenthesized expressions. Examples: `fieldname eq unquoted literal` `
|
|
929
|
+
# fieldname eq 'single quoted literal'` `fieldname eq "double quoted literal"` `(
|
|
930
|
+
# fieldname1 eq literal) (fieldname2 ne "literal")` The literal value is
|
|
931
|
+
# interpreted as a regular expression using Google RE2 library syntax. The
|
|
932
|
+
# literal value must match the entire field. For example, to filter for
|
|
933
|
+
# instances that do not end with name "instance", you would use `name ne .*
|
|
934
|
+
# instance`. You cannot combine constraints on multiple fields using regular
|
|
935
|
+
# expressions.
|
|
931
936
|
# @param [Fixnum] max_results
|
|
932
937
|
# The maximum number of results per page that should be returned. If the number
|
|
933
938
|
# 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_v2
|
|
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_v2/CHANGELOG.md
|
|
61
|
-
documentation_uri: https://googleapis.dev/ruby/google-apis-deploymentmanager_v2/v0.
|
|
61
|
+
documentation_uri: https://googleapis.dev/ruby/google-apis-deploymentmanager_v2/v0.27.0
|
|
62
62
|
source_code_uri: https://github.com/googleapis/google-api-ruby-client/tree/main/generated/google-apis-deploymentmanager_v2
|
|
63
63
|
post_install_message:
|
|
64
64
|
rdoc_options: []
|