feat(integrations): Much integrations so wow #166
Merged
Conversation
This file contains 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
topher-lo
force-pushed
the
feat/move-uim-integrations
branch
from
fc28a1c
to
5b2ae97
Compare
topher-lo
force-pushed
the
feat/move-uim-integrations
branch
from
5b2ae97
to
f1ae630
Compare
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.
What does this implement/fix? Explain your changes.
Lots of integrations categorized into ~7 automation "capabilities" and 10+ vendors:
More to come.
Any other comments?
Unit testing is non-trivial due to authentication. The most robustly tested APIs are ones that are API based (e.g. threat intelligence), the ones related to AWS, and Tracecat custom capabilities (e.g. PII extraction via regex).