fix(cli): deployments are skipped if stack is in a _failed state (#10847

)

fixes #10784


----

*By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*

packages/aws-cdk/lib/api/deploy-stack.ts

@@ -440,6 +440,12 @@ async function canSkipDeploy(
     return false;
   }
 
+  // Existing stack is in a failed state
+  if (cloudFormationStack.stackStatus.isFailure) {
+    debug(`${deployName}: stack is in a failure state`);
+    return false;
+  }
+
   // We can skip deploy
   return true;
 }

packages/aws-cdk/test/api/deploy-stack.test.ts

@@ -423,6 +423,25 @@ test('deploy not skipped if template did not change but one tag removed', async
   expect(cfnMocks.getTemplate).toHaveBeenCalledWith({ StackName: 'withouterrors', TemplateStage: 'Original' });
 });
 
+test('deploy is not skipped if stack is in a _FAILED state', async () => {
+  // GIVEN
+  givenStackExists({
+    StackStatus: 'DELETE_FAILED',
+  });
+
+  // WHEN
+  await deployStack({
+    stack: FAKE_STACK,
+    sdk,
+    sdkProvider,
+    resolvedEnvironment: mockResolvedEnvironment(),
+    usePreviousParameters: true,
+  }).catch(() => {});
+
+  // THEN
+  expect(cfnMocks.createChangeSet).toHaveBeenCalled();
+});
+
 test('existing stack in UPDATE_ROLLBACK_COMPLETE state can be updated', async () => {
   // GIVEN
   givenStackExists(