#[non_exhaustive]pub struct ZonalConfigBuilder { /* private fields */ }
Expand description
A builder for ZonalConfig
.
Implementations§
Source§impl ZonalConfigBuilder
impl ZonalConfigBuilder
Sourcepub fn first_zone_monitor_duration_in_seconds(self, input: i64) -> Self
pub fn first_zone_monitor_duration_in_seconds(self, input: i64) -> Self
The period of time, in seconds, that CodeDeploy must wait after completing a deployment to the first Availability Zone. CodeDeploy will wait this amount of time before starting a deployment to the second Availability Zone. You might set this option if you want to allow extra bake time for the first Availability Zone. If you don't specify a value for firstZoneMonitorDurationInSeconds
, then CodeDeploy uses the monitorDurationInSeconds
value for the first Availability Zone.
For more information about the zonal configuration feature, see zonal configuration in the CodeDeploy User Guide.
Sourcepub fn set_first_zone_monitor_duration_in_seconds(
self,
input: Option<i64>,
) -> Self
pub fn set_first_zone_monitor_duration_in_seconds( self, input: Option<i64>, ) -> Self
The period of time, in seconds, that CodeDeploy must wait after completing a deployment to the first Availability Zone. CodeDeploy will wait this amount of time before starting a deployment to the second Availability Zone. You might set this option if you want to allow extra bake time for the first Availability Zone. If you don't specify a value for firstZoneMonitorDurationInSeconds
, then CodeDeploy uses the monitorDurationInSeconds
value for the first Availability Zone.
For more information about the zonal configuration feature, see zonal configuration in the CodeDeploy User Guide.
Sourcepub fn get_first_zone_monitor_duration_in_seconds(&self) -> &Option<i64>
pub fn get_first_zone_monitor_duration_in_seconds(&self) -> &Option<i64>
The period of time, in seconds, that CodeDeploy must wait after completing a deployment to the first Availability Zone. CodeDeploy will wait this amount of time before starting a deployment to the second Availability Zone. You might set this option if you want to allow extra bake time for the first Availability Zone. If you don't specify a value for firstZoneMonitorDurationInSeconds
, then CodeDeploy uses the monitorDurationInSeconds
value for the first Availability Zone.
For more information about the zonal configuration feature, see zonal configuration in the CodeDeploy User Guide.
Sourcepub fn monitor_duration_in_seconds(self, input: i64) -> Self
pub fn monitor_duration_in_seconds(self, input: i64) -> Self
The period of time, in seconds, that CodeDeploy must wait after completing a deployment to an Availability Zone. CodeDeploy will wait this amount of time before starting a deployment to the next Availability Zone. Consider adding a monitor duration to give the deployment some time to prove itself (or 'bake') in one Availability Zone before it is released in the next zone. If you don't specify a monitorDurationInSeconds
, CodeDeploy starts deploying to the next Availability Zone immediately.
For more information about the zonal configuration feature, see zonal configuration in the CodeDeploy User Guide.
Sourcepub fn set_monitor_duration_in_seconds(self, input: Option<i64>) -> Self
pub fn set_monitor_duration_in_seconds(self, input: Option<i64>) -> Self
The period of time, in seconds, that CodeDeploy must wait after completing a deployment to an Availability Zone. CodeDeploy will wait this amount of time before starting a deployment to the next Availability Zone. Consider adding a monitor duration to give the deployment some time to prove itself (or 'bake') in one Availability Zone before it is released in the next zone. If you don't specify a monitorDurationInSeconds
, CodeDeploy starts deploying to the next Availability Zone immediately.
For more information about the zonal configuration feature, see zonal configuration in the CodeDeploy User Guide.
Sourcepub fn get_monitor_duration_in_seconds(&self) -> &Option<i64>
pub fn get_monitor_duration_in_seconds(&self) -> &Option<i64>
The period of time, in seconds, that CodeDeploy must wait after completing a deployment to an Availability Zone. CodeDeploy will wait this amount of time before starting a deployment to the next Availability Zone. Consider adding a monitor duration to give the deployment some time to prove itself (or 'bake') in one Availability Zone before it is released in the next zone. If you don't specify a monitorDurationInSeconds
, CodeDeploy starts deploying to the next Availability Zone immediately.
For more information about the zonal configuration feature, see zonal configuration in the CodeDeploy User Guide.
Sourcepub fn minimum_healthy_hosts_per_zone(
self,
input: MinimumHealthyHostsPerZone,
) -> Self
pub fn minimum_healthy_hosts_per_zone( self, input: MinimumHealthyHostsPerZone, ) -> Self
The number or percentage of instances that must remain available per Availability Zone during a deployment. This option works in conjunction with the MinimumHealthyHosts
option. For more information, see About the minimum number of healthy hosts per Availability Zone in the CodeDeploy User Guide.
If you don't specify the minimumHealthyHostsPerZone
option, then CodeDeploy uses a default value of 0
percent.
For more information about the zonal configuration feature, see zonal configuration in the CodeDeploy User Guide.
Sourcepub fn set_minimum_healthy_hosts_per_zone(
self,
input: Option<MinimumHealthyHostsPerZone>,
) -> Self
pub fn set_minimum_healthy_hosts_per_zone( self, input: Option<MinimumHealthyHostsPerZone>, ) -> Self
The number or percentage of instances that must remain available per Availability Zone during a deployment. This option works in conjunction with the MinimumHealthyHosts
option. For more information, see About the minimum number of healthy hosts per Availability Zone in the CodeDeploy User Guide.
If you don't specify the minimumHealthyHostsPerZone
option, then CodeDeploy uses a default value of 0
percent.
For more information about the zonal configuration feature, see zonal configuration in the CodeDeploy User Guide.
Sourcepub fn get_minimum_healthy_hosts_per_zone(
&self,
) -> &Option<MinimumHealthyHostsPerZone>
pub fn get_minimum_healthy_hosts_per_zone( &self, ) -> &Option<MinimumHealthyHostsPerZone>
The number or percentage of instances that must remain available per Availability Zone during a deployment. This option works in conjunction with the MinimumHealthyHosts
option. For more information, see About the minimum number of healthy hosts per Availability Zone in the CodeDeploy User Guide.
If you don't specify the minimumHealthyHostsPerZone
option, then CodeDeploy uses a default value of 0
percent.
For more information about the zonal configuration feature, see zonal configuration in the CodeDeploy User Guide.
Sourcepub fn build(self) -> ZonalConfig
pub fn build(self) -> ZonalConfig
Consumes the builder and constructs a ZonalConfig
.
Trait Implementations§
Source§impl Clone for ZonalConfigBuilder
impl Clone for ZonalConfigBuilder
Source§fn clone(&self) -> ZonalConfigBuilder
fn clone(&self) -> ZonalConfigBuilder
1.0.0 · Source§fn clone_from(&mut self, source: &Self)
fn clone_from(&mut self, source: &Self)
source
. Read moreSource§impl Debug for ZonalConfigBuilder
impl Debug for ZonalConfigBuilder
Source§impl Default for ZonalConfigBuilder
impl Default for ZonalConfigBuilder
Source§fn default() -> ZonalConfigBuilder
fn default() -> ZonalConfigBuilder
Source§impl PartialEq for ZonalConfigBuilder
impl PartialEq for ZonalConfigBuilder
impl StructuralPartialEq for ZonalConfigBuilder
Auto Trait Implementations§
impl Freeze for ZonalConfigBuilder
impl RefUnwindSafe for ZonalConfigBuilder
impl Send for ZonalConfigBuilder
impl Sync for ZonalConfigBuilder
impl Unpin for ZonalConfigBuilder
impl UnwindSafe for ZonalConfigBuilder
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);