-
## Original Post
> In current state when you use a `dateOlderThan` filter, it'll return an error if it comes across a resource/field that it cannot parse as a date, and will prevent `aws-nuke` from…
-
While migrating from rebuy-de/aws-nuke to libnuke in https://github.com/fluxcd/test-infra/pull/39, aws-nuke failed to delete EKSCluster. There were multiple errors. Some of them related to removing ro…
-
## Overview
This is going to be a HUGE lift, however libnuke has already eased it a bit by providing context passing.
AWS SDK v1 is EOL June 31, 2025. We need to be swapped to AWS SDK v2 by then…
-
Version: `3.3.2`
When resource filtering is in place via `tag`s, some resources aren't filtered out. For this preset:
```yaml
presets:
common:
filters:
global:
- propert…
-
Sorry to bring another issue 😅 it looks like I will be your testing ground.
Noticed another error in nuke dry run today:
> time="2024-07-30T12:41:31Z" level=error msg="Listing SecretsManagerS…
-
I've seen in nuke logs multiple times errors like
```
time="2024-07-29T15:48:21Z" level=warning component=libnuke error="*resources.CloudWatchDashboard does not support custom properties" handler…
-
> I'm very happy to see this issue already exists, as I was disappointed to see that there are quite a lot of resource types where tags are not fetched. By my very rough count (grep'ing for `tag` in t…
-
Rather than rely on string parsing such as this tool [oijkn/aws-nuke-exporter](https://github.com/oijkn/aws-nuke-exporter), `aws-nuke` could have an option to output structured logs (`--output` or `--…
so0k updated
2 months ago
-
version: 3.5.1
after running successfully in no-dry-run a few times all the way to completion, randomly received the following SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x43557ff on an a…
-
Version: 3.2.2
### Minimal Config
```yaml
regions:
- global
- eu-central-1
presets:
common:
filters:
global:
- property: "tag:to-delete/.*"
type: "rege…