pub struct UpdatePracticeRunConfigurationFluentBuilder { /* private fields */ }Expand description
Fluent builder constructing a request to UpdatePracticeRunConfiguration.
Update a practice run configuration to change one or more of the following: add, change, or remove the blocking alarm; change the outcome alarm; or add, change, or remove blocking dates or time windows.
Implementations§
Source§impl UpdatePracticeRunConfigurationFluentBuilder
impl UpdatePracticeRunConfigurationFluentBuilder
Sourcepub fn as_input(&self) -> &UpdatePracticeRunConfigurationInputBuilder
pub fn as_input(&self) -> &UpdatePracticeRunConfigurationInputBuilder
Access the UpdatePracticeRunConfiguration as a reference.
Sourcepub async fn send(
self,
) -> Result<UpdatePracticeRunConfigurationOutput, SdkError<UpdatePracticeRunConfigurationError, HttpResponse>>
pub async fn send( self, ) -> Result<UpdatePracticeRunConfigurationOutput, SdkError<UpdatePracticeRunConfigurationError, HttpResponse>>
Sends the request and returns the response.
If an error occurs, an SdkError will be returned with additional details that
can be matched against.
By default, any retryable failures will be retried twice. Retry behavior is configurable with the RetryConfig, which can be set when configuring the client.
Sourcepub fn customize(
self,
) -> CustomizableOperation<UpdatePracticeRunConfigurationOutput, UpdatePracticeRunConfigurationError, Self>
pub fn customize( self, ) -> CustomizableOperation<UpdatePracticeRunConfigurationOutput, UpdatePracticeRunConfigurationError, Self>
Consumes this builder, creating a customizable operation that can be modified before being sent.
Sourcepub fn resource_identifier(self, input: impl Into<String>) -> Self
pub fn resource_identifier(self, input: impl Into<String>) -> Self
The identifier for the resource that you want to update the practice run configuration for. The identifier is the Amazon Resource Name (ARN) for the resource.
Sourcepub fn set_resource_identifier(self, input: Option<String>) -> Self
pub fn set_resource_identifier(self, input: Option<String>) -> Self
The identifier for the resource that you want to update the practice run configuration for. The identifier is the Amazon Resource Name (ARN) for the resource.
Sourcepub fn get_resource_identifier(&self) -> &Option<String>
pub fn get_resource_identifier(&self) -> &Option<String>
The identifier for the resource that you want to update the practice run configuration for. The identifier is the Amazon Resource Name (ARN) for the resource.
Sourcepub fn blocked_windows(self, input: impl Into<String>) -> Self
pub fn blocked_windows(self, input: impl Into<String>) -> Self
Appends an item to blockedWindows.
To override the contents of this collection use set_blocked_windows.
Add, change, or remove windows of days and times for when you can, optionally, block ARC from starting a practice run for a resource.
The format for blocked windows is: DAY:HH:SS-DAY:HH:SS. Keep in mind, when you specify dates, that dates and times for practice runs are in UTC. Also, be aware of potential time adjustments that might be required for daylight saving time differences. Separate multiple blocked windows with spaces.
For example, say you run business report summaries three days a week. For this scenario, you might set the following recurring days and times as blocked windows, for example: MON-20:30-21:30 WED-20:30-21:30 FRI-20:30-21:30.
Sourcepub fn set_blocked_windows(self, input: Option<Vec<String>>) -> Self
pub fn set_blocked_windows(self, input: Option<Vec<String>>) -> Self
Add, change, or remove windows of days and times for when you can, optionally, block ARC from starting a practice run for a resource.
The format for blocked windows is: DAY:HH:SS-DAY:HH:SS. Keep in mind, when you specify dates, that dates and times for practice runs are in UTC. Also, be aware of potential time adjustments that might be required for daylight saving time differences. Separate multiple blocked windows with spaces.
For example, say you run business report summaries three days a week. For this scenario, you might set the following recurring days and times as blocked windows, for example: MON-20:30-21:30 WED-20:30-21:30 FRI-20:30-21:30.
Sourcepub fn get_blocked_windows(&self) -> &Option<Vec<String>>
pub fn get_blocked_windows(&self) -> &Option<Vec<String>>
Add, change, or remove windows of days and times for when you can, optionally, block ARC from starting a practice run for a resource.
The format for blocked windows is: DAY:HH:SS-DAY:HH:SS. Keep in mind, when you specify dates, that dates and times for practice runs are in UTC. Also, be aware of potential time adjustments that might be required for daylight saving time differences. Separate multiple blocked windows with spaces.
For example, say you run business report summaries three days a week. For this scenario, you might set the following recurring days and times as blocked windows, for example: MON-20:30-21:30 WED-20:30-21:30 FRI-20:30-21:30.
Sourcepub fn blocked_dates(self, input: impl Into<String>) -> Self
pub fn blocked_dates(self, input: impl Into<String>) -> Self
Appends an item to blockedDates.
To override the contents of this collection use set_blocked_dates.
Add, change, or remove blocked dates for a practice run in zonal autoshift.
Optionally, you can block practice runs for specific calendar dates. The format for blocked dates is: YYYY-MM-DD. Keep in mind, when you specify dates, that dates and times for practice runs are in UTC. Separate multiple blocked dates with spaces.
For example, if you have an application update scheduled to launch on May 1, 2024, and you don't want practice runs to shift traffic away at that time, you could set a blocked date for 2024-05-01.
Sourcepub fn set_blocked_dates(self, input: Option<Vec<String>>) -> Self
pub fn set_blocked_dates(self, input: Option<Vec<String>>) -> Self
Add, change, or remove blocked dates for a practice run in zonal autoshift.
Optionally, you can block practice runs for specific calendar dates. The format for blocked dates is: YYYY-MM-DD. Keep in mind, when you specify dates, that dates and times for practice runs are in UTC. Separate multiple blocked dates with spaces.
For example, if you have an application update scheduled to launch on May 1, 2024, and you don't want practice runs to shift traffic away at that time, you could set a blocked date for 2024-05-01.
Sourcepub fn get_blocked_dates(&self) -> &Option<Vec<String>>
pub fn get_blocked_dates(&self) -> &Option<Vec<String>>
Add, change, or remove blocked dates for a practice run in zonal autoshift.
Optionally, you can block practice runs for specific calendar dates. The format for blocked dates is: YYYY-MM-DD. Keep in mind, when you specify dates, that dates and times for practice runs are in UTC. Separate multiple blocked dates with spaces.
For example, if you have an application update scheduled to launch on May 1, 2024, and you don't want practice runs to shift traffic away at that time, you could set a blocked date for 2024-05-01.
Sourcepub fn blocking_alarms(self, input: ControlCondition) -> Self
pub fn blocking_alarms(self, input: ControlCondition) -> Self
Appends an item to blockingAlarms.
To override the contents of this collection use set_blocking_alarms.
Add, change, or remove the Amazon CloudWatch alarms that you optionally specify as the blocking alarms for practice runs.
Sourcepub fn set_blocking_alarms(self, input: Option<Vec<ControlCondition>>) -> Self
pub fn set_blocking_alarms(self, input: Option<Vec<ControlCondition>>) -> Self
Add, change, or remove the Amazon CloudWatch alarms that you optionally specify as the blocking alarms for practice runs.
Sourcepub fn get_blocking_alarms(&self) -> &Option<Vec<ControlCondition>>
pub fn get_blocking_alarms(&self) -> &Option<Vec<ControlCondition>>
Add, change, or remove the Amazon CloudWatch alarms that you optionally specify as the blocking alarms for practice runs.
Sourcepub fn allowed_windows(self, input: impl Into<String>) -> Self
pub fn allowed_windows(self, input: impl Into<String>) -> Self
Appends an item to allowedWindows.
To override the contents of this collection use set_allowed_windows.
Add, change, or remove windows of days and times for when you can, optionally, allow ARC to start a practice run for a resource.
The format for allowed windows is: DAY:HH:SS-DAY:HH:SS. Keep in mind, when you specify dates, that dates and times for practice runs are in UTC. Also, be aware of potential time adjustments that might be required for daylight saving time differences. Separate multiple allowed windows with spaces.
For example, say you want to allow practice runs only on Wednesdays and Fridays from noon to 5 p.m. For this scenario, you could set the following recurring days and times as allowed windows, for example: Wed-12:00-Wed:17:00 Fri-12:00-Fri:17:00.
The allowedWindows have to start and end on the same day. Windows that span multiple days aren't supported.
Sourcepub fn set_allowed_windows(self, input: Option<Vec<String>>) -> Self
pub fn set_allowed_windows(self, input: Option<Vec<String>>) -> Self
Add, change, or remove windows of days and times for when you can, optionally, allow ARC to start a practice run for a resource.
The format for allowed windows is: DAY:HH:SS-DAY:HH:SS. Keep in mind, when you specify dates, that dates and times for practice runs are in UTC. Also, be aware of potential time adjustments that might be required for daylight saving time differences. Separate multiple allowed windows with spaces.
For example, say you want to allow practice runs only on Wednesdays and Fridays from noon to 5 p.m. For this scenario, you could set the following recurring days and times as allowed windows, for example: Wed-12:00-Wed:17:00 Fri-12:00-Fri:17:00.
The allowedWindows have to start and end on the same day. Windows that span multiple days aren't supported.
Sourcepub fn get_allowed_windows(&self) -> &Option<Vec<String>>
pub fn get_allowed_windows(&self) -> &Option<Vec<String>>
Add, change, or remove windows of days and times for when you can, optionally, allow ARC to start a practice run for a resource.
The format for allowed windows is: DAY:HH:SS-DAY:HH:SS. Keep in mind, when you specify dates, that dates and times for practice runs are in UTC. Also, be aware of potential time adjustments that might be required for daylight saving time differences. Separate multiple allowed windows with spaces.
For example, say you want to allow practice runs only on Wednesdays and Fridays from noon to 5 p.m. For this scenario, you could set the following recurring days and times as allowed windows, for example: Wed-12:00-Wed:17:00 Fri-12:00-Fri:17:00.
The allowedWindows have to start and end on the same day. Windows that span multiple days aren't supported.
Sourcepub fn outcome_alarms(self, input: ControlCondition) -> Self
pub fn outcome_alarms(self, input: ControlCondition) -> Self
Appends an item to outcomeAlarms.
To override the contents of this collection use set_outcome_alarms.
Specify one or more Amazon CloudWatch alarms as the outcome alarms for practice runs.
Sourcepub fn set_outcome_alarms(self, input: Option<Vec<ControlCondition>>) -> Self
pub fn set_outcome_alarms(self, input: Option<Vec<ControlCondition>>) -> Self
Specify one or more Amazon CloudWatch alarms as the outcome alarms for practice runs.
Sourcepub fn get_outcome_alarms(&self) -> &Option<Vec<ControlCondition>>
pub fn get_outcome_alarms(&self) -> &Option<Vec<ControlCondition>>
Specify one or more Amazon CloudWatch alarms as the outcome alarms for practice runs.
Trait Implementations§
Source§impl Clone for UpdatePracticeRunConfigurationFluentBuilder
impl Clone for UpdatePracticeRunConfigurationFluentBuilder
Source§fn clone(&self) -> UpdatePracticeRunConfigurationFluentBuilder
fn clone(&self) -> UpdatePracticeRunConfigurationFluentBuilder
1.0.0 · Source§fn clone_from(&mut self, source: &Self)
fn clone_from(&mut self, source: &Self)
source. Read moreAuto Trait Implementations§
impl Freeze for UpdatePracticeRunConfigurationFluentBuilder
impl !RefUnwindSafe for UpdatePracticeRunConfigurationFluentBuilder
impl Send for UpdatePracticeRunConfigurationFluentBuilder
impl Sync for UpdatePracticeRunConfigurationFluentBuilder
impl Unpin for UpdatePracticeRunConfigurationFluentBuilder
impl !UnwindSafe for UpdatePracticeRunConfigurationFluentBuilder
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);