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

[Security Solution][Detections] Prevent rules from being created with a blank name or description #82087

Merged
merged 3 commits into from
Nov 2, 2020

Conversation

rylnd
Copy link
Contributor

@rylnd rylnd commented Oct 29, 2020

Summary

Our validations were a little lax here. While the fields did not cause
any errors as they're still strings, the lack of content causes some UX
weirdness that we should prevent.

Closes #81319

Checklist

Delete any items that are not applicable to this PR.

For maintainers

Our validations were a little lax here. While the fields did not cause
any errors as they're still strings, the lack of content causes some UX
weirdness that we should prevent.

Closes elastic#81319
@rylnd rylnd added v8.0.0 release_note:skip Skip the PR/issue when compiling release notes v7.11.0 Team:Detections and Resp Security Detection Response Team Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. labels Oct 29, 2020
@rylnd rylnd requested review from a team as code owners October 29, 2020 21:52
@rylnd rylnd self-assigned this Oct 29, 2020
Adding in the other required fields here to get a more concise error.
Copy link
Contributor

@marshallmain marshallmain left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@peluja1012
Copy link
Contributor

@elasticmachine merge upstream

@kibanamachine
Copy link
Contributor

💚 Build Succeeded

Metrics [docs]

page load bundle size

id before after diff
securitySolution 242.0KB 242.1KB +107.0B

History

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

@rylnd rylnd merged commit 039b44f into elastic:master Nov 2, 2020
@rylnd rylnd deleted the no_blank_rules branch November 2, 2020 16:47
@rylnd rylnd added release_note:fix and removed release_note:skip Skip the PR/issue when compiling release notes labels Nov 2, 2020
@rylnd
Copy link
Contributor Author

rylnd commented Nov 2, 2020

Adding a release note for this; if API users are affected by the new validation they'll have to add a name and description via the API.

rylnd added a commit that referenced this pull request Nov 2, 2020
… a blank name or description (#82087) (#82319)

* Prevent rules from being created with a blank name or description

Our validations were a little lax here. While the fields did not cause
any errors as they're still strings, the lack of content causes some UX
weirdness that we should prevent.

Closes #81319

* Fix unit tests for rule updates

Adding in the other required fields here to get a more concise error.

Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>

Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
release_note:fix Team:Detections and Resp Security Detection Response Team Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. v7.11.0 v8.0.0
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Security Solution] API users can create rules with blank name and description
4 participants