#[non_exhaustive]pub struct RollbackConfigurationBuilder { /* private fields */ }
Expand description
A builder for RollbackConfiguration
.
Implementations§
source§impl RollbackConfigurationBuilder
impl RollbackConfigurationBuilder
sourcepub fn rollback_triggers(self, input: RollbackTrigger) -> Self
pub fn rollback_triggers(self, input: RollbackTrigger) -> Self
Appends an item to rollback_triggers
.
To override the contents of this collection use set_rollback_triggers
.
The triggers to monitor during stack creation or update actions.
By default, CloudFormation saves the rollback triggers specified for a stack and applies them to any subsequent update operations for the stack, unless you specify otherwise. If you do specify rollback triggers for this parameter, those triggers replace any list of triggers previously specified for the stack. This means:
-
To use the rollback triggers previously specified for this stack, if any, don't specify this parameter.
-
To specify new or updated rollback triggers, you must specify all the triggers that you want used for this stack, even triggers you've specified before (for example, when creating the stack or during a previous stack update). Any triggers that you don't include in the updated list of triggers are no longer applied to the stack.
-
To remove all currently specified triggers, specify an empty list for this parameter.
If a specified trigger is missing, the entire stack operation fails and is rolled back.
sourcepub fn set_rollback_triggers(self, input: Option<Vec<RollbackTrigger>>) -> Self
pub fn set_rollback_triggers(self, input: Option<Vec<RollbackTrigger>>) -> Self
The triggers to monitor during stack creation or update actions.
By default, CloudFormation saves the rollback triggers specified for a stack and applies them to any subsequent update operations for the stack, unless you specify otherwise. If you do specify rollback triggers for this parameter, those triggers replace any list of triggers previously specified for the stack. This means:
-
To use the rollback triggers previously specified for this stack, if any, don't specify this parameter.
-
To specify new or updated rollback triggers, you must specify all the triggers that you want used for this stack, even triggers you've specified before (for example, when creating the stack or during a previous stack update). Any triggers that you don't include in the updated list of triggers are no longer applied to the stack.
-
To remove all currently specified triggers, specify an empty list for this parameter.
If a specified trigger is missing, the entire stack operation fails and is rolled back.
sourcepub fn get_rollback_triggers(&self) -> &Option<Vec<RollbackTrigger>>
pub fn get_rollback_triggers(&self) -> &Option<Vec<RollbackTrigger>>
The triggers to monitor during stack creation or update actions.
By default, CloudFormation saves the rollback triggers specified for a stack and applies them to any subsequent update operations for the stack, unless you specify otherwise. If you do specify rollback triggers for this parameter, those triggers replace any list of triggers previously specified for the stack. This means:
-
To use the rollback triggers previously specified for this stack, if any, don't specify this parameter.
-
To specify new or updated rollback triggers, you must specify all the triggers that you want used for this stack, even triggers you've specified before (for example, when creating the stack or during a previous stack update). Any triggers that you don't include in the updated list of triggers are no longer applied to the stack.
-
To remove all currently specified triggers, specify an empty list for this parameter.
If a specified trigger is missing, the entire stack operation fails and is rolled back.
sourcepub fn monitoring_time_in_minutes(self, input: i32) -> Self
pub fn monitoring_time_in_minutes(self, input: i32) -> Self
The amount of time, in minutes, during which CloudFormation should monitor all the rollback triggers after the stack creation or update operation deploys all necessary resources.
The default is 0 minutes.
If you specify a monitoring period but don't specify any rollback triggers, CloudFormation still waits the specified period of time before cleaning up old resources after update operations. You can use this monitoring period to perform any manual stack validation desired, and manually cancel the stack creation or update (using CancelUpdateStack, for example) as necessary.
If you specify 0 for this parameter, CloudFormation still monitors the specified rollback triggers during stack creation and update operations. Then, for update operations, it begins disposing of old resources immediately once the operation completes.
sourcepub fn set_monitoring_time_in_minutes(self, input: Option<i32>) -> Self
pub fn set_monitoring_time_in_minutes(self, input: Option<i32>) -> Self
The amount of time, in minutes, during which CloudFormation should monitor all the rollback triggers after the stack creation or update operation deploys all necessary resources.
The default is 0 minutes.
If you specify a monitoring period but don't specify any rollback triggers, CloudFormation still waits the specified period of time before cleaning up old resources after update operations. You can use this monitoring period to perform any manual stack validation desired, and manually cancel the stack creation or update (using CancelUpdateStack, for example) as necessary.
If you specify 0 for this parameter, CloudFormation still monitors the specified rollback triggers during stack creation and update operations. Then, for update operations, it begins disposing of old resources immediately once the operation completes.
sourcepub fn get_monitoring_time_in_minutes(&self) -> &Option<i32>
pub fn get_monitoring_time_in_minutes(&self) -> &Option<i32>
The amount of time, in minutes, during which CloudFormation should monitor all the rollback triggers after the stack creation or update operation deploys all necessary resources.
The default is 0 minutes.
If you specify a monitoring period but don't specify any rollback triggers, CloudFormation still waits the specified period of time before cleaning up old resources after update operations. You can use this monitoring period to perform any manual stack validation desired, and manually cancel the stack creation or update (using CancelUpdateStack, for example) as necessary.
If you specify 0 for this parameter, CloudFormation still monitors the specified rollback triggers during stack creation and update operations. Then, for update operations, it begins disposing of old resources immediately once the operation completes.
sourcepub fn build(self) -> RollbackConfiguration
pub fn build(self) -> RollbackConfiguration
Consumes the builder and constructs a RollbackConfiguration
.
Trait Implementations§
source§impl Clone for RollbackConfigurationBuilder
impl Clone for RollbackConfigurationBuilder
source§fn clone(&self) -> RollbackConfigurationBuilder
fn clone(&self) -> RollbackConfigurationBuilder
1.0.0 · source§fn clone_from(&mut self, source: &Self)
fn clone_from(&mut self, source: &Self)
source
. Read moresource§impl Debug for RollbackConfigurationBuilder
impl Debug for RollbackConfigurationBuilder
source§impl Default for RollbackConfigurationBuilder
impl Default for RollbackConfigurationBuilder
source§fn default() -> RollbackConfigurationBuilder
fn default() -> RollbackConfigurationBuilder
source§impl PartialEq for RollbackConfigurationBuilder
impl PartialEq for RollbackConfigurationBuilder
source§fn eq(&self, other: &RollbackConfigurationBuilder) -> bool
fn eq(&self, other: &RollbackConfigurationBuilder) -> bool
self
and other
values to be equal, and is used
by ==
.impl StructuralPartialEq for RollbackConfigurationBuilder
Auto Trait Implementations§
impl Freeze for RollbackConfigurationBuilder
impl RefUnwindSafe for RollbackConfigurationBuilder
impl Send for RollbackConfigurationBuilder
impl Sync for RollbackConfigurationBuilder
impl Unpin for RollbackConfigurationBuilder
impl UnwindSafe for RollbackConfigurationBuilder
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> 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 more