From feaa4d418c84155d806e795754130f2aea03f270 Mon Sep 17 00:00:00 2001 From: Ben Larabie Date: Tue, 8 Oct 2024 11:17:09 -0400 Subject: [PATCH] debug --- scripts/deleteEnvironment.sh | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/scripts/deleteEnvironment.sh b/scripts/deleteEnvironment.sh index d291dc6f3..4e7c9ec14 100755 --- a/scripts/deleteEnvironment.sh +++ b/scripts/deleteEnvironment.sh @@ -55,7 +55,7 @@ echo "Done." # Run the first round of aws-nuke. It will eventually end up in a loop where it can't delete some resources. This is expected. # After 100 retries, it will stop and we will run it again. echo "Starting first round of aws-nuke..." -aws-nuke run -c awsNuke.cfg --quiet --no-dry-run --max-wait-retries 100 --force --log-level error +aws-nuke run -c awsNuke.cfg --quiet --no-dry-run --max-wait-retries 100 --force -l trace echo "Done." # Sleep 5 minutes to make sure any lingering resources from the above aws-nuke run are deleted @@ -65,7 +65,7 @@ echo "Done." # Run the second round of aws-nuke. This should delete all remaining resources. echo "Starting second round of aws-nuke..." -aws-nuke run -c awsNuke.cfg --quiet --no-dry-run --max-wait-retries 300 --force --log-level error +aws-nuke run -c awsNuke.cfg --quiet --no-dry-run --max-wait-retries 300 --force -l trace echo "Done." # aws-nuke can't delete the below resources because they are part of a account-wide blacklist in the aws-nuke config