You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
run, nuke run nuke against an aws account and remove everything from it
20
+
resource-types, list-resources list available resources to nuke
21
+
help, h Shows a list of commands or help for one command
22
+
23
+
GLOBAL OPTIONS:
24
+
--help, -h show help
25
+
--version, -v print the version
26
+
```
27
+
28
+
## aws-nuke run
29
+
30
+
```console
31
+
NAME:
32
+
aws-nuke run - run nuke against an aws account and remove everything from it
33
+
34
+
USAGE:
35
+
aws-nuke run [command options] [arguments...]
36
+
37
+
OPTIONS:
38
+
--config value path to config file (default: "config.yaml")
39
+
--force disable prompting for verification to run (default: false)
40
+
--force-sleep value seconds to sleep (default: 10)
41
+
--quiet hide filtered messages (default: false)
42
+
--no-dry-run actually run the removal of the resources after discovery (default: false)
43
+
--only-resource value, --target value, --include value, --include-resource value [ --only-resource value, --target value, --include value, --include-resource value ] only run against these resource types
44
+
--exclude-resource value, --exclude value [ --exclude-resource value, --exclude value ] exclude these resource types
45
+
--cloud-control value [ --cloud-control value ] use these resource types with the Cloud Control API instead of the default
46
+
--feature-flag value [ --feature-flag value ] enable experimental behaviors that may not be fully tested or supported
47
+
--log-level value, -l value Log Level (default: "info") [$LOGLEVEL]
48
+
--log-caller log the caller (aka line number and file) (default: false)
Copy file name to clipboardExpand all lines: docs/config-filtering.md
+19-3Lines changed: 19 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -73,16 +73,32 @@ IAMUser:
73
73
74
74
### DateOlderThan
75
75
76
-
The identifier is parsed as a timestamp. After the offset is added to it (specified in the `value` field), the resulting
77
-
timestamp must be AFTER the current time. Details on offset syntax can be found in the [library documentation](https://golang.org/pkg/time/#ParseDuration).
78
-
Supported date formats are epoch time:
76
+
This works by parsing the specified property into a timestamp and comparing it to the current time minus the specified
77
+
duration. The duration is specified in the `value` field. The duration syntax is based on golang's duration syntax.
78
+
79
+
> ParseDuration parses a duration string. A duration string is a possibly signed sequence of decimal numbers, each with
80
+
> optional fraction and a unit suffix, such as "300ms", "-1.5h" or "2h45m". Valid time units are "ns", "us" (or "µs"),
81
+
> "ms", "s", "m", "h".
82
+
83
+
Full details on duration syntax can be found in the [time library documentation](https://golang.org/pkg/time/#ParseDuration).
84
+
85
+
The value from the property is parsed as a timestamp and the following are the supported formats:
79
86
80
87
- `2006-01-02`
81
88
- `2006/01/02`
82
89
- `2006-01-02T15:04:05Z`
83
90
- `2006-01-02T15:04:05.999999999Z07:00`
84
91
- `2006-01-02T15:04:05Z07:00`
85
92
93
+
In the follow example we are filtering EC2 Images that have a `CreationDate` older than 1 hour.
94
+
95
+
```yaml
96
+
EC2Image:
97
+
- type: dateOlderThan
98
+
property: CreationDate
99
+
value: 1h
100
+
```
101
+
86
102
## Properties
87
103
88
104
By default, when writing a filter if you do not specify a property, it will use the `Name` property. However, resources
0 commit comments