google-apis-deploymentmanager_v2 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: cb2bad23b10963e6f7d8d9eda0bdfee8d733884765d3ee701ec1ea6c7a411cbd
4
- data.tar.gz: 503c513729313ca50553ebc32d6392e7c695c65c4a218dcd6d6e5c6150d55372
3
+ metadata.gz: c44a615115daa9fe65ea86b320b9278bd2f6a4734eb829e58e4ce38f4b5a53aa
4
+ data.tar.gz: d7ea29e6f6821212c5b72fced9e0608522c89ff885f9e3688d6109059a0899e1
5
5
  SHA512:
6
- metadata.gz: 979c3ebc5076a7b812a66110ccd37ebbe0d840f025b3c92ab12581f90f5d521ec1c15010fc26c37ba0d347478012369ffe82bb11280fe3705bd29da04eeb92f5
7
- data.tar.gz: 1f136e10cf012476b4a2fd295b207d93936fde5266c3d6c4f43403dc5213a39b76a89c4fc7b353cb9e7e4d91f6bfc6a8f853fe55008e80cce886a9c2da1f87f5
6
+ metadata.gz: 20c7c705037a0386be0618642aa515a50414f91e4f64025d9c6a097d28ed82d882e9e73397f4d8b3a56b8289c3cc3438afdbeda5dddc3e4e151262cbce61cd19
7
+ data.tar.gz: 016073d4d750f83f584481c3575a990037863c6547fb32e407bf042ce5b260e74f64558dd7bd984559a37b0a139d7f71ef22a4e2dc7026f2ef053e42a2895a64
data/CHANGELOG.md CHANGED
@@ -1,5 +1,17 @@
1
1
  # Release history for google-apis-deploymentmanager_v2
2
2
 
3
+ ### v0.17.0 (2022-06-05)
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
@@ -35,8 +35,8 @@ module Google
35
35
  # "audit_log_configs": [ ` "log_type": "DATA_READ" `, ` "log_type": "DATA_WRITE"
36
36
  # , "exempted_members": [ "user:aliya@example.com" ] ` ] ` ] ` For sampleservice,
37
37
  # this policy enables DATA_READ, DATA_WRITE and ADMIN_READ logging. It also
38
- # exempts jose@example.com from DATA_READ logging, and aliya@example.com from
39
- # DATA_WRITE logging.
38
+ # exempts `jose@example.com` from DATA_READ logging, and `aliya@example.com`
39
+ # from DATA_WRITE logging.
40
40
  class AuditConfig
41
41
  include Google::Apis::Core::Hashable
42
42
 
@@ -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.14.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.4.1"
22
+ GENERATOR_VERSION = "0.5.0"
23
23
 
24
24
  # Revision of the discovery document this client was generated from
25
- REVISION = "20220407"
25
+ REVISION = "20220520"
26
26
  end
27
27
  end
28
28
  end
@@ -243,25 +243,36 @@ module Google
243
243
  # @param [String] project
244
244
  # The project ID for this request.
245
245
  # @param [String] filter
246
- # A filter expression that filters resources listed in the response. The
247
- # expression must specify the field name, an operator, and the value that you
248
- # want to use for filtering. The value must be a string, a number, or a boolean.
249
- # The operator must be either `=`, `!=`, `>`, `<`, `<=`, `>=` or `:`. For
250
- # example, if you are filtering Compute Engine instances, you can exclude
251
- # instances named `example-instance` by specifying `name != example-instance`.
252
- # The `:` operator can be used with string fields to match substrings. For non-
253
- # string fields it is equivalent to the `=` operator. The `:*` comparison can be
254
- # used to test whether a key has been defined. For example, to find all objects
255
- # with `owner` label use: ``` labels.owner:* ``` You can also filter nested
256
- # fields. For example, you could specify `scheduling.automaticRestart = false`
257
- # to include instances only if they are not scheduled for automatic restarts.
258
- # You can use filtering on nested fields to filter based on resource labels. To
259
- # filter on multiple expressions, provide each separate expression within
260
- # parentheses. For example: ``` (scheduling.automaticRestart = true) (
261
- # cpuPlatform = "Intel Skylake") ``` By default, each expression is an `AND`
262
- # expression. However, you can include `AND` and `OR` expressions explicitly.
263
- # For example: ``` (cpuPlatform = "Intel Skylake") OR (cpuPlatform = "Intel
264
- # Broadwell") AND (scheduling.automaticRestart = true) ```
246
+ # A filter expression that filters resources listed in the response. Most
247
+ # Compute resources support two types of filter expressions: expressions that
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
253
+ # 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`.
265
276
  # @param [Fixnum] max_results
266
277
  # The maximum number of results per page that should be returned. If the number
267
278
  # of available results is larger than `maxResults`, Compute Engine returns a `
@@ -571,25 +582,36 @@ module Google
571
582
  # @param [String] deployment
572
583
  # The name of the deployment for this request.
573
584
  # @param [String] filter
574
- # A filter expression that filters resources listed in the response. The
575
- # expression must specify the field name, an operator, and the value that you
576
- # want to use for filtering. The value must be a string, a number, or a boolean.
577
- # The operator must be either `=`, `!=`, `>`, `<`, `<=`, `>=` or `:`. For
578
- # example, if you are filtering Compute Engine instances, you can exclude
579
- # instances named `example-instance` by specifying `name != example-instance`.
580
- # The `:` operator can be used with string fields to match substrings. For non-
581
- # string fields it is equivalent to the `=` operator. The `:*` comparison can be
582
- # used to test whether a key has been defined. For example, to find all objects
583
- # with `owner` label use: ``` labels.owner:* ``` You can also filter nested
584
- # fields. For example, you could specify `scheduling.automaticRestart = false`
585
- # to include instances only if they are not scheduled for automatic restarts.
586
- # You can use filtering on nested fields to filter based on resource labels. To
587
- # filter on multiple expressions, provide each separate expression within
588
- # parentheses. For example: ``` (scheduling.automaticRestart = true) (
589
- # cpuPlatform = "Intel Skylake") ``` By default, each expression is an `AND`
590
- # expression. However, you can include `AND` and `OR` expressions explicitly.
591
- # For example: ``` (cpuPlatform = "Intel Skylake") OR (cpuPlatform = "Intel
592
- # Broadwell") AND (scheduling.automaticRestart = true) ```
585
+ # A filter expression that filters resources listed in the response. Most
586
+ # Compute resources support two types of filter expressions: expressions that
587
+ # 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
592
+ # 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`.
593
615
  # @param [Fixnum] max_results
594
616
  # The maximum number of results per page that should be returned. If the number
595
617
  # of available results is larger than `maxResults`, Compute Engine returns a `
@@ -675,25 +697,36 @@ module Google
675
697
  # @param [String] project
676
698
  # The project ID for this request.
677
699
  # @param [String] filter
678
- # A filter expression that filters resources listed in the response. The
679
- # expression must specify the field name, an operator, and the value that you
680
- # want to use for filtering. The value must be a string, a number, or a boolean.
681
- # The operator must be either `=`, `!=`, `>`, `<`, `<=`, `>=` or `:`. For
682
- # example, if you are filtering Compute Engine instances, you can exclude
683
- # instances named `example-instance` by specifying `name != example-instance`.
684
- # The `:` operator can be used with string fields to match substrings. For non-
685
- # string fields it is equivalent to the `=` operator. The `:*` comparison can be
686
- # used to test whether a key has been defined. For example, to find all objects
687
- # with `owner` label use: ``` labels.owner:* ``` You can also filter nested
688
- # fields. For example, you could specify `scheduling.automaticRestart = false`
689
- # to include instances only if they are not scheduled for automatic restarts.
690
- # You can use filtering on nested fields to filter based on resource labels. To
691
- # filter on multiple expressions, provide each separate expression within
692
- # parentheses. For example: ``` (scheduling.automaticRestart = true) (
693
- # cpuPlatform = "Intel Skylake") ``` By default, each expression is an `AND`
694
- # expression. However, you can include `AND` and `OR` expressions explicitly.
695
- # For example: ``` (cpuPlatform = "Intel Skylake") OR (cpuPlatform = "Intel
696
- # Broadwell") AND (scheduling.automaticRestart = true) ```
700
+ # A filter expression that filters resources listed in the response. Most
701
+ # Compute resources support two types of filter expressions: expressions that
702
+ # 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
707
+ # 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`.
697
730
  # @param [Fixnum] max_results
698
731
  # The maximum number of results per page that should be returned. If the number
699
732
  # of available results is larger than `maxResults`, Compute Engine returns a `
@@ -783,25 +816,36 @@ module Google
783
816
  # @param [String] deployment
784
817
  # The name of the deployment for this request.
785
818
  # @param [String] filter
786
- # A filter expression that filters resources listed in the response. The
787
- # expression must specify the field name, an operator, and the value that you
788
- # want to use for filtering. The value must be a string, a number, or a boolean.
789
- # The operator must be either `=`, `!=`, `>`, `<`, `<=`, `>=` or `:`. For
790
- # example, if you are filtering Compute Engine instances, you can exclude
791
- # instances named `example-instance` by specifying `name != example-instance`.
792
- # The `:` operator can be used with string fields to match substrings. For non-
793
- # string fields it is equivalent to the `=` operator. The `:*` comparison can be
794
- # used to test whether a key has been defined. For example, to find all objects
795
- # with `owner` label use: ``` labels.owner:* ``` You can also filter nested
796
- # fields. For example, you could specify `scheduling.automaticRestart = false`
797
- # to include instances only if they are not scheduled for automatic restarts.
798
- # You can use filtering on nested fields to filter based on resource labels. To
799
- # filter on multiple expressions, provide each separate expression within
800
- # parentheses. For example: ``` (scheduling.automaticRestart = true) (
801
- # cpuPlatform = "Intel Skylake") ``` By default, each expression is an `AND`
802
- # expression. However, you can include `AND` and `OR` expressions explicitly.
803
- # For example: ``` (cpuPlatform = "Intel Skylake") OR (cpuPlatform = "Intel
804
- # Broadwell") AND (scheduling.automaticRestart = true) ```
819
+ # A filter expression that filters resources listed in the response. Most
820
+ # Compute resources support two types of filter expressions: expressions that
821
+ # 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
826
+ # 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`.
805
849
  # @param [Fixnum] max_results
806
850
  # The maximum number of results per page that should be returned. If the number
807
851
  # of available results is larger than `maxResults`, Compute Engine returns a `
@@ -854,25 +898,36 @@ module Google
854
898
  # @param [String] project
855
899
  # The project ID for this request.
856
900
  # @param [String] filter
857
- # A filter expression that filters resources listed in the response. The
858
- # expression must specify the field name, an operator, and the value that you
859
- # want to use for filtering. The value must be a string, a number, or a boolean.
860
- # The operator must be either `=`, `!=`, `>`, `<`, `<=`, `>=` or `:`. For
861
- # example, if you are filtering Compute Engine instances, you can exclude
862
- # instances named `example-instance` by specifying `name != example-instance`.
863
- # The `:` operator can be used with string fields to match substrings. For non-
864
- # string fields it is equivalent to the `=` operator. The `:*` comparison can be
865
- # used to test whether a key has been defined. For example, to find all objects
866
- # with `owner` label use: ``` labels.owner:* ``` You can also filter nested
867
- # fields. For example, you could specify `scheduling.automaticRestart = false`
868
- # to include instances only if they are not scheduled for automatic restarts.
869
- # You can use filtering on nested fields to filter based on resource labels. To
870
- # filter on multiple expressions, provide each separate expression within
871
- # parentheses. For example: ``` (scheduling.automaticRestart = true) (
872
- # cpuPlatform = "Intel Skylake") ``` By default, each expression is an `AND`
873
- # expression. However, you can include `AND` and `OR` expressions explicitly.
874
- # For example: ``` (cpuPlatform = "Intel Skylake") OR (cpuPlatform = "Intel
875
- # Broadwell") AND (scheduling.automaticRestart = true) ```
901
+ # A filter expression that filters resources listed in the response. Most
902
+ # Compute resources support two types of filter expressions: expressions that
903
+ # 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
+ # 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`.
876
931
  # @param [Fixnum] max_results
877
932
  # The maximum number of results per page that should be returned. If the number
878
933
  # 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.14.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-04-18 00:00:00.000000000 Z
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.4'
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.4'
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_v2/CHANGELOG.md
61
- documentation_uri: https://googleapis.dev/ruby/google-apis-deploymentmanager_v2/v0.14.0
61
+ documentation_uri: https://googleapis.dev/ruby/google-apis-deploymentmanager_v2/v0.17.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: []
@@ -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 V2