google-apis-deploymentmanager_v2 0.25.0 → 0.26.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: 4194efbf16e5d6880353950bd1d28effc494f9d03699f41325aae391c91693ee
4
- data.tar.gz: e57edb80edb62c6b8bf729d068227a219959d30ff6c5cd34d3188e4708b69e6a
3
+ metadata.gz: eb509ed5f0c956c5834b73855a307b7b02ef7d1c356d0527c74fb96ffb8bf00d
4
+ data.tar.gz: 2c6530415ce2cd74c8e1a15bd1e6210fd4ff3fb5cb85c323b4dde1c91584eda3
5
5
  SHA512:
6
- metadata.gz: f721c2199fd874f0501f0b6c31b121f788b0e41d4c2eddd4e756e731a7093b9697c80669c0249633aaa0d95f124b1ec00bb668821fbe5bacf0eaa0038b875823
7
- data.tar.gz: 9f8613c65b1853880086d333e196709280f69919983cf540a0cac259dcbcbf598779b6a64060bf5e0974239d4a8776225f9075dd946dcb611f1c6868ccc1a1b6
6
+ metadata.gz: 9fef573db80f41066009f1b69807c12fbe442f8358ef17cb40669bab5bcc8c58d84dea8e2f6788768efbf797a5f3bf58477fc16f528797143c206233708092fa
7
+ data.tar.gz: 49a18b84fd607c0d43d3c4666f73fc88c0b5fa7416357d7d36e033215546b4ada6215c054b1ffd80ce822410e96f3579ec2ffd2726e1069f737b9adc347b5e0c
data/CHANGELOG.md CHANGED
@@ -1,5 +1,9 @@
1
1
  # Release history for google-apis-deploymentmanager_v2
2
2
 
3
+ ### v0.26.0 (2023-10-01)
4
+
5
+ * Regenerated from discovery document revision 20230921
6
+
3
7
  ### v0.25.0 (2023-08-27)
4
8
 
5
9
  * Regenerated from discovery document revision 20230821
@@ -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.25.0"
19
+ GEM_VERSION = "0.26.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 = "20230821"
25
+ REVISION = "20230921"
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. If you want to use AIP-160, your expression must specify the
250
- # field name, an operator, and the value that you want to use for filtering. The
251
- # value must be a string, a number, or a boolean. The operator must be either `=`
252
- # , `!=`, `>`, `<`, `<=`, `>=` or `:`. For example, if you are filtering Compute
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 `:` operator can be used with
255
- # string fields to match substrings. For non-string fields it is equivalent to
256
- # the `=` operator. The `:*` comparison can be used to test whether a key has
257
- # been defined. For example, to find all objects with `owner` label use: ```
258
- # labels.owner:* ``` You can also filter nested fields. For example, you could
259
- # specify `scheduling.automaticRestart = false` to include instances only if
260
- # they are not scheduled for automatic restarts. You can use filtering on nested
261
- # fields to filter based on resource labels. To filter on multiple expressions,
262
- # provide each separate expression within parentheses. For example: ``` (
263
- # scheduling.automaticRestart = true) (cpuPlatform = "Intel Skylake") ``` By
264
- # default, each expression is an `AND` expression. However, you can include `AND`
265
- # and `OR` expressions explicitly. For example: ``` (cpuPlatform = "Intel
266
- # Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.
267
- # automaticRestart = true) ``` If you want to use a regular expression, use the `
268
- # eq` (equal) or `ne` (not equal) operator against a single un-parenthesized
269
- # expression with or without quotes or against multiple parenthesized
270
- # expressions. Examples: `fieldname eq unquoted literal` `fieldname eq 'single
271
- # quoted literal'` `fieldname eq "double quoted literal"` `(fieldname1 eq
272
- # literal) (fieldname2 ne "literal")` The literal value is interpreted as a
273
- # regular expression using Google RE2 library syntax. The literal value must
274
- # match the entire field. For example, to filter for instances that do not end
275
- # with name "instance", you would use `name ne .*instance`.
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. If you want to use AIP-160, your expression must specify the
589
- # field name, an operator, and the value that you want to use for filtering. The
590
- # value must be a string, a number, or a boolean. The operator must be either `=`
591
- # , `!=`, `>`, `<`, `<=`, `>=` or `:`. For example, if you are filtering Compute
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 `:` operator can be used with
594
- # string fields to match substrings. For non-string fields it is equivalent to
595
- # the `=` operator. The `:*` comparison can be used to test whether a key has
596
- # been defined. For example, to find all objects with `owner` label use: ```
597
- # labels.owner:* ``` You can also filter nested fields. For example, you could
598
- # specify `scheduling.automaticRestart = false` to include instances only if
599
- # they are not scheduled for automatic restarts. You can use filtering on nested
600
- # fields to filter based on resource labels. To filter on multiple expressions,
601
- # provide each separate expression within parentheses. For example: ``` (
602
- # scheduling.automaticRestart = true) (cpuPlatform = "Intel Skylake") ``` By
603
- # default, each expression is an `AND` expression. However, you can include `AND`
604
- # and `OR` expressions explicitly. For example: ``` (cpuPlatform = "Intel
605
- # Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.
606
- # automaticRestart = true) ``` If you want to use a regular expression, use the `
607
- # eq` (equal) or `ne` (not equal) operator against a single un-parenthesized
608
- # expression with or without quotes or against multiple parenthesized
609
- # expressions. Examples: `fieldname eq unquoted literal` `fieldname eq 'single
610
- # quoted literal'` `fieldname eq "double quoted literal"` `(fieldname1 eq
611
- # literal) (fieldname2 ne "literal")` The literal value is interpreted as a
612
- # regular expression using Google RE2 library syntax. The literal value must
613
- # match the entire field. For example, to filter for instances that do not end
614
- # with name "instance", you would use `name ne .*instance`.
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. If you want to use AIP-160, your expression must specify the
704
- # field name, an operator, and the value that you want to use for filtering. The
705
- # value must be a string, a number, or a boolean. The operator must be either `=`
706
- # , `!=`, `>`, `<`, `<=`, `>=` or `:`. For example, if you are filtering Compute
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 `:` operator can be used with
709
- # string fields to match substrings. For non-string fields it is equivalent to
710
- # the `=` operator. The `:*` comparison can be used to test whether a key has
711
- # been defined. For example, to find all objects with `owner` label use: ```
712
- # labels.owner:* ``` You can also filter nested fields. For example, you could
713
- # specify `scheduling.automaticRestart = false` to include instances only if
714
- # they are not scheduled for automatic restarts. You can use filtering on nested
715
- # fields to filter based on resource labels. To filter on multiple expressions,
716
- # provide each separate expression within parentheses. For example: ``` (
717
- # scheduling.automaticRestart = true) (cpuPlatform = "Intel Skylake") ``` By
718
- # default, each expression is an `AND` expression. However, you can include `AND`
719
- # and `OR` expressions explicitly. For example: ``` (cpuPlatform = "Intel
720
- # Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.
721
- # automaticRestart = true) ``` If you want to use a regular expression, use the `
722
- # eq` (equal) or `ne` (not equal) operator against a single un-parenthesized
723
- # expression with or without quotes or against multiple parenthesized
724
- # expressions. Examples: `fieldname eq unquoted literal` `fieldname eq 'single
725
- # quoted literal'` `fieldname eq "double quoted literal"` `(fieldname1 eq
726
- # literal) (fieldname2 ne "literal")` The literal value is interpreted as a
727
- # regular expression using Google RE2 library syntax. The literal value must
728
- # match the entire field. For example, to filter for instances that do not end
729
- # with name "instance", you would use `name ne .*instance`.
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. If you want to use AIP-160, your expression must specify the
823
- # field name, an operator, and the value that you want to use for filtering. The
824
- # value must be a string, a number, or a boolean. The operator must be either `=`
825
- # , `!=`, `>`, `<`, `<=`, `>=` or `:`. For example, if you are filtering Compute
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 `:` operator can be used with
828
- # string fields to match substrings. For non-string fields it is equivalent to
829
- # the `=` operator. The `:*` comparison can be used to test whether a key has
830
- # been defined. For example, to find all objects with `owner` label use: ```
831
- # labels.owner:* ``` You can also filter nested fields. For example, you could
832
- # specify `scheduling.automaticRestart = false` to include instances only if
833
- # they are not scheduled for automatic restarts. You can use filtering on nested
834
- # fields to filter based on resource labels. To filter on multiple expressions,
835
- # provide each separate expression within parentheses. For example: ``` (
836
- # scheduling.automaticRestart = true) (cpuPlatform = "Intel Skylake") ``` By
837
- # default, each expression is an `AND` expression. However, you can include `AND`
838
- # and `OR` expressions explicitly. For example: ``` (cpuPlatform = "Intel
839
- # Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.
840
- # automaticRestart = true) ``` If you want to use a regular expression, use the `
841
- # eq` (equal) or `ne` (not equal) operator against a single un-parenthesized
842
- # expression with or without quotes or against multiple parenthesized
843
- # expressions. Examples: `fieldname eq unquoted literal` `fieldname eq 'single
844
- # quoted literal'` `fieldname eq "double quoted literal"` `(fieldname1 eq
845
- # literal) (fieldname2 ne "literal")` The literal value is interpreted as a
846
- # regular expression using Google RE2 library syntax. The literal value must
847
- # match the entire field. For example, to filter for instances that do not end
848
- # with name "instance", you would use `name ne .*instance`.
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. If you want to use AIP-160, your expression must specify the
905
- # field name, an operator, and the value that you want to use for filtering. The
906
- # value must be a string, a number, or a boolean. The operator must be either `=`
907
- # , `!=`, `>`, `<`, `<=`, `>=` or `:`. For example, if you are filtering Compute
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 `:` operator can be used with
910
- # string fields to match substrings. For non-string fields it is equivalent to
911
- # the `=` operator. The `:*` comparison can be used to test whether a key has
912
- # been defined. For example, to find all objects with `owner` label use: ```
913
- # labels.owner:* ``` You can also filter nested fields. For example, you could
914
- # specify `scheduling.automaticRestart = false` to include instances only if
915
- # they are not scheduled for automatic restarts. You can use filtering on nested
916
- # fields to filter based on resource labels. To filter on multiple expressions,
917
- # provide each separate expression within parentheses. For example: ``` (
918
- # scheduling.automaticRestart = true) (cpuPlatform = "Intel Skylake") ``` By
919
- # default, each expression is an `AND` expression. However, you can include `AND`
920
- # and `OR` expressions explicitly. For example: ``` (cpuPlatform = "Intel
921
- # Skylake") OR (cpuPlatform = "Intel Broadwell") AND (scheduling.
922
- # automaticRestart = true) ``` If you want to use a regular expression, use the `
923
- # eq` (equal) or `ne` (not equal) operator against a single un-parenthesized
924
- # expression with or without quotes or against multiple parenthesized
925
- # expressions. Examples: `fieldname eq unquoted literal` `fieldname eq 'single
926
- # quoted literal'` `fieldname eq "double quoted literal"` `(fieldname1 eq
927
- # literal) (fieldname2 ne "literal")` The literal value is interpreted as a
928
- # regular expression using Google RE2 library syntax. The literal value must
929
- # match the entire field. For example, to filter for instances that do not end
930
- # with name "instance", you would use `name ne .*instance`.
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.25.0
4
+ version: 0.26.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-08-27 00:00:00.000000000 Z
11
+ date: 2023-10-01 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.25.0
61
+ documentation_uri: https://googleapis.dev/ruby/google-apis-deploymentmanager_v2/v0.26.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: []