#[non_exhaustive]pub struct BackupRule {
pub rule_name: String,
pub target_backup_vault_name: String,
pub schedule_expression: Option<String>,
pub start_window_minutes: Option<i64>,
pub completion_window_minutes: Option<i64>,
pub lifecycle: Option<Lifecycle>,
pub recovery_point_tags: Option<HashMap<String, String>>,
pub rule_id: Option<String>,
pub copy_actions: Option<Vec<CopyAction>>,
pub enable_continuous_backup: Option<bool>,
pub schedule_expression_timezone: Option<String>,
pub index_actions: Option<Vec<IndexAction>>,
}
Expand description
Specifies a scheduled task used to back up a selection of resources.
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.rule_name: String
A display name for a backup rule. Must contain 1 to 50 alphanumeric or '-_.' characters.
target_backup_vault_name: String
The name of a logical container where backups are stored. Backup vaults are identified by names that are unique to the account used to create them and the Amazon Web Services Region where they are created.
schedule_expression: Option<String>
A cron expression in UTC specifying when Backup initiates a backup job. When no CRON expression is provided, Backup will use the default expression cron(0 5 ? * * *)
.
For more information about Amazon Web Services cron expressions, see Schedule Expressions for Rules in the Amazon CloudWatch Events User Guide.
Two examples of Amazon Web Services cron expressions are 15 * ? * * *
(take a backup every hour at 15 minutes past the hour) and 0 12 * * ? *
(take a backup every day at 12 noon UTC).
For a table of examples, click the preceding link and scroll down the page.
start_window_minutes: Option<i64>
A value in minutes after a backup is scheduled before a job will be canceled if it doesn't start successfully. This value is optional. If this value is included, it must be at least 60 minutes to avoid errors.
During the start window, the backup job status remains in CREATED
status until it has successfully begun or until the start window time has run out. If within the start window time Backup receives an error that allows the job to be retried, Backup will automatically retry to begin the job at least every 10 minutes until the backup successfully begins (the job status changes to RUNNING
) or until the job status changes to EXPIRED
(which is expected to occur when the start window time is over).
completion_window_minutes: Option<i64>
A value in minutes after a backup job is successfully started before it must be completed or it will be canceled by Backup. This value is optional.
lifecycle: Option<Lifecycle>
The lifecycle defines when a protected resource is transitioned to cold storage and when it expires. Backup transitions and expires backups automatically according to the lifecycle that you define.
Backups transitioned to cold storage must be stored in cold storage for a minimum of 90 days. Therefore, the “retention” setting must be 90 days greater than the “transition to cold after days” setting. The “transition to cold after days” setting cannot be changed after a backup has been transitioned to cold.
Resource types that can transition to cold storage are listed in the Feature availability by resource table. Backup ignores this expression for other resource types.
The tags that are assigned to resources that are associated with this rule when restored from backup.
rule_id: Option<String>
Uniquely identifies a rule that is used to schedule the backup of a selection of resources.
copy_actions: Option<Vec<CopyAction>>
An array of CopyAction
objects, which contains the details of the copy operation.
enable_continuous_backup: Option<bool>
Specifies whether Backup creates continuous backups. True causes Backup to create continuous backups capable of point-in-time restore (PITR). False (or not specified) causes Backup to create snapshot backups.
schedule_expression_timezone: Option<String>
The timezone in which the schedule expression is set. By default, ScheduleExpressions are in UTC. You can modify this to a specified timezone.
index_actions: Option<Vec<IndexAction>>
IndexActions is an array you use to specify how backup data should be indexed.
eEach BackupRule can have 0 or 1 IndexAction, as each backup can have up to one index associated with it.
Within the array is ResourceType. Only one will be accepted for each BackupRule.
Implementations§
Source§impl BackupRule
impl BackupRule
Sourcepub fn rule_name(&self) -> &str
pub fn rule_name(&self) -> &str
A display name for a backup rule. Must contain 1 to 50 alphanumeric or '-_.' characters.
Sourcepub fn target_backup_vault_name(&self) -> &str
pub fn target_backup_vault_name(&self) -> &str
The name of a logical container where backups are stored. Backup vaults are identified by names that are unique to the account used to create them and the Amazon Web Services Region where they are created.
Sourcepub fn schedule_expression(&self) -> Option<&str>
pub fn schedule_expression(&self) -> Option<&str>
A cron expression in UTC specifying when Backup initiates a backup job. When no CRON expression is provided, Backup will use the default expression cron(0 5 ? * * *)
.
For more information about Amazon Web Services cron expressions, see Schedule Expressions for Rules in the Amazon CloudWatch Events User Guide.
Two examples of Amazon Web Services cron expressions are 15 * ? * * *
(take a backup every hour at 15 minutes past the hour) and 0 12 * * ? *
(take a backup every day at 12 noon UTC).
For a table of examples, click the preceding link and scroll down the page.
Sourcepub fn start_window_minutes(&self) -> Option<i64>
pub fn start_window_minutes(&self) -> Option<i64>
A value in minutes after a backup is scheduled before a job will be canceled if it doesn't start successfully. This value is optional. If this value is included, it must be at least 60 minutes to avoid errors.
During the start window, the backup job status remains in CREATED
status until it has successfully begun or until the start window time has run out. If within the start window time Backup receives an error that allows the job to be retried, Backup will automatically retry to begin the job at least every 10 minutes until the backup successfully begins (the job status changes to RUNNING
) or until the job status changes to EXPIRED
(which is expected to occur when the start window time is over).
Sourcepub fn completion_window_minutes(&self) -> Option<i64>
pub fn completion_window_minutes(&self) -> Option<i64>
A value in minutes after a backup job is successfully started before it must be completed or it will be canceled by Backup. This value is optional.
Sourcepub fn lifecycle(&self) -> Option<&Lifecycle>
pub fn lifecycle(&self) -> Option<&Lifecycle>
The lifecycle defines when a protected resource is transitioned to cold storage and when it expires. Backup transitions and expires backups automatically according to the lifecycle that you define.
Backups transitioned to cold storage must be stored in cold storage for a minimum of 90 days. Therefore, the “retention” setting must be 90 days greater than the “transition to cold after days” setting. The “transition to cold after days” setting cannot be changed after a backup has been transitioned to cold.
Resource types that can transition to cold storage are listed in the Feature availability by resource table. Backup ignores this expression for other resource types.
The tags that are assigned to resources that are associated with this rule when restored from backup.
Sourcepub fn rule_id(&self) -> Option<&str>
pub fn rule_id(&self) -> Option<&str>
Uniquely identifies a rule that is used to schedule the backup of a selection of resources.
Sourcepub fn copy_actions(&self) -> &[CopyAction]
pub fn copy_actions(&self) -> &[CopyAction]
An array of CopyAction
objects, which contains the details of the copy operation.
If no value was sent for this field, a default will be set. If you want to determine if no value was sent, use .copy_actions.is_none()
.
Sourcepub fn enable_continuous_backup(&self) -> Option<bool>
pub fn enable_continuous_backup(&self) -> Option<bool>
Specifies whether Backup creates continuous backups. True causes Backup to create continuous backups capable of point-in-time restore (PITR). False (or not specified) causes Backup to create snapshot backups.
Sourcepub fn schedule_expression_timezone(&self) -> Option<&str>
pub fn schedule_expression_timezone(&self) -> Option<&str>
The timezone in which the schedule expression is set. By default, ScheduleExpressions are in UTC. You can modify this to a specified timezone.
Sourcepub fn index_actions(&self) -> &[IndexAction]
pub fn index_actions(&self) -> &[IndexAction]
IndexActions is an array you use to specify how backup data should be indexed.
eEach BackupRule can have 0 or 1 IndexAction, as each backup can have up to one index associated with it.
Within the array is ResourceType. Only one will be accepted for each BackupRule.
If no value was sent for this field, a default will be set. If you want to determine if no value was sent, use .index_actions.is_none()
.
Source§impl BackupRule
impl BackupRule
Sourcepub fn builder() -> BackupRuleBuilder
pub fn builder() -> BackupRuleBuilder
Creates a new builder-style object to manufacture BackupRule
.
Trait Implementations§
Source§impl Clone for BackupRule
impl Clone for BackupRule
Source§fn clone(&self) -> BackupRule
fn clone(&self) -> BackupRule
1.0.0 · Source§fn clone_from(&mut self, source: &Self)
fn clone_from(&mut self, source: &Self)
source
. Read moreSource§impl Debug for BackupRule
impl Debug for BackupRule
Source§impl PartialEq for BackupRule
impl PartialEq for BackupRule
impl StructuralPartialEq for BackupRule
Auto Trait Implementations§
impl Freeze for BackupRule
impl RefUnwindSafe for BackupRule
impl Send for BackupRule
impl Sync for BackupRule
impl Unpin for BackupRule
impl UnwindSafe for BackupRule
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);