amplify delete does not remove S3 deployment bucket about amplify-cli

[kaustavghosh06]

@jaxondu Yes, we are aware of the S3 deployment buckets not getting deleted due to the limitation of Cloudformation of not deleting S3 buckets with content in it.
That's the reason we have associated an "experimental" tag to the amplify delete command in the main README.md to get user feedback on this and then proceed with the next steps.
Thanks for the feedback.

[shasan-marsdd]

when rollback happens due to errors such as permissions (setting it up for users in our organization that shouldn't have full admin permissions). "amplify init" or "amplify env add" fails due to "failed to create bucket, it already exists". Even after we fix the permissions, deployment doesn't happen without manual delete of the buckets (not deployment, but other buckets such as hosting etc). On a deployment that fails and rolls back it should deleting the bucket.

[github-actions]

This issue has been automatically locked since there hasn't been any recent activity after it was closed. Please open a new issue for related bugs.

Looking for a help forum? We recommend joining the Amplify Community Discord server *-help channels for those types of questions.