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.

Sign up for GitHub

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

Jump to bottom

[Security Solution] Handle the meta field #180291

Closed
jpdjere opened this issue Apr 8, 2024 · 4 comments
Closed

[Security Solution] Handle the meta field #180291

jpdjere opened this issue Apr 8, 2024 · 4 comments
Labels
Feature:Prebuilt Detection Rules Security Solution Prebuilt Detection Rules area Team:Detection Rule Management Security Detection Rule Management Team Team:Detections and Resp Security Detection Response Team Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc.

Comments

@jpdjere
Copy link
Contributor

jpdjere commented Apr 8, 2024 •
edited
Loading

Epics: https://github.com/elastic/security-team/issues/1974 (internal), #174168

UPDATE:

Ticket closed in favour of #180393, which centralises decisions on how to handle fields during upgrade workflow.

Summary

  • Handle the meta field:
    • Should not be returned by the /upgrade/_review endpoint.
    • Should be handled automatically by the /upgrade/_perform endpoint: the user's value should always be used as the final version to update to.
  • No diff should ever show up for this field. (comment)

Background

TBD
@jpdjere jpdjere added triage_needed Team:Detections and Resp Security Detection Response Team Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. Team:Detection Rule Management Security Detection Rule Management Team Feature:Prebuilt Detection Rules Security Solution Prebuilt Detection Rules area labels Apr 8, 2024
@elasticmachine
Copy link
Contributor

Pinging @elastic/security-detections-response (Team:Detections and Resp)

@elasticmachine
Copy link
Contributor

Pinging @elastic/security-solution (Team: SecuritySolution)

@elasticmachine
Copy link
Contributor

Pinging @elastic/security-detection-rule-management (Team:Detection Rule Management)

@jpdjere jpdjere mentioned this issue Apr 8, 2024
Open
@jpdjere
Copy link
Contributor Author

jpdjere commented Apr 16, 2024

Closing in favour of ticket that centralizes decisions on how to handle fields during upgrade workflow: #180393

@jpdjere jpdjere closed this as not planned Won't fix, can't repro, duplicate, stale Apr 16, 2024
@banderror banderror changed the title [Security Solution] Handle the meta field [Security Solution] Handle the meta field (DRAFT) Apr 17, 2024
@jpdjere jpdjere changed the title [Security Solution] Handle the meta field (DRAFT) [Security Solution] Handle the meta field Apr 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Feature:Prebuilt Detection Rules Security Solution Prebuilt Detection Rules area Team:Detection Rule Management Security Detection Rule Management Team Team:Detections and Resp Security Detection Response Team Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@jpdjere @banderror @elasticmachine