Struct aws_sdk_cloudformation::client::fluent_builders::ContinueUpdateRollback [−][src]
pub struct ContinueUpdateRollback<C = DynConnector, M = AwsMiddleware, R = Standard> { /* fields omitted */ }
Expand description
Fluent builder constructing a request to ContinueUpdateRollback
.
For a specified stack that is in the UPDATE_ROLLBACK_FAILED
state,
continues rolling it back to the UPDATE_ROLLBACK_COMPLETE
state. Depending on
the cause of the failure, you can manually fix the error and continue the rollback. By continuing the rollback, you can
return your stack to a working state (the UPDATE_ROLLBACK_COMPLETE
state), and
then try to update the stack again.
A stack goes into the UPDATE_ROLLBACK_FAILED
state when
CloudFormation cannot roll back all changes after a failed stack update. For example, you
might have a stack that is rolling back to an old database instance that was deleted
outside of CloudFormation. Because CloudFormation doesn't know the database was
deleted, it assumes that the database instance still exists and attempts to roll back to
it, causing the update rollback to fail.
Implementations
impl<C, M, R> ContinueUpdateRollback<C, M, R> where
C: SmithyConnector,
M: SmithyMiddleware<C>,
R: NewRequestPolicy,
impl<C, M, R> ContinueUpdateRollback<C, M, R> where
C: SmithyConnector,
M: SmithyMiddleware<C>,
R: NewRequestPolicy,
pub async fn send(
self
) -> Result<ContinueUpdateRollbackOutput, SdkError<ContinueUpdateRollbackError>> where
R::Policy: SmithyRetryPolicy<ContinueUpdateRollbackInputOperationOutputAlias, ContinueUpdateRollbackOutput, ContinueUpdateRollbackError, ContinueUpdateRollbackInputOperationRetryAlias>,
pub async fn send(
self
) -> Result<ContinueUpdateRollbackOutput, SdkError<ContinueUpdateRollbackError>> where
R::Policy: SmithyRetryPolicy<ContinueUpdateRollbackInputOperationOutputAlias, ContinueUpdateRollbackOutput, ContinueUpdateRollbackError, ContinueUpdateRollbackInputOperationRetryAlias>,
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.
The name or the unique ID of the stack that you want to continue rolling back.
Don't specify the name of a nested stack (a stack that was created by using the
AWS::CloudFormation::Stack
resource). Instead, use this operation on the
parent stack (the stack that contains the AWS::CloudFormation::Stack
resource).
The name or the unique ID of the stack that you want to continue rolling back.
Don't specify the name of a nested stack (a stack that was created by using the
AWS::CloudFormation::Stack
resource). Instead, use this operation on the
parent stack (the stack that contains the AWS::CloudFormation::Stack
resource).
The Amazon Resource Name (ARN) of an Identity and Access Management (IAM) role that CloudFormation assumes to roll back the stack. CloudFormation uses the role's credentials to make calls on your behalf. CloudFormation always uses this role for all future operations on the stack. As long as users have permission to operate on the stack, CloudFormation uses this role even if the users don't have permission to pass it. Ensure that the role grants least privilege.
If you don't specify a value, CloudFormation uses the role that was previously associated with the stack. If no role is available, CloudFormation uses a temporary session that is generated from your user credentials.
The Amazon Resource Name (ARN) of an Identity and Access Management (IAM) role that CloudFormation assumes to roll back the stack. CloudFormation uses the role's credentials to make calls on your behalf. CloudFormation always uses this role for all future operations on the stack. As long as users have permission to operate on the stack, CloudFormation uses this role even if the users don't have permission to pass it. Ensure that the role grants least privilege.
If you don't specify a value, CloudFormation uses the role that was previously associated with the stack. If no role is available, CloudFormation uses a temporary session that is generated from your user credentials.
Appends an item to ResourcesToSkip
.
To override the contents of this collection use set_resources_to_skip
.
A list of the logical IDs of the resources that CloudFormation skips during the
continue update rollback operation. You can specify only resources that are in the
UPDATE_FAILED
state because a rollback failed. You can't specify resources
that are in the UPDATE_FAILED
state for other reasons, for example, because an
update was cancelled. To check why a resource update failed, use the DescribeStackResources action, and view the resource status reason.
Specify this property to skip rolling back resources that CloudFormation
can't successfully roll back. We recommend that you troubleshoot resources before skipping them. CloudFormation sets
the status of the specified resources to UPDATE_COMPLETE
and continues to
roll back the stack. After the rollback is complete, the state of the skipped resources
will be inconsistent with the state of the resources in the stack template. Before
performing another stack update, you must update the stack or resources to be consistent
with each other. If you don't, subsequent stack updates might fail, and the stack will
become unrecoverable.
Specify the minimum number of resources required to successfully roll back your stack. For example, a failed resource update might cause dependent resources to fail. In this case, it might not be necessary to skip the dependent resources.
To skip resources that are part of nested stacks, use the following format:
NestedStackName.ResourceLogicalID
. If you want to specify the logical ID of
a stack resource (Type: AWS::CloudFormation::Stack
) in the
ResourcesToSkip
list, then its corresponding embedded stack must be in one
of the following states: DELETE_IN_PROGRESS
, DELETE_COMPLETE
, or
DELETE_FAILED
.
Don't confuse a child stack's name with its corresponding logical ID defined in the parent stack. For an example of a continue update rollback operation with nested stacks, see Using ResourcesToSkip to recover a nested stacks hierarchy.
A list of the logical IDs of the resources that CloudFormation skips during the
continue update rollback operation. You can specify only resources that are in the
UPDATE_FAILED
state because a rollback failed. You can't specify resources
that are in the UPDATE_FAILED
state for other reasons, for example, because an
update was cancelled. To check why a resource update failed, use the DescribeStackResources action, and view the resource status reason.
Specify this property to skip rolling back resources that CloudFormation
can't successfully roll back. We recommend that you troubleshoot resources before skipping them. CloudFormation sets
the status of the specified resources to UPDATE_COMPLETE
and continues to
roll back the stack. After the rollback is complete, the state of the skipped resources
will be inconsistent with the state of the resources in the stack template. Before
performing another stack update, you must update the stack or resources to be consistent
with each other. If you don't, subsequent stack updates might fail, and the stack will
become unrecoverable.
Specify the minimum number of resources required to successfully roll back your stack. For example, a failed resource update might cause dependent resources to fail. In this case, it might not be necessary to skip the dependent resources.
To skip resources that are part of nested stacks, use the following format:
NestedStackName.ResourceLogicalID
. If you want to specify the logical ID of
a stack resource (Type: AWS::CloudFormation::Stack
) in the
ResourcesToSkip
list, then its corresponding embedded stack must be in one
of the following states: DELETE_IN_PROGRESS
, DELETE_COMPLETE
, or
DELETE_FAILED
.
Don't confuse a child stack's name with its corresponding logical ID defined in the parent stack. For an example of a continue update rollback operation with nested stacks, see Using ResourcesToSkip to recover a nested stacks hierarchy.
A unique identifier for this ContinueUpdateRollback
request. Specify
this token if you plan to retry requests so that CloudFormationknows that you're not
attempting to continue the rollback to a stack with the same name. You might retry
ContinueUpdateRollback
requests to ensure that CloudFormation
successfully received them.
A unique identifier for this ContinueUpdateRollback
request. Specify
this token if you plan to retry requests so that CloudFormationknows that you're not
attempting to continue the rollback to a stack with the same name. You might retry
ContinueUpdateRollback
requests to ensure that CloudFormation
successfully received them.
Trait Implementations
Auto Trait Implementations
impl<C = DynConnector, M = AwsMiddleware, R = Standard> !RefUnwindSafe for ContinueUpdateRollback<C, M, R>
impl<C, M, R> Send for ContinueUpdateRollback<C, M, R> where
C: Send + Sync,
M: Send + Sync,
R: Send + Sync,
impl<C, M, R> Sync for ContinueUpdateRollback<C, M, R> where
C: Send + Sync,
M: Send + Sync,
R: Send + Sync,
impl<C, M, R> Unpin for ContinueUpdateRollback<C, M, R>
impl<C = DynConnector, M = AwsMiddleware, R = Standard> !UnwindSafe for ContinueUpdateRollback<C, M, R>
Blanket Implementations
Mutably borrows from an owned value. Read more
Attaches the provided Subscriber
to this type, returning a
WithDispatch
wrapper. Read more
Attaches the current default Subscriber
to this type, returning a
WithDispatch
wrapper. Read more