elastic / elastic/elastic-package
`elastic-package export security_rules`
- Dominant language
- Go
- Stars
- 72
- Forks
- 141
- Avg merge
- 19h 42m
- Merged PRs (30d)
- 55
Description
An `elastic-package export security_rules` command could provide the functionality in [`export-rules.sh`](https://gist.github.com/chrisberkhout/74f19f60b0708dc51984a834ec47758b).
Security rules can't be exported manually in Kibana, as **Stack Management > Saved objects > Inspect alert** provides a version of a security rule that isn't ready for use in an integration package.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reading the linked export-rules.sh to understand the intended security-rule export workflow, then inspect the existing `elastic-package export` command entry point. Done means `elastic-package export security_rules` produces security rules that are ready for use in an integration package, rather than the unusable Kibana saved-object output.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100