Graylog2/graylog2-server

Deleting or renaming a pipeline rule should update corresponding references in the pipelines

Open

#21,162 建立於 2024年12月11日

在 GitHub 查看
 (5 留言) (0 反應) (0 負責人)Java (6,945 star) (1,032 fork)batch import
good first issueimprovementtriaged

描述

When a pipeline rule is deleted or renamed, we do not update affected pipelines. Invalid references are left over. It looks messy and forces the user to explicitly remove or update the rule wherever it had been used. GL has the ability to do this on behalf of the user.

Your Environment

  • Graylog Version: 6.2

貢獻者指南

技術棧
java
領域
backend
議題類型
feature
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
1-2 days
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
active
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
clear
前置要求
JavaGraylog pipeline systemGit version control
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
40
研究方向
Start by understanding the pipeline rule deletion/renaming flow in the codebase. Look at the PipelineRuleService and related classes to identify where rules are removed or renamed. Then investigate how pipelines reference rules (likely via IDs or names) and implement a mechanism to update or remove those references. Check existing tests for similar behaviors to guide implementation.