Include sendcsv parameter for email alert action
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 139
- Forks
- 52
- Avg merge
- 1h 16m
- Merged PRs (30d)
- 3
Description
Is your feature request related to a problem? Please describe.
Allow the results to be attached as CSV when this option is enabled for the email alert action.
Describe the solution you'd like
When the sendcsv key is defined as 'true':
deployment:
alert_action:
email:
sendcsv: 'true'
, then it's set through the jinja2 template:
{% if detection.deployment.alert_action.email.sendcsv %}
action.email.sendcsv = 1
{% endif %}
Describe alternatives you've considered
We can of course set it through the Spunk UI or REST API, but the preference is to use DaC as much as possible.
Additional context
N/A
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the Jinja2 template that renders deployment.alert_action.email and trace how the YAML sendcsv value is loaded. Done means a true sendcsv setting produces the requested action.email.sendcsv output, with coverage for the enabled and unset cases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100