#[non_exhaustive]pub struct CreateDatasetInput {
pub dataset_name: Option<String>,
pub actions: Option<Vec<DatasetAction>>,
pub triggers: Option<Vec<DatasetTrigger>>,
pub content_delivery_rules: Option<Vec<DatasetContentDeliveryRule>>,
pub retention_period: Option<RetentionPeriod>,
pub versioning_configuration: Option<VersioningConfiguration>,
pub tags: Option<Vec<Tag>>,
pub late_data_rules: Option<Vec<LateDataRule>>,
}
Fields (Non-exhaustive)§
This struct is marked as non-exhaustive
Struct { .. }
syntax; cannot be matched against without a wildcard ..
; and struct update syntax will not work.dataset_name: Option<String>
The name of the dataset.
actions: Option<Vec<DatasetAction>>
A list of actions that create the dataset contents.
triggers: Option<Vec<DatasetTrigger>>
A list of triggers. A trigger causes dataset contents to be populated at a specified time interval or when another dataset's contents are created. The list of triggers can be empty or contain up to five DataSetTrigger
objects.
content_delivery_rules: Option<Vec<DatasetContentDeliveryRule>>
When dataset contents are created, they are delivered to destinations specified here.
retention_period: Option<RetentionPeriod>
Optional. How long, in days, versions of dataset contents are kept for the dataset. If not specified or set to null
, versions of dataset contents are retained for at most 90 days. The number of versions of dataset contents retained is determined by the versioningConfiguration
parameter. For more information, see Keeping Multiple Versions of IoT Analytics datasets in the IoT Analytics User Guide.
versioning_configuration: Option<VersioningConfiguration>
Optional. How many versions of dataset contents are kept. If not specified or set to null, only the latest version plus the latest succeeded version (if they are different) are kept for the time period specified by the retentionPeriod
parameter. For more information, see Keeping Multiple Versions of IoT Analytics datasets in the IoT Analytics User Guide.
Metadata which can be used to manage the dataset.
late_data_rules: Option<Vec<LateDataRule>>
A list of data rules that send notifications to CloudWatch, when data arrives late. To specify lateDataRules
, the dataset must use a DeltaTimer filter.
Implementations§
Source§impl CreateDatasetInput
impl CreateDatasetInput
Sourcepub fn dataset_name(&self) -> Option<&str>
pub fn dataset_name(&self) -> Option<&str>
The name of the dataset.
Sourcepub fn actions(&self) -> &[DatasetAction]
pub fn actions(&self) -> &[DatasetAction]
A list of actions that create the dataset contents.
If no value was sent for this field, a default will be set. If you want to determine if no value was sent, use .actions.is_none()
.
Sourcepub fn triggers(&self) -> &[DatasetTrigger]
pub fn triggers(&self) -> &[DatasetTrigger]
A list of triggers. A trigger causes dataset contents to be populated at a specified time interval or when another dataset's contents are created. The list of triggers can be empty or contain up to five DataSetTrigger
objects.
If no value was sent for this field, a default will be set. If you want to determine if no value was sent, use .triggers.is_none()
.
Sourcepub fn content_delivery_rules(&self) -> &[DatasetContentDeliveryRule]
pub fn content_delivery_rules(&self) -> &[DatasetContentDeliveryRule]
When dataset contents are created, they are delivered to destinations specified here.
If no value was sent for this field, a default will be set. If you want to determine if no value was sent, use .content_delivery_rules.is_none()
.
Sourcepub fn retention_period(&self) -> Option<&RetentionPeriod>
pub fn retention_period(&self) -> Option<&RetentionPeriod>
Optional. How long, in days, versions of dataset contents are kept for the dataset. If not specified or set to null
, versions of dataset contents are retained for at most 90 days. The number of versions of dataset contents retained is determined by the versioningConfiguration
parameter. For more information, see Keeping Multiple Versions of IoT Analytics datasets in the IoT Analytics User Guide.
Sourcepub fn versioning_configuration(&self) -> Option<&VersioningConfiguration>
pub fn versioning_configuration(&self) -> Option<&VersioningConfiguration>
Optional. How many versions of dataset contents are kept. If not specified or set to null, only the latest version plus the latest succeeded version (if they are different) are kept for the time period specified by the retentionPeriod
parameter. For more information, see Keeping Multiple Versions of IoT Analytics datasets in the IoT Analytics User Guide.
Metadata which can be used to manage the dataset.
If no value was sent for this field, a default will be set. If you want to determine if no value was sent, use .tags.is_none()
.
Sourcepub fn late_data_rules(&self) -> &[LateDataRule]
pub fn late_data_rules(&self) -> &[LateDataRule]
A list of data rules that send notifications to CloudWatch, when data arrives late. To specify lateDataRules
, the dataset must use a DeltaTimer filter.
If no value was sent for this field, a default will be set. If you want to determine if no value was sent, use .late_data_rules.is_none()
.
Source§impl CreateDatasetInput
impl CreateDatasetInput
Sourcepub fn builder() -> CreateDatasetInputBuilder
pub fn builder() -> CreateDatasetInputBuilder
Creates a new builder-style object to manufacture CreateDatasetInput
.
Trait Implementations§
Source§impl Clone for CreateDatasetInput
impl Clone for CreateDatasetInput
Source§fn clone(&self) -> CreateDatasetInput
fn clone(&self) -> CreateDatasetInput
1.0.0 · Source§const fn clone_from(&mut self, source: &Self)
const fn clone_from(&mut self, source: &Self)
source
. Read moreSource§impl Debug for CreateDatasetInput
impl Debug for CreateDatasetInput
Source§impl PartialEq for CreateDatasetInput
impl PartialEq for CreateDatasetInput
impl StructuralPartialEq for CreateDatasetInput
Auto Trait Implementations§
impl Freeze for CreateDatasetInput
impl RefUnwindSafe for CreateDatasetInput
impl Send for CreateDatasetInput
impl Sync for CreateDatasetInput
impl Unpin for CreateDatasetInput
impl UnwindSafe for CreateDatasetInput
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);