Graylog2/graylog2-server

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

Open

#21162 opened on Dec 11, 2024

View on GitHub
 (5 comments) (0 reactions) (0 assignees)Java (6,945 stars) (1,032 forks)batch import
good first issueimprovementtriaged

Description

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

Contributor guide

Tech stack
java
Domain
backend
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
JavaGraylog pipeline systemGit version control
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40
Research direction
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.