aws-sdk-secretsmanager 1.1.0 → 1.2.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
  SHA1:
3
- metadata.gz: adfd3d55ac5ae5a9c37802f343b3d6285c443559
4
- data.tar.gz: 57c6b3a72a81a2125795101d9fb516114540e6f7
3
+ metadata.gz: a65a947821c77aa133bc215984a4c1878447b3a9
4
+ data.tar.gz: 7064ca3a346af57957d737c08e7b4fc7449a7afa
5
5
  SHA512:
6
- metadata.gz: 3fa42ba1efa146eccf3d3cefd69826f844219fb3b2c412ac91231878065de20d85c2c5865c1fa952386a8e5c4c5ae07ebce1ec438fc8d74a609cc3943f379711
7
- data.tar.gz: 3b07bfeb219f21c9eca866c7f46a649e14ed4cec82349d82a65c9e29862ccd9d34b96d23f3f0399689a0eeed06526ddac6defdc56a56b325e738a31e8dcadcda
6
+ metadata.gz: 430c1c77387b5bfee03cce66d8c9536b848f0eb6f3314f779441a6eb03294be777b04cbd95f1dbf4a243b25ed2e2deb7d0f2b8c42d3336a6c16d5f277ae319cb
7
+ data.tar.gz: e50f748131534f71046edacd8fc101079fb8daa56f7f0801910f9d53e0af98edbb13ff6c6cc831e4cf111e56bb698b11301174bb6af4280e4ea4c3ed07c15c7f
@@ -42,6 +42,6 @@ require_relative 'aws-sdk-secretsmanager/customizations'
42
42
  # @service
43
43
  module Aws::SecretsManager
44
44
 
45
- GEM_VERSION = '1.1.0'
45
+ GEM_VERSION = '1.2.0'
46
46
 
47
47
  end
@@ -267,24 +267,24 @@ module Aws::SecretsManager
267
267
  # versions of the secret. Versions without a staging label are
268
268
  # considered deprecated and are not included in the list.
269
269
  #
270
- # You provide the secret data to be encrypted by putting text in the
271
- # `SecretString` parameter or binary data in the `SecretBinary`
272
- # parameter. If you include `SecretString` or `SecretBinary` then
273
- # Secrets Manager also creates an initial secret version and, if you
274
- # don't supply a staging label, automatically maps the new version's
275
- # ID to the staging label `AWSCURRENT`.
270
+ # You provide the secret data to be encrypted by putting text in either
271
+ # the `SecretString` parameter or binary data in the `SecretBinary`
272
+ # parameter, but not both. If you include `SecretString` or
273
+ # `SecretBinary` then Secrets Manager also creates an initial secret
274
+ # version and, if you don't supply a staging label, automatically maps
275
+ # the new version's ID to the staging label `AWSCURRENT`.
276
276
  #
277
277
  # <note markdown="1"> * If you call an operation that needs to encrypt or decrypt the
278
- # `SecretString` and `SecretBinary` for a secret in the same account
279
- # as the calling user and that secret doesn't specify a KMS
280
- # encryption key, Secrets Manager uses the account's default AWS
281
- # managed customer master key (CMK) with the alias
282
- # `aws/secretsmanager`. If this key doesn't already exist in your
283
- # account then Secrets Manager creates it for you automatically. All
284
- # users in the same AWS account automatically have access to use the
285
- # default CMK. Note that if an Secrets Manager API call results in AWS
286
- # having to create the account's AWS-managed CMK, it can result in a
287
- # one-time significant delay in returning the result.
278
+ # `SecretString` or `SecretBinary` for a secret in the same account as
279
+ # the calling user and that secret doesn't specify a KMS encryption
280
+ # key, Secrets Manager uses the account's default AWS managed
281
+ # customer master key (CMK) with the alias `aws/secretsmanager`. If
282
+ # this key doesn't already exist in your account then Secrets Manager
283
+ # creates it for you automatically. All users in the same AWS account
284
+ # automatically have access to use the default CMK. Note that if an
285
+ # Secrets Manager API call results in AWS having to create the
286
+ # account's AWS-managed CMK, it can result in a one-time significant
287
+ # delay in returning the result.
288
288
  #
289
289
  # * If the secret is in a different AWS account from the credentials
290
290
  # calling an API that requires encryption or decryption of the secret
@@ -386,7 +386,7 @@ module Aws::SecretsManager
386
386
  #
387
387
  # @option params [String] :kms_key_id
388
388
  # (Optional) Specifies the ARN or alias of the AWS KMS customer master
389
- # key (CMK) to be used to encrypt the `SecretString` and `SecretBinary`
389
+ # key (CMK) to be used to encrypt the `SecretString` or `SecretBinary`
390
390
  # values in the versions stored in this secret.
391
391
  #
392
392
  # If you don't specify this value, then Secrets Manager defaults to
@@ -408,12 +408,8 @@ module Aws::SecretsManager
408
408
  # file and then use the appropriate technique for your tool to pass the
409
409
  # contents of the file as a parameter.
410
410
  #
411
- # Either `SecretString`, `SecretBinary`, or both must have a value. They
412
- # cannot both be empty.
413
- #
414
- # This `SecretBinary` value is stored separately from the
415
- # `SecretString`, but the two parameters jointly share a maximum size
416
- # limit.
411
+ # Either `SecretString` or `SecretBinary` must have a value, but not
412
+ # both. They cannot both be empty.
417
413
  #
418
414
  # This parameter is not available using the Secrets Manager console. It
419
415
  # can be accessed only by using the AWS CLI or one of the AWS SDKs.
@@ -422,11 +418,8 @@ module Aws::SecretsManager
422
418
  # (Optional) Specifies text data that you want to encrypt and store in
423
419
  # this new version of the secret.
424
420
  #
425
- # Either `SecretString`, `SecretBinary`, or both must have a value. They
426
- # cannot both be empty.
427
- #
428
- # This string value is stored separately from the `SecretBinary`, but
429
- # the two parameters jointly share a maximum size limit.
421
+ # Either `SecretString` or `SecretBinary` must have a value, but not
422
+ # both. They cannot both be empty.
430
423
  #
431
424
  # If you create a secret by using the Secrets Manager console then
432
425
  # Secrets Manager puts the protected secret text in only the
@@ -883,8 +876,9 @@ module Aws::SecretsManager
883
876
  req.send_request(options)
884
877
  end
885
878
 
886
- # Retrieves the contents of the encrypted fields `SecretString` and
887
- # `SecretBinary` from the specified version of a secret.
879
+ # Retrieves the contents of the encrypted fields `SecretString` or
880
+ # `SecretBinary` from the specified version of a secret, whichever
881
+ # contains content.
888
882
  #
889
883
  # **Minimum permissions**
890
884
  #
@@ -1286,16 +1280,16 @@ module Aws::SecretsManager
1286
1280
  # `AWSPREVIOUS` to the version that `AWSCURRENT` was removed from.
1287
1281
  #
1288
1282
  # <note markdown="1"> * If you call an operation that needs to encrypt or decrypt the
1289
- # `SecretString` and `SecretBinary` for a secret in the same account
1290
- # as the calling user and that secret doesn't specify a KMS
1291
- # encryption key, Secrets Manager uses the account's default AWS
1292
- # managed customer master key (CMK) with the alias
1293
- # `aws/secretsmanager`. If this key doesn't already exist in your
1294
- # account then Secrets Manager creates it for you automatically. All
1295
- # users in the same AWS account automatically have access to use the
1296
- # default CMK. Note that if an Secrets Manager API call results in AWS
1297
- # having to create the account's AWS-managed CMK, it can result in a
1298
- # one-time significant delay in returning the result.
1283
+ # `SecretString` or `SecretBinary` for a secret in the same account as
1284
+ # the calling user and that secret doesn't specify a KMS encryption
1285
+ # key, Secrets Manager uses the account's default AWS managed
1286
+ # customer master key (CMK) with the alias `aws/secretsmanager`. If
1287
+ # this key doesn't already exist in your account then Secrets Manager
1288
+ # creates it for you automatically. All users in the same AWS account
1289
+ # automatically have access to use the default CMK. Note that if an
1290
+ # Secrets Manager API call results in AWS having to create the
1291
+ # account's AWS-managed CMK, it can result in a one-time significant
1292
+ # delay in returning the result.
1299
1293
  #
1300
1294
  # * If the secret is in a different AWS account from the credentials
1301
1295
  # calling an API that requires encryption or decryption of the secret
@@ -1388,7 +1382,8 @@ module Aws::SecretsManager
1388
1382
  # command-line tools, we recommend that you store your binary data in a
1389
1383
  # file and then use the appropriate technique for your tool to pass the
1390
1384
  # contents of the file as a parameter. Either `SecretBinary` or
1391
- # `SecretString` must have a value. They cannot both be empty.
1385
+ # `SecretString` must have a value, but not both. They cannot both be
1386
+ # empty.
1392
1387
  #
1393
1388
  # This parameter is not accessible if the secret using the Secrets
1394
1389
  # Manager console.
@@ -1396,7 +1391,8 @@ module Aws::SecretsManager
1396
1391
  # @option params [String] :secret_string
1397
1392
  # (Optional) Specifies text data that you want to encrypt and store in
1398
1393
  # this new version of the secret. Either `SecretString` or
1399
- # `SecretBinary` must have a value. They cannot both be empty.
1394
+ # `SecretBinary` must have a value, but not both. They cannot both be
1395
+ # empty.
1400
1396
  #
1401
1397
  # If you create this secret by using the Secrets Manager console then
1402
1398
  # Secrets Manager puts the protected secret text in only the
@@ -1901,16 +1897,16 @@ module Aws::SecretsManager
1901
1897
  # only create new ones.
1902
1898
  #
1903
1899
  # <note markdown="1"> * If you call an operation that needs to encrypt or decrypt the
1904
- # `SecretString` and `SecretBinary` for a secret in the same account
1905
- # as the calling user and that secret doesn't specify a KMS
1906
- # encryption key, Secrets Manager uses the account's default AWS
1907
- # managed customer master key (CMK) with the alias
1908
- # `aws/secretsmanager`. If this key doesn't already exist in your
1909
- # account then Secrets Manager creates it for you automatically. All
1910
- # users in the same AWS account automatically have access to use the
1911
- # default CMK. Note that if an Secrets Manager API call results in AWS
1912
- # having to create the account's AWS-managed CMK, it can result in a
1913
- # one-time significant delay in returning the result.
1900
+ # `SecretString` or `SecretBinary` for a secret in the same account as
1901
+ # the calling user and that secret doesn't specify a KMS encryption
1902
+ # key, Secrets Manager uses the account's default AWS managed
1903
+ # customer master key (CMK) with the alias `aws/secretsmanager`. If
1904
+ # this key doesn't already exist in your account then Secrets Manager
1905
+ # creates it for you automatically. All users in the same AWS account
1906
+ # automatically have access to use the default CMK. Note that if an
1907
+ # Secrets Manager API call results in AWS having to create the
1908
+ # account's AWS-managed CMK, it can result in a one-time significant
1909
+ # delay in returning the result.
1914
1910
  #
1915
1911
  # * If the secret is in a different AWS account from the credentials
1916
1912
  # calling an API that requires encryption or decryption of the secret
@@ -2025,14 +2021,16 @@ module Aws::SecretsManager
2025
2021
  # command-line tools, we recommend that you store your binary data in a
2026
2022
  # file and then use the appropriate technique for your tool to pass the
2027
2023
  # contents of the file as a parameter. Either `SecretBinary` or
2028
- # `SecretString` must have a value. They cannot both be empty.
2024
+ # `SecretString` must have a value, but not both. They cannot both be
2025
+ # empty.
2029
2026
  #
2030
2027
  # This parameter is not accessible using the Secrets Manager console.
2031
2028
  #
2032
2029
  # @option params [String] :secret_string
2033
2030
  # (Optional) Specifies text data that you want to encrypt and store in
2034
2031
  # this new version of the secret. Either `SecretBinary` or
2035
- # `SecretString` must have a value. They cannot both be empty.
2032
+ # `SecretString` must have a value, but not both. They cannot both be
2033
+ # empty.
2036
2034
  #
2037
2035
  # If you create this secret by using the Secrets Manager console then
2038
2036
  # Secrets Manager puts the protected secret text in only the
@@ -2303,7 +2301,7 @@ module Aws::SecretsManager
2303
2301
  params: params,
2304
2302
  config: config)
2305
2303
  context[:gem_name] = 'aws-sdk-secretsmanager'
2306
- context[:gem_version] = '1.1.0'
2304
+ context[:gem_version] = '1.2.0'
2307
2305
  Seahorse::Client::Request.new(handlers, context)
2308
2306
  end
2309
2307
 
@@ -127,8 +127,8 @@ module Aws::SecretsManager
127
127
  #
128
128
  # @!attribute [rw] kms_key_id
129
129
  # (Optional) Specifies the ARN or alias of the AWS KMS customer master
130
- # key (CMK) to be used to encrypt the `SecretString` and
131
- # `SecretBinary` values in the versions stored in this secret.
130
+ # key (CMK) to be used to encrypt the `SecretString` or `SecretBinary`
131
+ # values in the versions stored in this secret.
132
132
  #
133
133
  # If you don't specify this value, then Secrets Manager defaults to
134
134
  # using the AWS account's default CMK (the one named
@@ -150,12 +150,8 @@ module Aws::SecretsManager
150
150
  # a file and then use the appropriate technique for your tool to pass
151
151
  # the contents of the file as a parameter.
152
152
  #
153
- # Either `SecretString`, `SecretBinary`, or both must have a value.
154
- # They cannot both be empty.
155
- #
156
- # This `SecretBinary` value is stored separately from the
157
- # `SecretString`, but the two parameters jointly share a maximum size
158
- # limit.
153
+ # Either `SecretString` or `SecretBinary` must have a value, but not
154
+ # both. They cannot both be empty.
159
155
  #
160
156
  # This parameter is not available using the Secrets Manager console.
161
157
  # It can be accessed only by using the AWS CLI or one of the AWS SDKs.
@@ -165,11 +161,8 @@ module Aws::SecretsManager
165
161
  # (Optional) Specifies text data that you want to encrypt and store in
166
162
  # this new version of the secret.
167
163
  #
168
- # Either `SecretString`, `SecretBinary`, or both must have a value.
169
- # They cannot both be empty.
170
- #
171
- # This string value is stored separately from the `SecretBinary`, but
172
- # the two parameters jointly share a maximum size limit.
164
+ # Either `SecretString` or `SecretBinary` must have a value, but not
165
+ # both. They cannot both be empty.
173
166
  #
174
167
  # If you create a secret by using the Secrets Manager console then
175
168
  # Secrets Manager puts the protected secret text in only the
@@ -377,7 +370,7 @@ module Aws::SecretsManager
377
370
  #
378
371
  # @!attribute [rw] kms_key_id
379
372
  # The ARN or alias of the AWS KMS customer master key (CMK) that's
380
- # used to encrypt the `SecretString` and `SecretBinary` fields in each
373
+ # used to encrypt the `SecretString` or `SecretBinary` fields in each
381
374
  # version of the secret. If you don't provide a key, then Secrets
382
375
  # Manager defaults to encrypting the secret fields with the default
383
376
  # KMS CMK (the one named `awssecretsmanager`) for this account.
@@ -896,7 +889,8 @@ module Aws::SecretsManager
896
889
  # command-line tools, we recommend that you store your binary data in
897
890
  # a file and then use the appropriate technique for your tool to pass
898
891
  # the contents of the file as a parameter. Either `SecretBinary` or
899
- # `SecretString` must have a value. They cannot both be empty.
892
+ # `SecretString` must have a value, but not both. They cannot both be
893
+ # empty.
900
894
  #
901
895
  # This parameter is not accessible if the secret using the Secrets
902
896
  # Manager console.
@@ -905,7 +899,8 @@ module Aws::SecretsManager
905
899
  # @!attribute [rw] secret_string
906
900
  # (Optional) Specifies text data that you want to encrypt and store in
907
901
  # this new version of the secret. Either `SecretString` or
908
- # `SecretBinary` must have a value. They cannot both be empty.
902
+ # `SecretBinary` must have a value, but not both. They cannot both be
903
+ # empty.
909
904
  #
910
905
  # If you create this secret by using the Secrets Manager console then
911
906
  # Secrets Manager puts the protected secret text in only the
@@ -1479,7 +1474,8 @@ module Aws::SecretsManager
1479
1474
  # command-line tools, we recommend that you store your binary data in
1480
1475
  # a file and then use the appropriate technique for your tool to pass
1481
1476
  # the contents of the file as a parameter. Either `SecretBinary` or
1482
- # `SecretString` must have a value. They cannot both be empty.
1477
+ # `SecretString` must have a value, but not both. They cannot both be
1478
+ # empty.
1483
1479
  #
1484
1480
  # This parameter is not accessible using the Secrets Manager console.
1485
1481
  # @return [String]
@@ -1487,7 +1483,8 @@ module Aws::SecretsManager
1487
1483
  # @!attribute [rw] secret_string
1488
1484
  # (Optional) Specifies text data that you want to encrypt and store in
1489
1485
  # this new version of the secret. Either `SecretBinary` or
1490
- # `SecretString` must have a value. They cannot both be empty.
1486
+ # `SecretString` must have a value, but not both. They cannot both be
1487
+ # empty.
1491
1488
  #
1492
1489
  # If you create this secret by using the Secrets Manager console then
1493
1490
  # Secrets Manager puts the protected secret text in only the
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.1.0
4
+ version: 1.2.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-19 00:00:00.000000000 Z
11
+ date: 2018-04-24 00:00:00.000000000 Z
12
12
  dependencies:
13
13
  - !ruby/object:Gem::Dependency
14
14
  name: aws-sdk-core