Cloudformation stack fails to delete when resources don't exist

[fridim]

aws-nuke fails to delete a stack in DELETE_FAILED state with resources to delete marked as DELETE_FAILED because the resources don't exist anymore.

aws-nuke has a mechanism to only retain resources not DELETE_COMPLETE.

		for _, r := range retainableResources.StackResourceSummaries {
			if *r.ResourceStatus != cloudformation.ResourceStatusDeleteComplete {
				retain = append(retain, r.LogicalResourceId)
			}
		}

Suggestion: aws-nuke could exclude resources that don't exist anymore.

another option if it's hard to prove they don't exist: if they consistently fail deleting as part of the stack, is it safe to exclude them and leave the deletion to aws-nuke outside of the stack?

[ekristen]

Interesting. Any clue on how to replicate this?