#[non_exhaustive]pub struct CreateSnaplockConfigurationBuilder { /* private fields */ }Expand description
A builder for CreateSnaplockConfiguration.
Implementations§
Source§impl CreateSnaplockConfigurationBuilder
impl CreateSnaplockConfigurationBuilder
Sourcepub fn audit_log_volume(self, input: bool) -> Self
pub fn audit_log_volume(self, input: bool) -> Self
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.
Sourcepub fn set_audit_log_volume(self, input: Option<bool>) -> Self
pub fn set_audit_log_volume(self, input: Option<bool>) -> Self
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.
Sourcepub fn get_audit_log_volume(&self) -> &Option<bool>
pub fn get_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.
Sourcepub fn autocommit_period(self, input: AutocommitPeriod) -> Self
pub fn autocommit_period(self, input: AutocommitPeriod) -> Self
The configuration object for setting the autocommit period of files in an FSx for ONTAP SnapLock volume.
Sourcepub fn set_autocommit_period(self, input: Option<AutocommitPeriod>) -> Self
pub fn set_autocommit_period(self, input: Option<AutocommitPeriod>) -> Self
The configuration object for setting the autocommit period of files in an FSx for ONTAP SnapLock volume.
Sourcepub fn get_autocommit_period(&self) -> &Option<AutocommitPeriod>
pub fn get_autocommit_period(&self) -> &Option<AutocommitPeriod>
The configuration object for setting the autocommit period of files in an FSx for ONTAP SnapLock volume.
Sourcepub fn privileged_delete(self, input: PrivilegedDelete) -> Self
pub fn privileged_delete(self, input: PrivilegedDelete) -> Self
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.
Sourcepub fn set_privileged_delete(self, input: Option<PrivilegedDelete>) -> Self
pub fn set_privileged_delete(self, input: Option<PrivilegedDelete>) -> Self
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.
Sourcepub fn get_privileged_delete(&self) -> &Option<PrivilegedDelete>
pub fn get_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.
Sourcepub fn retention_period(self, input: SnaplockRetentionPeriod) -> Self
pub fn retention_period(self, input: SnaplockRetentionPeriod) -> Self
Specifies the retention period of an FSx for ONTAP SnapLock volume.
Sourcepub fn set_retention_period(
self,
input: Option<SnaplockRetentionPeriod>,
) -> Self
pub fn set_retention_period( self, input: Option<SnaplockRetentionPeriod>, ) -> Self
Specifies the retention period of an FSx for ONTAP SnapLock volume.
Sourcepub fn get_retention_period(&self) -> &Option<SnaplockRetentionPeriod>
pub fn get_retention_period(&self) -> &Option<SnaplockRetentionPeriod>
Specifies the retention period of an FSx for ONTAP SnapLock volume.
Sourcepub fn snaplock_type(self, input: SnaplockType) -> Self
pub fn snaplock_type(self, input: SnaplockType) -> Self
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.
Sourcepub fn set_snaplock_type(self, input: Option<SnaplockType>) -> Self
pub fn set_snaplock_type(self, input: Option<SnaplockType>) -> Self
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.
Sourcepub fn get_snaplock_type(&self) -> &Option<SnaplockType>
pub fn get_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.
Sourcepub fn volume_append_mode_enabled(self, input: bool) -> Self
pub fn volume_append_mode_enabled(self, input: bool) -> Self
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.
Sourcepub fn set_volume_append_mode_enabled(self, input: Option<bool>) -> Self
pub fn set_volume_append_mode_enabled(self, input: Option<bool>) -> Self
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.
Sourcepub fn get_volume_append_mode_enabled(&self) -> &Option<bool>
pub fn get_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.
Sourcepub fn build(self) -> CreateSnaplockConfiguration
pub fn build(self) -> CreateSnaplockConfiguration
Consumes the builder and constructs a CreateSnaplockConfiguration.
Trait Implementations§
Source§impl Clone for CreateSnaplockConfigurationBuilder
impl Clone for CreateSnaplockConfigurationBuilder
Source§fn clone(&self) -> CreateSnaplockConfigurationBuilder
fn clone(&self) -> CreateSnaplockConfigurationBuilder
1.0.0 · Source§fn clone_from(&mut self, source: &Self)
fn clone_from(&mut self, source: &Self)
source. Read moreSource§impl Default for CreateSnaplockConfigurationBuilder
impl Default for CreateSnaplockConfigurationBuilder
Source§fn default() -> CreateSnaplockConfigurationBuilder
fn default() -> CreateSnaplockConfigurationBuilder
Source§impl PartialEq for CreateSnaplockConfigurationBuilder
impl PartialEq for CreateSnaplockConfigurationBuilder
Source§fn eq(&self, other: &CreateSnaplockConfigurationBuilder) -> bool
fn eq(&self, other: &CreateSnaplockConfigurationBuilder) -> bool
self and other values to be equal, and is used by ==.impl StructuralPartialEq for CreateSnaplockConfigurationBuilder
Auto Trait Implementations§
impl Freeze for CreateSnaplockConfigurationBuilder
impl RefUnwindSafe for CreateSnaplockConfigurationBuilder
impl Send for CreateSnaplockConfigurationBuilder
impl Sync for CreateSnaplockConfigurationBuilder
impl Unpin for CreateSnaplockConfigurationBuilder
impl UnwindSafe for CreateSnaplockConfigurationBuilder
Blanket Implementations§
Source§impl<T> BorrowMut<T> for Twhere
T: ?Sized,
impl<T> BorrowMut<T> for Twhere
T: ?Sized,
Source§fn borrow_mut(&mut self) -> &mut T
fn borrow_mut(&mut self) -> &mut T
Source§impl<T> CloneToUninit for Twhere
T: Clone,
impl<T> CloneToUninit for Twhere
T: Clone,
Source§impl<T> Instrument for T
impl<T> Instrument for T
Source§fn instrument(self, span: Span) -> Instrumented<Self>
fn instrument(self, span: Span) -> Instrumented<Self>
Source§fn in_current_span(self) -> Instrumented<Self>
fn in_current_span(self) -> Instrumented<Self>
Source§impl<T> IntoEither for T
impl<T> IntoEither for T
Source§fn into_either(self, into_left: bool) -> Either<Self, Self>
fn into_either(self, into_left: bool) -> Either<Self, Self>
self into a Left variant of Either<Self, Self>
if into_left is true.
Converts self into a Right variant of Either<Self, Self>
otherwise. Read moreSource§fn into_either_with<F>(self, into_left: F) -> Either<Self, Self>
fn into_either_with<F>(self, into_left: F) -> Either<Self, Self>
self into a Left variant of Either<Self, Self>
if into_left(&self) returns true.
Converts self into a Right variant of Either<Self, Self>
otherwise. Read moreSource§impl<T> Paint for Twhere
T: ?Sized,
impl<T> Paint for Twhere
T: ?Sized,
Source§fn fg(&self, value: Color) -> Painted<&T>
fn fg(&self, value: Color) -> Painted<&T>
Returns a styled value derived from self with the foreground set to
value.
This method should be used rarely. Instead, prefer to use color-specific
builder methods like red() and
green(), which have the same functionality but are
pithier.
§Example
Set foreground color to white using fg():
use yansi::{Paint, Color};
painted.fg(Color::White);Set foreground color to white using white().
use yansi::Paint;
painted.white();Source§fn bright_black(&self) -> Painted<&T>
fn bright_black(&self) -> Painted<&T>
Source§fn bright_red(&self) -> Painted<&T>
fn bright_red(&self) -> Painted<&T>
Source§fn bright_green(&self) -> Painted<&T>
fn bright_green(&self) -> Painted<&T>
Source§fn bright_yellow(&self) -> Painted<&T>
fn bright_yellow(&self) -> Painted<&T>
Source§fn bright_blue(&self) -> Painted<&T>
fn bright_blue(&self) -> Painted<&T>
Source§fn bright_magenta(&self) -> Painted<&T>
fn bright_magenta(&self) -> Painted<&T>
Source§fn bright_cyan(&self) -> Painted<&T>
fn bright_cyan(&self) -> Painted<&T>
Source§fn bright_white(&self) -> Painted<&T>
fn bright_white(&self) -> Painted<&T>
Source§fn bg(&self, value: Color) -> Painted<&T>
fn bg(&self, value: Color) -> Painted<&T>
Returns a styled value derived from self with the background set to
value.
This method should be used rarely. Instead, prefer to use color-specific
builder methods like on_red() and
on_green(), which have the same functionality but
are pithier.
§Example
Set background color to red using fg():
use yansi::{Paint, Color};
painted.bg(Color::Red);Set background color to red using on_red().
use yansi::Paint;
painted.on_red();Source§fn on_primary(&self) -> Painted<&T>
fn on_primary(&self) -> Painted<&T>
Source§fn on_magenta(&self) -> Painted<&T>
fn on_magenta(&self) -> Painted<&T>
Source§fn on_bright_black(&self) -> Painted<&T>
fn on_bright_black(&self) -> Painted<&T>
Source§fn on_bright_red(&self) -> Painted<&T>
fn on_bright_red(&self) -> Painted<&T>
Source§fn on_bright_green(&self) -> Painted<&T>
fn on_bright_green(&self) -> Painted<&T>
Source§fn on_bright_yellow(&self) -> Painted<&T>
fn on_bright_yellow(&self) -> Painted<&T>
Source§fn on_bright_blue(&self) -> Painted<&T>
fn on_bright_blue(&self) -> Painted<&T>
Source§fn on_bright_magenta(&self) -> Painted<&T>
fn on_bright_magenta(&self) -> Painted<&T>
Source§fn on_bright_cyan(&self) -> Painted<&T>
fn on_bright_cyan(&self) -> Painted<&T>
Source§fn on_bright_white(&self) -> Painted<&T>
fn on_bright_white(&self) -> Painted<&T>
Source§fn attr(&self, value: Attribute) -> Painted<&T>
fn attr(&self, value: Attribute) -> Painted<&T>
Enables the styling Attribute value.
This method should be used rarely. Instead, prefer to use
attribute-specific builder methods like bold() and
underline(), which have the same functionality
but are pithier.
§Example
Make text bold using attr():
use yansi::{Paint, Attribute};
painted.attr(Attribute::Bold);Make text bold using using bold().
use yansi::Paint;
painted.bold();Source§fn rapid_blink(&self) -> Painted<&T>
fn rapid_blink(&self) -> Painted<&T>
Source§fn quirk(&self, value: Quirk) -> Painted<&T>
fn quirk(&self, value: Quirk) -> Painted<&T>
Enables the yansi Quirk value.
This method should be used rarely. Instead, prefer to use quirk-specific
builder methods like mask() and
wrap(), which have the same functionality but are
pithier.
§Example
Enable wrapping using .quirk():
use yansi::{Paint, Quirk};
painted.quirk(Quirk::Wrap);Enable wrapping using wrap().
use yansi::Paint;
painted.wrap();Source§fn clear(&self) -> Painted<&T>
👎Deprecated since 1.0.1: renamed to resetting() due to conflicts with Vec::clear().
The clear() method will be removed in a future release.
fn clear(&self) -> Painted<&T>
resetting() due to conflicts with Vec::clear().
The clear() method will be removed in a future release.Source§fn whenever(&self, value: Condition) -> Painted<&T>
fn whenever(&self, value: Condition) -> Painted<&T>
Conditionally enable styling based on whether the Condition value
applies. Replaces any previous condition.
See the crate level docs for more details.
§Example
Enable styling painted only when both stdout and stderr are TTYs:
use yansi::{Paint, Condition};
painted.red().on_yellow().whenever(Condition::STDOUTERR_ARE_TTY);