Struct CreateSnaplockConfiguration 

#[non_exhaustive]
pub struct CreateSnaplockConfiguration {
    pub audit_log_volume: Option<bool>,
    pub autocommit_period: Option<AutocommitPeriod>,
    pub privileged_delete: Option<PrivilegedDelete>,
    pub retention_period: Option<SnaplockRetentionPeriod>,
    pub snaplock_type: Option<SnaplockType>,
    pub volume_append_mode_enabled: Option<bool>,
}

Defines the SnapLock configuration when creating an FSx for ONTAP SnapLock volume.

Fields (Non-exhaustive)

Non-exhaustive structs could have additional fields added in future. Therefore, non-exhaustive structs cannot be constructed in external crates using the traditional Struct { .. } syntax; cannot be matched against without a wildcard ..; and struct update syntax will not work.

audit_log_volume: Option<bool>

Enables or disables the audit log volume for an FSx for ONTAP SnapLock volume. The default value is false. If you set AuditLogVolume to true, the SnapLock volume is created as an audit log volume. The minimum retention period for an audit log volume is six months.

For more information, see SnapLock audit log volumes.

autocommit_period: Option<AutocommitPeriod>

The configuration object for setting the autocommit period of files in an FSx for ONTAP SnapLock volume.

privileged_delete: Option<PrivilegedDelete>

Enables, disables, or permanently disables privileged delete on an FSx for ONTAP SnapLock Enterprise volume. Enabling privileged delete allows SnapLock administrators to delete WORM files even if they have active retention periods. PERMANENTLY_DISABLED is a terminal state. If privileged delete is permanently disabled on a SnapLock volume, you can't re-enable it. The default value is DISABLED.

For more information, see Privileged delete.

retention_period: Option<SnaplockRetentionPeriod>

Specifies the retention period of an FSx for ONTAP SnapLock volume.

snaplock_type: Option<SnaplockType>

Specifies the retention mode of an FSx for ONTAP SnapLock volume. After it is set, it can't be changed. You can choose one of the following retention modes:

• COMPLIANCE: Files transitioned to write once, read many (WORM) on a Compliance volume can't be deleted until their retention periods expire. This retention mode is used to address government or industry-specific mandates or to protect against ransomware attacks. For more information, see SnapLock Compliance.

• ENTERPRISE: Files transitioned to WORM on an Enterprise volume can be deleted by authorized users before their retention periods expire using privileged delete. This retention mode is used to advance an organization's data integrity and internal compliance or to test retention settings before using SnapLock Compliance. For more information, see SnapLock Enterprise.

volume_append_mode_enabled: Option<bool>

Enables or disables volume-append mode on an FSx for ONTAP SnapLock volume. Volume-append mode allows you to create WORM-appendable files and write data to them incrementally. The default value is false.

For more information, see Volume-append mode.

Implementations

impl CreateSnaplockConfiguration

pub fn audit_log_volume(&self) -> Option<bool>

Enables or disables the audit log volume for an FSx for ONTAP SnapLock volume. The default value is false. If you set AuditLogVolume to true, the SnapLock volume is created as an audit log volume. The minimum retention period for an audit log volume is six months.

For more information, see SnapLock audit log volumes.

pub fn autocommit_period(&self) -> Option<&AutocommitPeriod>

The configuration object for setting the autocommit period of files in an FSx for ONTAP SnapLock volume.

pub fn privileged_delete(&self) -> Option<&PrivilegedDelete>

Enables, disables, or permanently disables privileged delete on an FSx for ONTAP SnapLock Enterprise volume. Enabling privileged delete allows SnapLock administrators to delete WORM files even if they have active retention periods. PERMANENTLY_DISABLED is a terminal state. If privileged delete is permanently disabled on a SnapLock volume, you can't re-enable it. The default value is DISABLED.

For more information, see Privileged delete.

pub fn retention_period(&self) -> Option<&SnaplockRetentionPeriod>

Specifies the retention period of an FSx for ONTAP SnapLock volume.

pub fn snaplock_type(&self) -> Option<&SnaplockType>

Specifies the retention mode of an FSx for ONTAP SnapLock volume. After it is set, it can't be changed. You can choose one of the following retention modes:

• COMPLIANCE: Files transitioned to write once, read many (WORM) on a Compliance volume can't be deleted until their retention periods expire. This retention mode is used to address government or industry-specific mandates or to protect against ransomware attacks. For more information, see SnapLock Compliance.

• ENTERPRISE: Files transitioned to WORM on an Enterprise volume can be deleted by authorized users before their retention periods expire using privileged delete. This retention mode is used to advance an organization's data integrity and internal compliance or to test retention settings before using SnapLock Compliance. For more information, see SnapLock Enterprise.

pub fn volume_append_mode_enabled(&self) -> Option<bool>

Enables or disables volume-append mode on an FSx for ONTAP SnapLock volume. Volume-append mode allows you to create WORM-appendable files and write data to them incrementally. The default value is false.

For more information, see Volume-append mode.

impl CreateSnaplockConfiguration

pub fn builder() -> CreateSnaplockConfigurationBuilder

Creates a new builder-style object to manufacture CreateSnaplockConfiguration.

Trait Implementations

impl Clone for CreateSnaplockConfiguration

fn clone(&self) -> CreateSnaplockConfiguration

Returns a duplicate of the value.

fn clone_from(&mut self, source: &Self)

Performs copy-assignment from source.

impl Debug for CreateSnaplockConfiguration

fn fmt(&self, f: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.

impl PartialEq for CreateSnaplockConfiguration

fn eq(&self, other: &CreateSnaplockConfiguration) -> bool

Tests for self and other values to be equal, and is used by ==.

fn ne(&self, other: &Rhs) -> bool

Tests for !=. The default implementation is almost always sufficient, and should not be overridden without very good reason.

impl StructuralPartialEq for CreateSnaplockConfiguration