Pre-requisite: force_destroy on S3 buckets
By default, if your Terraform code includes an S3 bucket, when you run terraform destroy, if that bucket contains
any content, Terraform will not delete the bucket and instead will give you an error like this:
bucketNotEmpty: The bucket you tried to delete is not empty. You must delete all versions in the bucket.
This is a safety mechanism to ensure that you don't accidentally delete your data.
If you are absolutely sure you want to delete the contents of an S3 bucket (remember, there's no undo!!!), all the
services that use S3 buckets expose a force_destroy setting that you can set to true in your terragrunt.hcl
files to tell that service to delete the contents of the bucket when you run destroy. Here's a partial list of
services that expose this variable (note, you may not have all of these in your Reference Architecture!):
networking/albmgmt/openvpn-serverlandingzone/account-baseline-appservices/k8s-service