#[non_exhaustive]pub struct PutStorageConfigurationOutputBuilder { /* private fields */ }Expand description
A builder for PutStorageConfigurationOutput.
Implementations§
Source§impl PutStorageConfigurationOutputBuilder
impl PutStorageConfigurationOutputBuilder
Sourcepub fn storage_type(self, input: StorageType) -> Self
pub fn storage_type(self, input: StorageType) -> Self
The storage tier that you specified for your data. The storageType parameter can be one of the following values:
-
SITEWISE_DEFAULT_STORAGE– IoT SiteWise saves your data into the hot tier. The hot tier is a service-managed database. -
MULTI_LAYER_STORAGE– IoT SiteWise saves your data in both the cold tier and the hot tier. The cold tier is a customer-managed Amazon S3 bucket.
Sourcepub fn set_storage_type(self, input: Option<StorageType>) -> Self
pub fn set_storage_type(self, input: Option<StorageType>) -> Self
The storage tier that you specified for your data. The storageType parameter can be one of the following values:
-
SITEWISE_DEFAULT_STORAGE– IoT SiteWise saves your data into the hot tier. The hot tier is a service-managed database. -
MULTI_LAYER_STORAGE– IoT SiteWise saves your data in both the cold tier and the hot tier. The cold tier is a customer-managed Amazon S3 bucket.
Sourcepub fn get_storage_type(&self) -> &Option<StorageType>
pub fn get_storage_type(&self) -> &Option<StorageType>
The storage tier that you specified for your data. The storageType parameter can be one of the following values:
-
SITEWISE_DEFAULT_STORAGE– IoT SiteWise saves your data into the hot tier. The hot tier is a service-managed database. -
MULTI_LAYER_STORAGE– IoT SiteWise saves your data in both the cold tier and the hot tier. The cold tier is a customer-managed Amazon S3 bucket.
Sourcepub fn multi_layer_storage(self, input: MultiLayerStorage) -> Self
pub fn multi_layer_storage(self, input: MultiLayerStorage) -> Self
Contains information about the storage destination.
Sourcepub fn set_multi_layer_storage(self, input: Option<MultiLayerStorage>) -> Self
pub fn set_multi_layer_storage(self, input: Option<MultiLayerStorage>) -> Self
Contains information about the storage destination.
Sourcepub fn get_multi_layer_storage(&self) -> &Option<MultiLayerStorage>
pub fn get_multi_layer_storage(&self) -> &Option<MultiLayerStorage>
Contains information about the storage destination.
Sourcepub fn disassociated_data_storage(
self,
input: DisassociatedDataStorageState,
) -> Self
pub fn disassociated_data_storage( self, input: DisassociatedDataStorageState, ) -> Self
Contains the storage configuration for time series (data streams) that aren't associated with asset properties. The disassociatedDataStorage can be one of the following values:
-
ENABLED– IoT SiteWise accepts time series that aren't associated with asset properties.After the
disassociatedDataStorageis enabled, you can't disable it. -
DISABLED– IoT SiteWise doesn't accept time series (data streams) that aren't associated with asset properties.
For more information, see Data streams in the IoT SiteWise User Guide.
Sourcepub fn set_disassociated_data_storage(
self,
input: Option<DisassociatedDataStorageState>,
) -> Self
pub fn set_disassociated_data_storage( self, input: Option<DisassociatedDataStorageState>, ) -> Self
Contains the storage configuration for time series (data streams) that aren't associated with asset properties. The disassociatedDataStorage can be one of the following values:
-
ENABLED– IoT SiteWise accepts time series that aren't associated with asset properties.After the
disassociatedDataStorageis enabled, you can't disable it. -
DISABLED– IoT SiteWise doesn't accept time series (data streams) that aren't associated with asset properties.
For more information, see Data streams in the IoT SiteWise User Guide.
Sourcepub fn get_disassociated_data_storage(
&self,
) -> &Option<DisassociatedDataStorageState>
pub fn get_disassociated_data_storage( &self, ) -> &Option<DisassociatedDataStorageState>
Contains the storage configuration for time series (data streams) that aren't associated with asset properties. The disassociatedDataStorage can be one of the following values:
-
ENABLED– IoT SiteWise accepts time series that aren't associated with asset properties.After the
disassociatedDataStorageis enabled, you can't disable it. -
DISABLED– IoT SiteWise doesn't accept time series (data streams) that aren't associated with asset properties.
For more information, see Data streams in the IoT SiteWise User Guide.
Sourcepub fn retention_period(self, input: RetentionPeriod) -> Self
pub fn retention_period(self, input: RetentionPeriod) -> Self
The number of days your data is kept in the hot tier. By default, your data is kept indefinitely in the hot tier.
Sourcepub fn set_retention_period(self, input: Option<RetentionPeriod>) -> Self
pub fn set_retention_period(self, input: Option<RetentionPeriod>) -> Self
The number of days your data is kept in the hot tier. By default, your data is kept indefinitely in the hot tier.
Sourcepub fn get_retention_period(&self) -> &Option<RetentionPeriod>
pub fn get_retention_period(&self) -> &Option<RetentionPeriod>
The number of days your data is kept in the hot tier. By default, your data is kept indefinitely in the hot tier.
Sourcepub fn configuration_status(self, input: ConfigurationStatus) -> Self
pub fn configuration_status(self, input: ConfigurationStatus) -> Self
Contains current status information for the configuration.
This field is required.Sourcepub fn set_configuration_status(
self,
input: Option<ConfigurationStatus>,
) -> Self
pub fn set_configuration_status( self, input: Option<ConfigurationStatus>, ) -> Self
Contains current status information for the configuration.
Sourcepub fn get_configuration_status(&self) -> &Option<ConfigurationStatus>
pub fn get_configuration_status(&self) -> &Option<ConfigurationStatus>
Contains current status information for the configuration.
Sourcepub fn warm_tier(self, input: WarmTierState) -> Self
pub fn warm_tier(self, input: WarmTierState) -> Self
A service managed storage tier optimized for analytical queries. It stores periodically uploaded, buffered and historical data ingested with the CreaeBulkImportJob API.
Sourcepub fn set_warm_tier(self, input: Option<WarmTierState>) -> Self
pub fn set_warm_tier(self, input: Option<WarmTierState>) -> Self
A service managed storage tier optimized for analytical queries. It stores periodically uploaded, buffered and historical data ingested with the CreaeBulkImportJob API.
Sourcepub fn get_warm_tier(&self) -> &Option<WarmTierState>
pub fn get_warm_tier(&self) -> &Option<WarmTierState>
A service managed storage tier optimized for analytical queries. It stores periodically uploaded, buffered and historical data ingested with the CreaeBulkImportJob API.
Sourcepub fn warm_tier_retention_period(self, input: WarmTierRetentionPeriod) -> Self
pub fn warm_tier_retention_period(self, input: WarmTierRetentionPeriod) -> Self
Set this period to specify how long your data is stored in the warm tier before it is deleted. You can set this only if cold tier is enabled.
Sourcepub fn set_warm_tier_retention_period(
self,
input: Option<WarmTierRetentionPeriod>,
) -> Self
pub fn set_warm_tier_retention_period( self, input: Option<WarmTierRetentionPeriod>, ) -> Self
Set this period to specify how long your data is stored in the warm tier before it is deleted. You can set this only if cold tier is enabled.
Sourcepub fn get_warm_tier_retention_period(&self) -> &Option<WarmTierRetentionPeriod>
pub fn get_warm_tier_retention_period(&self) -> &Option<WarmTierRetentionPeriod>
Set this period to specify how long your data is stored in the warm tier before it is deleted. You can set this only if cold tier is enabled.
Sourcepub fn disallow_ingest_null_na_n(self, input: bool) -> Self
pub fn disallow_ingest_null_na_n(self, input: bool) -> Self
Describes the configuration for ingesting NULL and NaN data. By default the feature is allowed. The feature is disallowed if the value is true.
Sourcepub fn set_disallow_ingest_null_na_n(self, input: Option<bool>) -> Self
pub fn set_disallow_ingest_null_na_n(self, input: Option<bool>) -> Self
Describes the configuration for ingesting NULL and NaN data. By default the feature is allowed. The feature is disallowed if the value is true.
Sourcepub fn get_disallow_ingest_null_na_n(&self) -> &Option<bool>
pub fn get_disallow_ingest_null_na_n(&self) -> &Option<bool>
Describes the configuration for ingesting NULL and NaN data. By default the feature is allowed. The feature is disallowed if the value is true.
Sourcepub fn build(self) -> Result<PutStorageConfigurationOutput, BuildError>
pub fn build(self) -> Result<PutStorageConfigurationOutput, BuildError>
Consumes the builder and constructs a PutStorageConfigurationOutput.
This method will fail if any of the following fields are not set:
Trait Implementations§
Source§impl Clone for PutStorageConfigurationOutputBuilder
impl Clone for PutStorageConfigurationOutputBuilder
Source§fn clone(&self) -> PutStorageConfigurationOutputBuilder
fn clone(&self) -> PutStorageConfigurationOutputBuilder
1.0.0 · Source§fn clone_from(&mut self, source: &Self)
fn clone_from(&mut self, source: &Self)
source. Read moreSource§impl Default for PutStorageConfigurationOutputBuilder
impl Default for PutStorageConfigurationOutputBuilder
Source§fn default() -> PutStorageConfigurationOutputBuilder
fn default() -> PutStorageConfigurationOutputBuilder
Source§impl PartialEq for PutStorageConfigurationOutputBuilder
impl PartialEq for PutStorageConfigurationOutputBuilder
Source§fn eq(&self, other: &PutStorageConfigurationOutputBuilder) -> bool
fn eq(&self, other: &PutStorageConfigurationOutputBuilder) -> bool
self and other values to be equal, and is used by ==.impl StructuralPartialEq for PutStorageConfigurationOutputBuilder
Auto Trait Implementations§
impl Freeze for PutStorageConfigurationOutputBuilder
impl RefUnwindSafe for PutStorageConfigurationOutputBuilder
impl Send for PutStorageConfigurationOutputBuilder
impl Sync for PutStorageConfigurationOutputBuilder
impl Unpin for PutStorageConfigurationOutputBuilder
impl UnwindSafe for PutStorageConfigurationOutputBuilder
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);