-
Notifications
You must be signed in to change notification settings - Fork 8.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Security Solution] [Platform] Migrate pre-8.0 action connector ids in rule params on import to post-8.0 _id #120975
Merged
Merged
Changes from all commits
Commits
Show all changes
23 commits
Select commit
Hold shift + click to select a range
6f29df4
WIP
dhurley14 ee3e7d1
WIP
dhurley14 fa8b09f
working with actions client resolve
dhurley14 4b43eb5
use elasticsearch instead of saved objects client resolve api
dhurley14 8c40aad
cleanup
dhurley14 45e40bd
more cleanup
dhurley14 9adc3db
updates comments and a little bit of cleanup
dhurley14 14f2d95
undo change
dhurley14 a8ac8be
cleanup
dhurley14 f21d717
merge main into branch
dhurley14 67836fa
fix typecheck failure
dhurley14 83b7d70
some error handling and added jest tests for swapActionIds and migrat…
dhurley14 33dffbb
only find origin id for action saved objects
dhurley14 19b1862
Merge branch 'main' into migrate-imported-actions
kibanamachine 50a2b40
replacd es client with scoped SO client including hidden objects
dhurley14 9e0be05
fix jest tests to use mocked SO client
dhurley14 af7de37
Merge remote-tracking branch 'upstream/main' into migrate-imported-ac…
dhurley14 2ff74da
add more integration tests
dhurley14 ced8410
fixes comments
dhurley14 0262eb4
updates from PR comments
dhurley14 e80a271
Merge remote-tracking branch 'upstream/main' into migrate-imported-ac…
dhurley14 8ee2dc4
updates expected error message in jest test
dhurley14 a90ec5a
nest pMaps - pMap over rule.actions in case the number of promises is…
dhurley14 File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Action
here inmigrateLegacyActionIds
refers to connectors right? Wondering if we should have the same language betweenmigrateLegacyActionIds
andgetInvalidConnectors
. Or is one dealing with the rule action objects and he other dealing with the connectors?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is a similar issue to when rules were known as "alerts" because they were alerting SO's. The security solution calls SO
actions
as actions but they are known to kibana alerting as action connectors. My thinking is to follow the same guidance we used between "rules" and "alerts" back when they meant the same thing ('alert' SO types) where we called them rules in the security solution. I believe since the precedent is for connectors to be called 'actions' in the security solution we should continue to use that terminology in the code.