client.rb in aws-sdk-secretsmanager-1.4.0

- old
+ new

@@ -269,12 +269,12 @@
     #
     # You provide the secret data to be encrypted by putting text in either
     # the `SecretString` parameter or binary data in the `SecretBinary`
     # parameter, but not both. If you include `SecretString` or
     # `SecretBinary` then Secrets Manager also creates an initial secret
-    # version and, if you don't supply a staging label, automatically maps
-    # the new version's ID to the staging label `AWSCURRENT`.
+    # version and automatically attaches the staging label `AWSCURRENT` to
+    # the new version.
     #
     # <note markdown="1"> * If you call an operation that needs to encrypt or decrypt the
     #   `SecretString` or `SecretBinary` for a secret in the same account as
     #   the calling user and that secret doesn't specify a KMS encryption
     #   key, Secrets Manager uses the account's default AWS managed
@@ -1250,11 +1250,12 @@
     end
 
     # Stores a new encrypted secret value in the specified secret. To do
     # this, the operation creates a new version and attaches it to the
     # secret. The version can contain a new `SecretString` value or a new
-    # `SecretBinary` value.
+    # `SecretBinary` value. You can also specify the staging labels that are
+    # initially attached to the new version.
     #
     # <note markdown="1"> The Secrets Manager console uses only the `SecretString` field. To add
     # binary data to a secret with the `SecretBinary` field you must use the
     # AWS CLI or one of the AWS SDKs.
     #
@@ -1264,24 +1265,25 @@
     #   Secrets Manager automatically attaches the staging label
     #   `AWSCURRENT` to the new version.
     #
     # * If another version of this secret already exists, then this
     #   operation does not automatically move any staging labels other than
-    #   those that you specify in the `VersionStages` parameter.
+    #   those that you explicitly specify in the `VersionStages` parameter.
     #
+    # * If this operation moves the staging label `AWSCURRENT` from another
+    #   version to this version (because you included it in the
+    #   `StagingLabels` parameter) then Secrets Manager also automatically
+    #   moves the staging label `AWSPREVIOUS` to the version that
+    #   `AWSCURRENT` was removed from.
+    #
     # * This operation is idempotent. If a version with a `SecretVersionId`
     #   with the same value as the `ClientRequestToken` parameter already
     #   exists and you specify the same secret data, the operation succeeds
     #   but does nothing. However, if the secret data is different, then the
     #   operation fails because you cannot modify an existing version; you
     #   can only create new ones.
     #
-    # * If this operation moves the staging label `AWSCURRENT` to this
-    #   version (because you included it in the `StagingLabels` parameter)
-    #   then Secrets Manager also automatically moves the staging label
-    #   `AWSPREVIOUS` to the version that `AWSCURRENT` was removed from.
-    #
     # <note markdown="1"> * If you call an operation that needs to encrypt or decrypt the
     #   `SecretString` or `SecretBinary` for a secret in the same account as
     #   the calling user and that secret doesn't specify a KMS encryption
     #   key, Secrets Manager uses the account's default AWS managed
     #   customer master key (CMK) with the alias `aws/secretsmanager`. If
@@ -1884,22 +1886,19 @@
     # encrypt and store binary data as part of the version of a secret, you
     # must use either the AWS CLI or one of the AWS SDKs.
     #
     #  </note>
     #
-    # * If this update creates the first version of the secret or if you did
-    #   not include the `VersionStages` parameter then Secrets Manager
-    #   automatically attaches the staging label `AWSCURRENT` to the new
-    #   version and removes it from any version that had it previously. The
-    #   previous version (if any) is then given the staging label
-    #   `AWSPREVIOUS`.
-    #
     # * If a version with a `SecretVersionId` with the same value as the
     #   `ClientRequestToken` parameter already exists, the operation
     #   generates an error. You cannot modify an existing version, you can
     #   only create new ones.
     #
+    # * If you include `SecretString` or `SecretBinary` to create a new
+    #   secret version, Secrets Manager automatically attaches the staging
+    #   label `AWSCURRENT` to the new version.
+    #
     # <note markdown="1"> * If you call an operation that needs to encrypt or decrypt the
     #   `SecretString` or `SecretBinary` for a secret in the same account as
     #   the calling user and that secret doesn't specify a KMS encryption
     #   key, Secrets Manager uses the account's default AWS managed
     #   customer master key (CMK) with the alias `aws/secretsmanager`. If
@@ -2302,10 +2301,10 @@
         operation: config.api.operation(operation_name),
         client: self,
         params: params,
         config: config)
       context[:gem_name] = 'aws-sdk-secretsmanager'
-      context[:gem_version] = '1.3.0'
+      context[:gem_version] = '1.4.0'
       Seahorse::Client::Request.new(handlers, context)
     end
 
     # @api private
     # @deprecated