Struct aws_sdk_secretsmanager::input::UpdateSecretInput
source ·
[−]#[non_exhaustive]pub struct UpdateSecretInput {
pub secret_id: Option<String>,
pub client_request_token: Option<String>,
pub description: Option<String>,
pub kms_key_id: Option<String>,
pub secret_binary: Option<Blob>,
pub secret_string: Option<String>,
}
Fields (Non-exhaustive)
This struct is marked as non-exhaustive
Struct { .. }
syntax; cannot be matched against without a wildcard ..
; and struct update syntax will not work.secret_id: Option<String>
The ARN or name of the secret.
For an ARN, we recommend that you specify a complete ARN rather than a partial ARN.
client_request_token: Option<String>
If you include SecretString
or SecretBinary
, then Secrets Manager creates a new version for the secret, and this parameter specifies the unique identifier for the new version.
If you use the Amazon Web Services CLI or one of the Amazon Web Services SDKs to call this operation, then you can leave this parameter empty. The CLI or SDK generates a random UUID for you and includes it as the value for this parameter in the request. If you don't use the SDK and instead generate a raw HTTP request to the Secrets Manager service endpoint, then you must generate a ClientRequestToken
yourself for the new version and include the value in the request.
This value becomes the VersionId
of the new version.
description: Option<String>
The description of the secret.
kms_key_id: Option<String>
The ARN, key ID, or alias of the KMS key that Secrets Manager uses to encrypt new secret versions as well as any existing versions the staging labels AWSCURRENT
, AWSPENDING
, or AWSPREVIOUS
. For more information about versions and staging labels, see Concepts: Version.
You can only use the Amazon Web Services managed key aws/secretsmanager
if you call this operation using credentials from the same Amazon Web Services account that owns the secret. If the secret is in a different account, then you must use a customer managed key and provide the ARN of that KMS key in this field. The user making the call must have permissions to both the secret and the KMS key in their respective accounts.
secret_binary: Option<Blob>
The binary data to encrypt and store in the new version of the secret. We recommend that you store your binary data in a file and then pass the contents of the file as a parameter.
Either SecretBinary
or SecretString
must have a value, but not both.
You can't access this parameter in the Secrets Manager console.
secret_string: Option<String>
The text data to encrypt and store in the new version of the secret. We recommend you use a JSON structure of key/value pairs for your secret value.
Either SecretBinary
or SecretString
must have a value, but not both.
Implementations
pub async fn make_operation(
self,
_config: &Config
) -> Result<Operation<UpdateSecret, AwsErrorRetryPolicy>, BuildError>
pub async fn make_operation(
self,
_config: &Config
) -> Result<Operation<UpdateSecret, AwsErrorRetryPolicy>, BuildError>
Consumes the builder and constructs an Operation<UpdateSecret
>
Creates a new builder-style object to manufacture UpdateSecretInput
The ARN or name of the secret.
For an ARN, we recommend that you specify a complete ARN rather than a partial ARN.
If you include SecretString
or SecretBinary
, then Secrets Manager creates a new version for the secret, and this parameter specifies the unique identifier for the new version.
If you use the Amazon Web Services CLI or one of the Amazon Web Services SDKs to call this operation, then you can leave this parameter empty. The CLI or SDK generates a random UUID for you and includes it as the value for this parameter in the request. If you don't use the SDK and instead generate a raw HTTP request to the Secrets Manager service endpoint, then you must generate a ClientRequestToken
yourself for the new version and include the value in the request.
This value becomes the VersionId
of the new version.
The description of the secret.
The ARN, key ID, or alias of the KMS key that Secrets Manager uses to encrypt new secret versions as well as any existing versions the staging labels AWSCURRENT
, AWSPENDING
, or AWSPREVIOUS
. For more information about versions and staging labels, see Concepts: Version.
You can only use the Amazon Web Services managed key aws/secretsmanager
if you call this operation using credentials from the same Amazon Web Services account that owns the secret. If the secret is in a different account, then you must use a customer managed key and provide the ARN of that KMS key in this field. The user making the call must have permissions to both the secret and the KMS key in their respective accounts.
The binary data to encrypt and store in the new version of the secret. We recommend that you store your binary data in a file and then pass the contents of the file as a parameter.
Either SecretBinary
or SecretString
must have a value, but not both.
You can't access this parameter in the Secrets Manager console.
The text data to encrypt and store in the new version of the secret. We recommend you use a JSON structure of key/value pairs for your secret value.
Either SecretBinary
or SecretString
must have a value, but not both.
Trait Implementations
This method tests for self
and other
values to be equal, and is used
by ==
. Read more
This method tests for !=
.
Auto Trait Implementations
impl RefUnwindSafe for UpdateSecretInput
impl Send for UpdateSecretInput
impl Sync for UpdateSecretInput
impl Unpin for UpdateSecretInput
impl UnwindSafe for UpdateSecretInput
Blanket Implementations
Mutably borrows from an owned value. Read more
Attaches the provided Subscriber
to this type, returning a
WithDispatch
wrapper. Read more
Attaches the current default Subscriber
to this type, returning a
WithDispatch
wrapper. Read more