Skip to content
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

[7.x] [Security Solution][Detections] Indicator path followup (#91747) #91772

Merged
merged 1 commit into from
Feb 18, 2021

Conversation

rylnd
Copy link
Contributor

@rylnd rylnd commented Feb 17, 2021

Backports the following commits to 7.x:

* Remove eslint issue by not permuting our input

We instead return a new object from our enrich function.

* Fixes editing of non-indicator rules

If the user edits a rule without visiting the About tab, they will
receive a value of threatIndicatorPath: '' which we'll then try to send
to the backend, but it gets rejected.

By removing this defaulting logic we get the correct behavior: existing
rules default to threatIndicatorPath: undefined, which gets stripped
before being sent to the backend. If the rule is an indicator rule, the
value will be persisted as expected.

* Move default indicator path to common constant
@rylnd rylnd added the backport label Feb 17, 2021
@kibanamachine
Copy link
Contributor

💚 Build Succeeded

Metrics [docs]

Async chunks

Total size of all lazy-loaded chunks that will be downloaded as the user navigates the app

id before after diff
securitySolution 7.7MB 7.7MB -84.0B

Page load bundle

Size of the bundles that are downloaded on every page load. Target size is below 100kb

id before after diff
securitySolution 237.4KB 237.5KB +140.0B

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream

@rylnd rylnd merged commit 7dddca8 into elastic:7.x Feb 18, 2021
@rylnd rylnd deleted the backport/7.x/pr-91747 branch February 18, 2021 01:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants