aws-nuke
aws-nuke copied to clipboard
feat: revenant
Fixes https://github.com/rebuy-de/aws-nuke/issues/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.
Hi, we have the same issue, could this make it into incoming release please?
Hello, perhaps @bjoernhaeuser can have a look?
@github-vincent-miszczak any chance you could rebase this please? @bjoernhaeuser / @TomasMocek once rebased, any chance of a review and merge please?