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
* Added new cli flag to exclude tactic name in rule file name
* added a shortcut for the flag and adjusted CLI readme
* Add no tactic flag also to import to prevent warnings
* Added info about unit test
* version bump
* Added no_tactic_filename as config option + fixed linting
* pyproject version bump
---------
Co-authored-by: Mika Ayenson, PhD <[email protected]>
Co-authored-by: Eric Forte <[email protected]>
Copy file name to clipboardExpand all lines: CLI.md
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -265,6 +265,7 @@ Options:
265
265
-e, --overwrite-exceptions Overwrite exceptions in existing rules
266
266
-ac, --overwrite-action-connectors
267
267
Overwrite action connectors in existing rules
268
+
-nt, --no-tactic-filename Allow rule filenames without tactic prefix. Use this if rules have been exported with this flag.
268
269
-h, --help Show this message and exit.
269
270
```
270
271
@@ -520,6 +521,7 @@ Options:
520
521
-e, --export-exceptions Include exceptions in export
521
522
-s, --skip-errors Skip errors when exporting rules
522
523
-sv, --strip-version Strip the version fields from all rules
524
+
-nt, --no-tactic-filename Exclude tactic prefix in exported filenames for rules. Use same flag for import-rules to prevent warnings and disable its unit test.
Copy file name to clipboardExpand all lines: docs-dev/custom-rules-management.md
+3-1Lines changed: 3 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -94,8 +94,10 @@ be set in `_config.yaml` or as the environment variable `DETECTION_RULES_TEST_CO
94
94
environment variable if both are set. Having both these options allows for configuring testing on prebuilt Elastic rules
95
95
without specifying a rules _config.yaml.
96
96
97
+
Some notes:
97
98
98
-
* Note: If set in this file, the path should be relative to the location of this config. If passed as an environment variable, it should be the full path
99
+
* If set in this file, the path should be relative to the location of this config. If passed as an environment variable, it should be the full path
100
+
* When using the `--no-tactic-filename` flag for kibana imports and exports, be sure to disable the unit test by using the following line `- tests.test_all_rules.TestRuleFiles.test_rule_file_name_tactic` in your test config file.
99
101
100
102
101
103
### How the config is used and it's designed portability
Copy file name to clipboardExpand all lines: pyproject.toml
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
[project]
2
2
name = "detection_rules"
3
-
version = "1.0.10"
3
+
version = "1.0.11"
4
4
description = "Detection Rules is the home for rules used by Elastic Security. This repository is used for the development, maintenance, testing, validation, and release of rules for Elastic Security’s Detection Engine."
0 commit comments