/** * <p> * For a specified stack that is in the <code>UPDATE_ROLLBACK_FAILED</code> state, continues rolling it back to the * <code>UPDATE_ROLLBACK_COMPLETE</code> state. Depending on the cause of the failure, you can manually <a href= * "http://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/troubleshooting.html#troubleshooting-errors-update-rollback-failed" * > fix the error</a> and continue the rollback. By continuing the rollback, you can return your stack to a working * state (the <code>UPDATE_ROLLBACK_COMPLETE</code> state), and then try to update the stack again. * </p> * <p> * A stack goes into the <code>UPDATE_ROLLBACK_FAILED</code> state when AWS 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 AWS CloudFormation. Because AWS 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. * </p> * * @param continueUpdateRollbackRequest * The input for the <a>ContinueUpdateRollback</a> action. * @return Result of the ContinueUpdateRollback operation returned by the service. * @throws TokenAlreadyExistsException * A client request token already exists. * @sample AmazonCloudFormation.ContinueUpdateRollback * @see <a href="http://docs.aws.amazon.com/goto/WebAPI/cloudformation-2010-05-15/ContinueUpdateRollback" * target="_top">AWS API Documentation</a> */ @Override public ContinueUpdateRollbackResult continueUpdateRollback(ContinueUpdateRollbackRequest request) { request = beforeClientExecution(request); return executeContinueUpdateRollback(request); }
/** * <p> * For a specified stack that is in the <code>UPDATE_ROLLBACK_FAILED</code> state, continues rolling it back to the * <code>UPDATE_ROLLBACK_COMPLETE</code> state. Depending on the cause of the failure, you can manually <a href= * "http://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/troubleshooting.html#troubleshooting-errors-update-rollback-failed" * > fix the error</a> and continue the rollback. By continuing the rollback, you can return your stack to a working * state (the <code>UPDATE_ROLLBACK_COMPLETE</code> state), and then try to update the stack again. * </p> * <p> * A stack goes into the <code>UPDATE_ROLLBACK_FAILED</code> state when AWS 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 AWS CloudFormation. Because AWS 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. * </p> * * @param continueUpdateRollbackRequest * The input for the <a>ContinueUpdateRollback</a> action. * @return Result of the ContinueUpdateRollback operation returned by the service. * @throws TokenAlreadyExistsException * A client request token already exists. * @sample AmazonCloudFormation.ContinueUpdateRollback * @see <a href="http://docs.aws.amazon.com/goto/WebAPI/cloudformation-2010-05-15/ContinueUpdateRollback" * target="_top">AWS API Documentation</a> */ @Override public ContinueUpdateRollbackResult continueUpdateRollback(ContinueUpdateRollbackRequest request) { request = beforeClientExecution(request); return executeContinueUpdateRollback(request); }