aws-sdk-secretsmanager 1.101.0 → 1.102.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: 27aba913be3847849aa610964d15ee3b5fca875fae22d51df856c81d1e653da4
4
- data.tar.gz: eed6bb159ff151a94fa16331e1882c7fa3b4ad23be00c8e1721ed561d00de088
3
+ metadata.gz: 50f7a307d3cf7e170b14c7c82003a213df54c39cb4ef1362439c98b1bb8975fb
4
+ data.tar.gz: f582e643ce4cedebc497bf2d4b5dbe1df20e1e46093eb7acff75202bcd351e0f
5
5
  SHA512:
6
- metadata.gz: df812f193a3284a5141a9a4a4242b0d657fcc02f90d7a3b8802a9414753f139802b5e305825e9ee852628c49072a5eb465380294e72fcb22adffaeb59eda3a1a
7
- data.tar.gz: d8e1e0b617ab53e9ad8cfc202b9f6f283e8a156d9f7c96792631dd8e313531e290e1f6b0ef3ac5221a998a9b5f788bf7a15b940fc1b349c8351243ccf060b7c9
6
+ metadata.gz: b2090771993d6af8f722c35db483af31fe92513907c358a2faddedfcde98d52e017df49d29550a36da745b3943d98273c5ab72e86fc3e2fa05a66fcf7d06d296
7
+ data.tar.gz: f921d379077a4522b8982ae7e0328fdadb73909152cfc0c681a442a766fe7e6214ded88dd8903918cf23f50dca640782b3dc73c63ca5026b85fc9f4b65b8614e
data/CHANGELOG.md CHANGED
@@ -1,6 +1,11 @@
1
1
  Unreleased Changes
2
2
  ------------------
3
3
 
4
+ 1.102.0 (2024-07-18)
5
+ ------------------
6
+
7
+ * Feature - Doc only update for Secrets Manager
8
+
4
9
  1.101.0 (2024-07-02)
5
10
  ------------------
6
11
 
data/VERSION CHANGED
@@ -1 +1 @@
1
- 1.101.0
1
+ 1.102.0
@@ -724,6 +724,12 @@ module Aws::SecretsManager
724
724
  # you need `kms:GenerateDataKey` and `kms:Decrypt` permission to the
725
725
  # key.
726
726
  #
727
+ # When you enter commands in a command shell, there is a risk of the
728
+ # command history being accessed or utilities having access to your
729
+ # command parameters. This is a concern if the command includes the
730
+ # value of a secret. Learn how to [Mitigate the risks of using
731
+ # command-line tools to store Secrets Manager secrets][7].
732
+ #
727
733
  #
728
734
  #
729
735
  # [1]: https://docs.aws.amazon.com/secretsmanager/latest/userguide/service-linked-secrets.html
@@ -732,6 +738,7 @@ module Aws::SecretsManager
732
738
  # [4]: https://docs.aws.amazon.com/secretsmanager/latest/userguide/retrieve-ct-entries.html
733
739
  # [5]: https://docs.aws.amazon.com/secretsmanager/latest/userguide/reference_iam-permissions.html#reference_iam-permissions_actions
734
740
  # [6]: https://docs.aws.amazon.com/secretsmanager/latest/userguide/auth-and-access.html
741
+ # [7]: https://docs.aws.amazon.com/secretsmanager/latest/userguide/security_cli-exposure-risks.html
735
742
  #
736
743
  # @option params [required, String] :name
737
744
  # The name of the new secret.
@@ -2038,11 +2045,18 @@ module Aws::SecretsManager
2038
2045
  # more information, see [ IAM policy actions for Secrets Manager][2] and
2039
2046
  # [Authentication and access control in Secrets Manager][3].
2040
2047
  #
2048
+ # When you enter commands in a command shell, there is a risk of the
2049
+ # command history being accessed or utilities having access to your
2050
+ # command parameters. This is a concern if the command includes the
2051
+ # value of a secret. Learn how to [Mitigate the risks of using
2052
+ # command-line tools to store Secrets Manager secrets][4].
2053
+ #
2041
2054
  #
2042
2055
  #
2043
2056
  # [1]: https://docs.aws.amazon.com/secretsmanager/latest/userguide/retrieve-ct-entries.html
2044
2057
  # [2]: https://docs.aws.amazon.com/secretsmanager/latest/userguide/reference_iam-permissions.html#reference_iam-permissions_actions
2045
2058
  # [3]: https://docs.aws.amazon.com/secretsmanager/latest/userguide/auth-and-access.html
2059
+ # [4]: https://docs.aws.amazon.com/secretsmanager/latest/userguide/security_cli-exposure-risks.html
2046
2060
  #
2047
2061
  # @option params [required, String] :secret_id
2048
2062
  # The ARN or name of the secret to add a new version to.
@@ -2891,10 +2905,16 @@ module Aws::SecretsManager
2891
2905
  # a customer managed key, you must also have `kms:GenerateDataKey`,
2892
2906
  # `kms:Encrypt`, and `kms:Decrypt` permissions on the key. If you change
2893
2907
  # the KMS key and you don't have `kms:Encrypt` permission to the new
2894
- # key, Secrets Manager does not re-ecrypt existing secret versions with
2908
+ # key, Secrets Manager does not re-encrypt existing secret versions with
2895
2909
  # the new key. For more information, see [ Secret encryption and
2896
2910
  # decryption][5].
2897
2911
  #
2912
+ # When you enter commands in a command shell, there is a risk of the
2913
+ # command history being accessed or utilities having access to your
2914
+ # command parameters. This is a concern if the command includes the
2915
+ # value of a secret. Learn how to [Mitigate the risks of using
2916
+ # command-line tools to store Secrets Manager secrets][6].
2917
+ #
2898
2918
  #
2899
2919
  #
2900
2920
  # [1]: https://docs.aws.amazon.com/secretsmanager/latest/userguide/service-linked-secrets.html
@@ -2902,6 +2922,7 @@ module Aws::SecretsManager
2902
2922
  # [3]: https://docs.aws.amazon.com/secretsmanager/latest/userguide/reference_iam-permissions.html#reference_iam-permissions_actions
2903
2923
  # [4]: https://docs.aws.amazon.com/secretsmanager/latest/userguide/auth-and-access.html
2904
2924
  # [5]: https://docs.aws.amazon.com/secretsmanager/latest/userguide/security-encryption.html
2925
+ # [6]: https://docs.aws.amazon.com/secretsmanager/latest/userguide/security_cli-exposure-risks.html
2905
2926
  #
2906
2927
  # @option params [required, String] :secret_id
2907
2928
  # The ARN or name of the secret.
@@ -2950,8 +2971,8 @@ module Aws::SecretsManager
2950
2971
  # encrypt new secret versions as well as any existing versions with the
2951
2972
  # staging labels `AWSCURRENT`, `AWSPENDING`, or `AWSPREVIOUS`. If you
2952
2973
  # don't have `kms:Encrypt` permission to the new key, Secrets Manager
2953
- # does not re-ecrypt existing secret versions with the new key. For more
2954
- # information about versions and staging labels, see [Concepts:
2974
+ # does not re-encrypt existing secret versions with the new key. For
2975
+ # more information about versions and staging labels, see [Concepts:
2955
2976
  # Version][1].
2956
2977
  #
2957
2978
  # A key alias is always prefixed by `alias/`, for example
@@ -3347,7 +3368,7 @@ module Aws::SecretsManager
3347
3368
  params: params,
3348
3369
  config: config)
3349
3370
  context[:gem_name] = 'aws-sdk-secretsmanager'
3350
- context[:gem_version] = '1.101.0'
3371
+ context[:gem_version] = '1.102.0'
3351
3372
  Seahorse::Client::Request.new(handlers, context)
3352
3373
  end
3353
3374
 
@@ -2266,7 +2266,7 @@ module Aws::SecretsManager
2266
2266
  # to encrypt new secret versions as well as any existing versions with
2267
2267
  # the staging labels `AWSCURRENT`, `AWSPENDING`, or `AWSPREVIOUS`. If
2268
2268
  # you don't have `kms:Encrypt` permission to the new key, Secrets
2269
- # Manager does not re-ecrypt existing secret versions with the new
2269
+ # Manager does not re-encrypt existing secret versions with the new
2270
2270
  # key. For more information about versions and staging labels, see
2271
2271
  # [Concepts: Version][1].
2272
2272
  #
@@ -52,6 +52,6 @@ require_relative 'aws-sdk-secretsmanager/customizations'
52
52
  # @!group service
53
53
  module Aws::SecretsManager
54
54
 
55
- GEM_VERSION = '1.101.0'
55
+ GEM_VERSION = '1.102.0'
56
56
 
57
57
  end
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.101.0
4
+ version: 1.102.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: 2024-07-02 00:00:00.000000000 Z
11
+ date: 2024-07-18 00:00:00.000000000 Z
12
12
  dependencies:
13
13
  - !ruby/object:Gem::Dependency
14
14
  name: aws-sdk-core