Expand description
Data structures used by operation inputs/outputs.
Modules§
Structs§
- Backup
Contains information about a backup of an CloudHSM cluster. All backup objects contain the
BackupId,BackupState,ClusterId, andCreateTimestampparameters. Backups that were copied into a destination region additionally contain theCopyTimestamp,SourceBackup,SourceCluster, andSourceRegionparameters. A backup that is pending deletion will include theDeleteTimestampparameter.- Backup
Retention Policy A policy that defines the number of days to retain backups.
- Certificates
Contains one or more certificates or a certificate signing request (CSR).
- Cluster
Contains information about an CloudHSM cluster.
- Destination
Backup Contains information about the backup that will be copied and created by the
CopyBackupToRegionoperation.- Hsm
Contains information about a hardware security module (HSM) in an CloudHSM cluster.
- Tag
Contains a tag. A tag is a key-value pair.
Enums§
- Backup
Policy - When writing a match expression against
BackupPolicy, 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. - Backup
Retention Type - When writing a match expression against
BackupRetentionType, 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. - Backup
State - When writing a match expression against
BackupState, 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. - Cluster
Mode - When writing a match expression against
ClusterMode, 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. - Cluster
State - When writing a match expression against
ClusterState, 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. - HsmState
- When writing a match expression against
HsmState, 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. - Network
Type - When writing a match expression against
NetworkType, 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.