Email Action Support #397
Draft
Email Action Support #397
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Implementing email action support for the few detections we have that depend on them.
I've avoided integration with deployments, partly because it didn't make sense to add email support at this level, also because that functionality is still a bit of a mystery to me.
Draft for feedback and contributions. I'm aware that there is limited validation, Pydantic is a beast that I have yet to wrangle in any meaningful way!
P.S. I would love to try and tackle the implementation of webhook and threat intelligence action support in the not too distant future, email is just the easiest of the bunch to start with...