Closed bjfish25 closed 2 months ago
@bjfish25 This issue and it's associated PR #1237 has been implemented over on the now active fork of aws-nuke via https://github.com/ekristen/aws-nuke/pull/234
Please see a copy of the notice from the README about the deprecation of this project. Sven was kind enough to grant me access to help triage and close issues and pull requests that have already been addressed in the actively maintained fork. Some additional information is located in the welcome issue for more information.
[!CAUTION] This repository for aws-nuke is no longer being actively maintained. We recommend users to switch to the actively maintained fork of this project at ekristen/aws-nuke. We appreciate all the support and contributions we've received throughout the life of this project. We believe that the fork will continue to provide the functionality and support that you have come to expect from aws-nuke. Please note that this deprecation means we will not be addressing issues, accepting pull requests, or making future releases from this repository. Thank you for your understanding and support.
https://aws.amazon.com/about-aws/whats-new/2023/03/amazon-dynamodb-table-deletion-protection/
aws-nuke should offer a flag to bypass it similar to other services
PR: https://github.com/rebuy-de/aws-nuke/pull/1237