-
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][Endpoint][Exceptions] Only write manifest to policy when there are changes #72000
Merged
Merged
[Security Solution][Endpoint][Exceptions] Only write manifest to policy when there are changes #72000
Changes from 16 commits
Commits
Show all changes
18 commits
Select commit
Hold shift + click to select a range
936b498
Refactor security_solution policy creation callback - part 1
madirey 8392372
Fix manifest dispatch
madirey 17316b4
Change how dispatches are performed
madirey ac6a453
simplify manifest types
madirey a8cc143
Merge branch 'master' of github.com:elastic/kibana into policy-creati…
madirey c8516fb
Remove unused mock
madirey 045c470
Fix tests
madirey eaf1cfa
Merge branch 'master' of github.com:elastic/kibana into policy-creati…
madirey 4ec51cb
one place to construct artifact ids
madirey a2fc28a
fixing linter exceptions
madirey 8e2cd14
Add tests for stable hashes
madirey 85f873d
Additional testing and type cleanup
madirey e5296ce
Merge branch 'master' of github.com:elastic/kibana into policy-creati…
madirey e5731e5
Remove unnecessary log
madirey 08afa76
Minor fixup
madirey 5bf5655
jsdoc
madirey 87f8ee4
type fixup
madirey 807f80f
Additional type adjustments
madirey 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
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.
maybe me more specific in the naming, any reason to no keep this in the security_solution plugin? it will make future change easier no?
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.
@nchaulet These are mocks related to the policy, so IMO they belong here. The manifest is part of the policy. I'm happy to rename or move though if that's the consensus. Can we address in a quick follow-up to this one?
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.
We discussed and in our next PR, I'll see if I can make the names more descriptive. Leaving them here for now, as they may be useful for future tests. We can move them to security_solution if they don't end up being useful here.
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.
@madirey sorry for the late response.
I agree with @nchaulet on this here - these are endpoint specific mocks that Ingest knows nothing about. We only use their data structure to store our Policy data in (the area where we store it accepts any json blob).
We should really move them to our Plugin (probably under the generator we have in
/common/endpoint
.