aws-sdk-secretsmanager 1.2.0 → 1.3.0
Sign up to get free protection for your applications and to get access to all the features.
- checksums.yaml +4 -4
- data/lib/aws-sdk-secretsmanager.rb +1 -1
- data/lib/aws-sdk-secretsmanager/client.rb +8 -5
- metadata +3 -3
checksums.yaml
CHANGED
@@ -1,7 +1,7 @@
|
|
1
1
|
---
|
2
2
|
SHA1:
|
3
|
-
metadata.gz:
|
4
|
-
data.tar.gz:
|
3
|
+
metadata.gz: 9b5d50862e1753f7912719d144dfa9c6b6d3a6aa
|
4
|
+
data.tar.gz: 386928c5bcaba009f9ce62c15fa25eaa0d481b4b
|
5
5
|
SHA512:
|
6
|
-
metadata.gz:
|
7
|
-
data.tar.gz:
|
6
|
+
metadata.gz: e03a3419c1f76afd448bfa73eba0ca659a328b6b89d781453bafc5081184159eb064631fb962e2f189313c4c49400a666d03579626e367189e3f5ee03a4a4ce8
|
7
|
+
data.tar.gz: d33a2a8724354c6273a4bb02660bd892b0dec94d6e36921ae6cfd9be7022a0635d32db03e4a3328ca803cd1893ac9528b9a75d4e3d2ec3516568c0c710ae04ae
|
@@ -295,7 +295,8 @@ module Aws::SecretsManager
|
|
295
295
|
# `KMSKeyId`. If you call an API that must encrypt or decrypt
|
296
296
|
# `SecretString` or `SecretBinary` using credentials from a different
|
297
297
|
# account then the KMS key policy must grant cross-account access to
|
298
|
-
# that other account's user or role
|
298
|
+
# that other account's user or role for both the kms:GenerateDataKey
|
299
|
+
# and kms:Decrypt operations.
|
299
300
|
#
|
300
301
|
# </note>
|
301
302
|
#
|
@@ -311,7 +312,7 @@ module Aws::SecretsManager
|
|
311
312
|
# key to encrypt the secret. You do not need this permission to use
|
312
313
|
# the account's default AWS managed CMK for Secrets Manager.
|
313
314
|
#
|
314
|
-
# * kms:
|
315
|
+
# * kms:Decrypt - needed only if you use a customer-created KMS key to
|
315
316
|
# encrypt the secret. You do not need this permission to use the
|
316
317
|
# account's default AWS managed CMK for Secrets Manager.
|
317
318
|
#
|
@@ -1300,7 +1301,8 @@ module Aws::SecretsManager
|
|
1300
1301
|
# `KMSKeyId`. If you call an API that must encrypt or decrypt
|
1301
1302
|
# `SecretString` or `SecretBinary` using credentials from a different
|
1302
1303
|
# account then the KMS key policy must grant cross-account access to
|
1303
|
-
# that other account's user or role
|
1304
|
+
# that other account's user or role for both the kms:GenerateDataKey
|
1305
|
+
# and kms:Decrypt operations.
|
1304
1306
|
#
|
1305
1307
|
# </note>
|
1306
1308
|
#
|
@@ -1917,7 +1919,8 @@ module Aws::SecretsManager
|
|
1917
1919
|
# `KMSKeyId`. If you call an API that must encrypt or decrypt
|
1918
1920
|
# `SecretString` or `SecretBinary` using credentials from a different
|
1919
1921
|
# account then the KMS key policy must grant cross-account access to
|
1920
|
-
# that other account's user or role
|
1922
|
+
# that other account's user or role for both the kms:GenerateDataKey
|
1923
|
+
# and kms:Decrypt operations.
|
1921
1924
|
#
|
1922
1925
|
# </note>
|
1923
1926
|
#
|
@@ -2301,7 +2304,7 @@ module Aws::SecretsManager
|
|
2301
2304
|
params: params,
|
2302
2305
|
config: config)
|
2303
2306
|
context[:gem_name] = 'aws-sdk-secretsmanager'
|
2304
|
-
context[:gem_version] = '1.
|
2307
|
+
context[:gem_version] = '1.3.0'
|
2305
2308
|
Seahorse::Client::Request.new(handlers, context)
|
2306
2309
|
end
|
2307
2310
|
|
metadata
CHANGED
@@ -1,14 +1,14 @@
|
|
1
1
|
--- !ruby/object:Gem::Specification
|
2
2
|
name: aws-sdk-secretsmanager
|
3
3
|
version: !ruby/object:Gem::Version
|
4
|
-
version: 1.
|
4
|
+
version: 1.3.0
|
5
5
|
platform: ruby
|
6
6
|
authors:
|
7
7
|
- Amazon Web Services
|
8
8
|
autorequire:
|
9
9
|
bindir: bin
|
10
10
|
cert_chain: []
|
11
|
-
date: 2018-04-
|
11
|
+
date: 2018-04-26 00:00:00.000000000 Z
|
12
12
|
dependencies:
|
13
13
|
- !ruby/object:Gem::Dependency
|
14
14
|
name: aws-sdk-core
|
@@ -75,7 +75,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
|
|
75
75
|
version: '0'
|
76
76
|
requirements: []
|
77
77
|
rubyforge_project:
|
78
|
-
rubygems_version: 2.5.2.
|
78
|
+
rubygems_version: 2.5.2.3
|
79
79
|
signing_key:
|
80
80
|
specification_version: 4
|
81
81
|
summary: AWS SDK for Ruby - AWS Secrets Manager
|