Module aws_sdk_secretsmanager::types
source · Expand description
Data structures used by operation inputs/outputs.
Modules§
- Builders
- Error types that AWS Secrets Manager can respond with.
Structs§
The error Secrets Manager encountered while retrieving an individual secret as part of
BatchGetSecretValue
.Allows you to add filters when you use the search function in Secrets Manager. For more information, see Find secrets in Secrets Manager.
A custom type that specifies a
Region
and theKmsKeyId
for a replica secret.A replication object consisting of a
RegionReplicationStatus
object and includes a Region, KMSKeyId, status, and status message.A structure that defines the rotation configuration for the secret.
A structure that contains the details about a secret. It does not include the encrypted
SecretString
andSecretBinary
values. To get those values, use GetSecretValue .A structure that contains the secret value and other details for a secret.
A structure that contains information about one version of a secret.
A structure that contains information about a tag.
Displays errors that occurred during validation of the resource policy.
Enums§
- When writing a match expression against
FilterNameStringType
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
SortOrderType
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
StatusType
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.