#[non_exhaustive]pub struct RollbackConfiguration {
pub rollback_triggers: Option<Vec<RollbackTrigger>>,
pub monitoring_time_in_minutes: Option<i32>,
}
Expand description
Structure containing the rollback triggers for CloudFormation to monitor during stack creation and updating operations, and for the specified monitoring period afterwards.
Rollback triggers enable you to have CloudFormation monitor the state of your application during stack creation and updating, and to roll back that operation if the application breaches the threshold of any of the alarms you've specified. For more information, see Monitor and Roll Back Stack Operations.
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.rollback_triggers: 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.
monitoring_time_in_minutes: 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.
Implementations§
source§impl RollbackConfiguration
impl RollbackConfiguration
sourcepub fn rollback_triggers(&self) -> &[RollbackTrigger]
pub fn rollback_triggers(&self) -> &[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.
If no value was sent for this field, a default will be set. If you want to determine if no value was sent, use .rollback_triggers.is_none()
.
sourcepub fn monitoring_time_in_minutes(&self) -> Option<i32>
pub fn 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.
source§impl RollbackConfiguration
impl RollbackConfiguration
sourcepub fn builder() -> RollbackConfigurationBuilder
pub fn builder() -> RollbackConfigurationBuilder
Creates a new builder-style object to manufacture RollbackConfiguration
.
Trait Implementations§
source§impl Clone for RollbackConfiguration
impl Clone for RollbackConfiguration
source§fn clone(&self) -> RollbackConfiguration
fn clone(&self) -> RollbackConfiguration
1.0.0 · source§fn clone_from(&mut self, source: &Self)
fn clone_from(&mut self, source: &Self)
source
. Read moresource§impl Debug for RollbackConfiguration
impl Debug for RollbackConfiguration
source§impl PartialEq for RollbackConfiguration
impl PartialEq for RollbackConfiguration
source§fn eq(&self, other: &RollbackConfiguration) -> bool
fn eq(&self, other: &RollbackConfiguration) -> bool
self
and other
values to be equal, and is used
by ==
.impl StructuralPartialEq for RollbackConfiguration
Auto Trait Implementations§
impl Freeze for RollbackConfiguration
impl RefUnwindSafe for RollbackConfiguration
impl Send for RollbackConfiguration
impl Sync for RollbackConfiguration
impl Unpin for RollbackConfiguration
impl UnwindSafe for RollbackConfiguration
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