google-apis-deploymentmanager_v2 0.10.0 → 0.11.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: e28d375d7f0adcdf5f6b34c48e8f2db40256001c128b2f7ac173fdf67d2d3860
|
4
|
+
data.tar.gz: 0c2f8a0c30b16af11f63a5b66c5f5fa09ab7d375271a3646c64a62ffa47ea4b5
|
5
5
|
SHA512:
|
6
|
-
metadata.gz:
|
7
|
-
data.tar.gz:
|
6
|
+
metadata.gz: 1c20ac04463cb762f4e4333f3e1919fdcf1014f0b8106f16889edad9e453f0460d6a63054735868c3661b57accfddbc367d57b930b1c40959304ec8273cf0aa3
|
7
|
+
data.tar.gz: daf4213fafc79ca7faf4f4c65003003aee8472ab4a4c070535da2f4f35f0b0e7cc37b1cc570b572e07428a9476497dc279f0ea57c738fa4cc2f7a0344964e108
|
data/CHANGELOG.md
CHANGED
@@ -1075,7 +1075,12 @@ module Google
|
|
1075
1075
|
|
1076
1076
|
# Associates a list of `members` to a `role`. Optionally, may specify a `
|
1077
1077
|
# condition` that determines how and when the `bindings` are applied. Each of
|
1078
|
-
# the `bindings` must contain at least one member.
|
1078
|
+
# the `bindings` must contain at least one member. The `bindings` in a `Policy`
|
1079
|
+
# can refer to up to 1,500 members; up to 250 of these members can be Google
|
1080
|
+
# groups. Each occurrence of a member counts towards these limits. For example,
|
1081
|
+
# if the `bindings` grant 50 different roles to `user:alice@example.com`, and
|
1082
|
+
# not to any other member, then you can add another 1,450 members to the `
|
1083
|
+
# bindings` in the `Policy`.
|
1079
1084
|
# Corresponds to the JSON property `bindings`
|
1080
1085
|
# @return [Array<Google::Apis::DeploymentmanagerV2::Binding>]
|
1081
1086
|
attr_accessor :bindings
|
@@ -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.11.0"
|
20
20
|
|
21
21
|
# Version of the code generator used to generate this client
|
22
22
|
GENERATOR_VERSION = "0.4.0"
|
23
23
|
|
24
24
|
# Revision of the discovery document this client was generated from
|
25
|
-
REVISION = "
|
25
|
+
REVISION = "20210930"
|
26
26
|
end
|
27
27
|
end
|
28
28
|
end
|
@@ -244,20 +244,24 @@ module Google
|
|
244
244
|
# The project ID for this request.
|
245
245
|
# @param [String] filter
|
246
246
|
# A filter expression that filters resources listed in the response. The
|
247
|
-
# expression must specify the field name,
|
248
|
-
#
|
249
|
-
#
|
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
250
|
# example, if you are filtering Compute Engine instances, you can exclude
|
251
251
|
# instances named `example-instance` by specifying `name != example-instance`.
|
252
|
-
#
|
253
|
-
#
|
254
|
-
#
|
255
|
-
#
|
256
|
-
#
|
257
|
-
#
|
258
|
-
#
|
259
|
-
#
|
260
|
-
#
|
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) ```
|
261
265
|
# @param [Fixnum] max_results
|
262
266
|
# The maximum number of results per page that should be returned. If the number
|
263
267
|
# of available results is larger than `maxResults`, Compute Engine returns a `
|
@@ -568,20 +572,24 @@ module Google
|
|
568
572
|
# The name of the deployment for this request.
|
569
573
|
# @param [String] filter
|
570
574
|
# A filter expression that filters resources listed in the response. The
|
571
|
-
# expression must specify the field name,
|
572
|
-
#
|
573
|
-
#
|
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
|
574
578
|
# example, if you are filtering Compute Engine instances, you can exclude
|
575
579
|
# instances named `example-instance` by specifying `name != example-instance`.
|
576
|
-
#
|
577
|
-
#
|
578
|
-
#
|
579
|
-
#
|
580
|
-
#
|
581
|
-
#
|
582
|
-
#
|
583
|
-
#
|
584
|
-
#
|
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
593
|
# @param [Fixnum] max_results
|
586
594
|
# The maximum number of results per page that should be returned. If the number
|
587
595
|
# of available results is larger than `maxResults`, Compute Engine returns a `
|
@@ -668,20 +676,24 @@ module Google
|
|
668
676
|
# The project ID for this request.
|
669
677
|
# @param [String] filter
|
670
678
|
# A filter expression that filters resources listed in the response. The
|
671
|
-
# expression must specify the field name,
|
672
|
-
#
|
673
|
-
#
|
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
|
674
682
|
# example, if you are filtering Compute Engine instances, you can exclude
|
675
683
|
# instances named `example-instance` by specifying `name != example-instance`.
|
676
|
-
#
|
677
|
-
#
|
678
|
-
#
|
679
|
-
#
|
680
|
-
#
|
681
|
-
#
|
682
|
-
#
|
683
|
-
#
|
684
|
-
#
|
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) ```
|
685
697
|
# @param [Fixnum] max_results
|
686
698
|
# The maximum number of results per page that should be returned. If the number
|
687
699
|
# of available results is larger than `maxResults`, Compute Engine returns a `
|
@@ -772,20 +784,24 @@ module Google
|
|
772
784
|
# The name of the deployment for this request.
|
773
785
|
# @param [String] filter
|
774
786
|
# A filter expression that filters resources listed in the response. The
|
775
|
-
# expression must specify the field name,
|
776
|
-
#
|
777
|
-
#
|
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
|
778
790
|
# example, if you are filtering Compute Engine instances, you can exclude
|
779
791
|
# instances named `example-instance` by specifying `name != example-instance`.
|
780
|
-
#
|
781
|
-
#
|
782
|
-
#
|
783
|
-
#
|
784
|
-
#
|
785
|
-
#
|
786
|
-
#
|
787
|
-
#
|
788
|
-
#
|
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) ```
|
789
805
|
# @param [Fixnum] max_results
|
790
806
|
# The maximum number of results per page that should be returned. If the number
|
791
807
|
# of available results is larger than `maxResults`, Compute Engine returns a `
|
@@ -839,20 +855,24 @@ module Google
|
|
839
855
|
# The project ID for this request.
|
840
856
|
# @param [String] filter
|
841
857
|
# A filter expression that filters resources listed in the response. The
|
842
|
-
# expression must specify the field name,
|
843
|
-
#
|
844
|
-
#
|
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
|
845
861
|
# example, if you are filtering Compute Engine instances, you can exclude
|
846
862
|
# instances named `example-instance` by specifying `name != example-instance`.
|
847
|
-
#
|
848
|
-
#
|
849
|
-
#
|
850
|
-
#
|
851
|
-
#
|
852
|
-
#
|
853
|
-
#
|
854
|
-
#
|
855
|
-
#
|
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) ```
|
856
876
|
# @param [Fixnum] max_results
|
857
877
|
# The maximum number of results per page that should be returned. If the number
|
858
878
|
# 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.11.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: 2021-
|
11
|
+
date: 2021-10-11 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/master/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.11.0
|
62
62
|
source_code_uri: https://github.com/googleapis/google-api-ruby-client/tree/master/generated/google-apis-deploymentmanager_v2
|
63
63
|
post_install_message:
|
64
64
|
rdoc_options: []
|