aws-sdk-secretsmanager 1.3.0 → 1.4.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 9b5d50862e1753f7912719d144dfa9c6b6d3a6aa
-  data.tar.gz: 386928c5bcaba009f9ce62c15fa25eaa0d481b4b
+  metadata.gz: 2f17237570f95842390c4f41ba74d2c68148a07e
+  data.tar.gz: d1d0f97ae02f336614827ce6a9ceb7d381c6d083
 SHA512:
-  metadata.gz: e03a3419c1f76afd448bfa73eba0ca659a328b6b89d781453bafc5081184159eb064631fb962e2f189313c4c49400a666d03579626e367189e3f5ee03a4a4ce8
-  data.tar.gz: d33a2a8724354c6273a4bb02660bd892b0dec94d6e36921ae6cfd9be7022a0635d32db03e4a3328ca803cd1893ac9528b9a75d4e3d2ec3516568c0c710ae04ae
+  metadata.gz: 7037266f1cd9e210ac1a4b6ba1b1a9ade064617a63b2f78bbd40db4912bb7e260952eb26d731940ffc60e57135f708d4665ad8140f75989b2499274dd31ed113
+  data.tar.gz: 7eee3de54d702b3889516af345f9d433465f71d8a9da37a8c59c64db734c8fdbddc3c51f6934e8fc9ebc800b8f945e3a5af862172bfa83dda8d9fae402b74828

data/lib/aws-sdk-secretsmanager.rb

@@ -42,6 +42,6 @@ require_relative 'aws-sdk-secretsmanager/customizations'
 # @service
 module Aws::SecretsManager
 
-  GEM_VERSION = '1.3.0'
+  GEM_VERSION = '1.4.0'
 
 end

data/lib/aws-sdk-secretsmanager/client.rb

@@ -271,8 +271,8 @@ module Aws::SecretsManager
     # 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
@@ -1252,7 +1252,8 @@ module Aws::SecretsManager
     # 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
@@ -1266,7 +1267,13 @@ module Aws::SecretsManager
     #
     # * 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
@@ -1275,11 +1282,6 @@ module Aws::SecretsManager
     #   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
@@ -1886,18 +1888,15 @@ module Aws::SecretsManager
     #
     #  </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
@@ -2304,7 +2303,7 @@ module Aws::SecretsManager
         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
 

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: aws-sdk-secretsmanager
 version: !ruby/object:Gem::Version
-  version: 1.3.0
+  version: 1.4.0
 platform: ruby
 authors:
 - Amazon Web Services
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2018-04-26 00:00:00.000000000 Z
+date: 2018-05-03 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: aws-sdk-core