feat: revenant

[github-vincent-miszczak]

Fixes #500
We have this issue with our EKS clusters, nuke never completes.

Resources may come back after Remove() because they are managed by other resources that may be removed later (that's the case with EKS and log groups).

I added the opportunity to mark such resources to handle them correctly.

[tudrzal]

Hi, we have the same issue, could this make it into incoming release please?

[TomasMocek]

Hello, perhaps @bjoernhaeuser can have a look?

[bdellegrazie]

@github-vincent-miszczak any chance you could rebase this please?
@bjoernhaeuser / @TomasMocek once rebased, any chance of a review and merge please?

[ekristen]

I like this idea, however I need to research and understand this a bit better before implementing in libnuke and aws-nuke@v3 as such I've opened an issue for tracking purposes ekristen/libnuke#75

If you still feel this is an issue and should be implemented, please comment over there.

---

Please see the 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.